speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

lewicowo.pl

http://lewicowo.pl/

73 73 78 91 82AXE ✓CWV

Data from Aug 20, 2026, 3:34 PM UTC 3d old

Built Awesome #1,098 · 1 measurement · since Aug 20, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Self-hosted · nginx Hosted by Self-hosted

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.

LCP 710 ms good
INP — no data
CLS 0 good

Scores

73
Performance
no change
73
Accessibility
no change
78
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.76 s — — 5.76 s 5.76 s
CLS Cumulative Layout Shift 0.150 — — 0.150 0.150
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.11 s — — 1.11 s 1.11 s
Speed Index 1.11 s — — 1.11 s 1.11 s
TTFB Time to First Byte 556 ms — — 556 ms 556 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 5.76 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

resource load duration 534 ms
time to first byte 109 ms
element render delay 19 ms
resource load delay 10 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 710 ms good 96.9% good
CLS CWV 0 good 99.4% good
FCP 664 ms good 93.4% good
TTFB 392 ms good 92.6% good

Lab vs field

Lab LCP 5.76 s · field p75 710 ms · real users are 0.12× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 671 ms — 0 642 ms 377 ms
2026-08-08 671 ms — 0 638 ms 374 ms
2026-08-01 697 ms — 0 675 ms 401 ms
2026-07-25 728 ms — 0 694 ms 410 ms
2026-07-18 775 ms — 0 680 ms 402 ms
2026-07-11 850 ms — 0 767 ms 443 ms
2026-07-04 816 ms — 0 735 ms 402 ms
2026-06-27 816 ms — 0 729 ms 390 ms
2026-06-20 868 ms — 0 797 ms 414 ms
2026-06-13 758 ms — 0 720 ms 377 ms
2026-06-06 764 ms — 0 715 ms 389 ms
2026-05-30 816 ms — 0 772 ms 404 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.90 MB — — 1.90 MB 1.90 MB
Requests 23 — — 23 23
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.89 MB · 21 req
document 14.6 kB · 1 req
stylesheet 1.4 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 390 ms — — 390 ms 390 ms
Long Tasks 0 — — 0 0
DOM Elements 270 — — 270 270
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 82 — — 82 82
A11y Failures 4 — — 4 4
A11y Failing Nodes 81 — — 81 81

Main thread work

other 263 ms
style layout 63 ms
paint composite render 44 ms
script evaluation 11 ms
parse HTML 8 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

82 violating nodes across 5 rules, 640 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 35 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 26 nodes
  • critical image-alt — Images must have alternative text 19 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 4 of 15 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 35 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 26 nodes
  • image-alt — Image elements do not have `[alt]` attributes 19 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 3:34 PM UTC 73 5.76 s 0.150 0 ms 1.90 MB 3/3 ±12 2,367 31.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show lewicowo.pl's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="http://lewicowo.pl/"></speedlify2-score>