speedlify2

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.

Core Web Vitals field data, url-level

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

Scores

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

39.4% of pixels differ — parts of the page change. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

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 3.10 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.

Field data Chrome UX Report, url-level

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

Lab vs field LCP

The lab LCP is 1.76× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

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

Page weight

By resource type

Third parties 3 entities

193 kB transferred, 37 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Page health

Main thread work

Axe violations axe-core 4.13.0, full rule set

45 violating nodes across 5 rules, 1051 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 40 nodes
• serious link-in-text-block — Links must be distinguishable without relying on color 2 nodes
• critical button-name — Buttons must have discernible text 1 node
• critical image-alt — Images must have alternative text 1 node
• moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 5 of 29 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. 40 nodes
• link-in-text-block — Links rely on color to be distinguishable. 2 nodes
• button-name — Buttons do not have an accessible name 1 node
• image-alt — Image elements do not have `[alt]` attributes 1 node
• label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

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

Measurement log

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

Embed this score

Live below, then the markup that produces it. Drop that on any page to show pptr.dev'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="https://pptr.dev/"></speedlify2-score>