Check of ciunkos.com/korpo-tlumacz

Nov 3, 2026, 12:45 · 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
95good±0 vs previous
LCP
1.5 sgood+3 ms vs previous
CLS
0good±0 vs previous
TBT
238 msneeds improvement±0 vs previous
FCP
1.2 sgood+3 ms vs previous
TTFB
23 msgood+2 ms vs previous

No slowdown against the previous check and the 7-day median.

First screen: https://ciunkos.com/korpo-tlumacz
First screen
LCP element
div Popieram kierunek. Wszystko jest dla mnie jasne.
Page weight
630 KB
Long tasks
3
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 2804

Loads

LoadPerfLCPFCPTBTCLSTTFB
1NO_NAVSTART
2951.5 s1.2 s238 ms023 ms
3961.5 s1.2 s215 ms021 ms

What failed

Performance 95

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: 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
Performance9596+1
Accessibility100100±0
Best Practices10092−8
SEO100100±0
LCP1.5 s1.7 s+166 ms
CLS00±0
TBT238 ms180 ms−58 ms
FCP1.2 s1.7 s+466 ms
TTFB23 ms5 ms−18 ms
Lighthouse version
13.6.0
Google checked at
Nov 3, 2026, 12:45
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.

  • Duplicated JavaScript duplicated-javascript-insight (Performance)
  • Forced reflow forced-reflow-insight (Performance)
  • Legacy JavaScript legacy-javascript-insight (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