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-23 → 2026-08-19). This is what Google measures you on.

Scores

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 4.75 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-23 → 2026-08-19). This is what Google measures you on.

Lab vs field

Lab LCP 4.75 s · field p75 1.28 s · real users are 0.27× faster than the lab.

Field history 25 weeks

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

Page weight

By resource type

Third parties 6 entities

452 kB transferred, 131 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

74 violating nodes across 9 rules, 632 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.

• moderate region — All page content should be contained by landmarks 30 nodes
• critical image-alt — Images must have alternative text 23 nodes
• serious link-name — Links must have discernible text 13 nodes
• serious listitem — <li> elements must be contained in a <ul> or <ol> 3 nodes
• serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
• critical label — Form elements must have labels 1 node
• moderate landmark-one-main — Document should have one main landmark 1 node
• serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node
• serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 7 of 20 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.

• image-alt — Image elements do not have `[alt]` attributes 23 nodes
• link-name — Links do not have a discernible name 13 nodes
• listitem — List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements. 3 nodes
• color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
• list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node
• target-size — Touch targets do not have sufficient size or spacing. 1 node
• landmark-one-main — Document does not have a main landmark. 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 quickchart.io'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://quickchart.io/"></speedlify2-score>