Check of ciunkos.com/korpo-tlumacz

Nov 4, 2026, 12:44 · daily

Lighthouse 13.5 (mobile, simulated throttling), median of three runs. Scores 0–100: 90 and up green, 50–89 orange, below 50 red; a dash means the category was not measured in that check.

TBT is the lab stand-in for INP, which needs real interactions.

Performance
84needs improvement−11 vs previous
LCP
3.0 sneeds improvement+1.5 s vs previous
CLS
0good±0 vs previous
TBT
427 msneeds improvement+189 ms vs previous
FCP
1.2 sgood+4 ms vs previous
TTFB
36 msgood+13 ms vs previous

Slower than before: LCP, TBT, Performance

First screen: https://ciunkos.com/korpo-tlumacz
First screen
LCP element
div Wpłynął sygnał od zespołu, więc wszczynamy procedurę wyjaśniającą i przygotowal…
Page weight
635 KB
Long tasks
6
Conditions
Lighthouse 13.5.0, mobile (Moto G Power emulation, 412×823), simulated throttling (150 ms RTT, 1.6 Mbps, CPU 4×), median of 3 runs, benchmarkIndex 1923

Loads

LoadPerfLCPFCPTBTCLSTTFB
1871.4 s1.3 s494 ms0539 ms
2813.0 s1.2 s506 ms047 ms
3843.0 s1.2 s427 ms036 ms

What failed

Performance 84

Accessibility 100

Best Practices 100

SEO 100

Nothing failed in this category.

Google PageSpeed Insights: Comparison details

Vitals Desk is the primary measurement. Google adds one mobile lab run from its servers. This comparison does not change our scores, history or slowdown emails.

Substantial differences: Performance, LCP, TBT, FCP

The Lighthouse versions differ; scores and checks may not be directly comparable.

Different locations, hardware, Lighthouse versions and a single run versus our three-run median can produce different results. These are comparison notes, not regression alerts.

Google PageSpeed Insights
MetricVitals DeskGoogleGoogle minus Vitals Desk
Performance8494+10
Accessibility100100±0
Best Practices10092−8
SEO100100±0
LCP3.0 s1.7 s−1.3 s
CLS00.02+0.02
TBT427 ms242 ms−185 ms
FCP1.2 s1.7 s+462 ms
TTFB36 ms4 ms−32 ms
Lighthouse version
13.6.0
Google checked at
Nov 4, 2026, 12:44
Google’s final URL
https://ciunkos.com/korpo-tlumacz

Additional failed checks in Google’s sample

These appear in Google’s saved sample but not in our saved list. Each source keeps a limited list.

  • Legacy JavaScript legacy-javascript-insight (Performance)
  • Time to Interactive interactive (Performance)
  • Browser errors were logged to the console errors-in-console (Best Practices)
  • Issues were logged in the `Issues` panel in Chrome Devtools inspector-issues (Best Practices)

Open PageSpeed Insights