quickchart.io
Data from Aug 21, 2026, 6:51 AM UTC — 12h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 12h
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
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 4.75 s | — | — | 4.75 s | 4.75 s | |
| CLS Cumulative Layout Shift | 0.019 | — | — | 0.019 | 0.019 | |
| TBT Total Blocking Time | 120 ms | — | — | 120 ms | 120 ms | |
| FCP First Contentful Paint | 1.03 s | — | — | 1.03 s | 1.03 s | |
| Speed Index | 1.38 s | — | — | 1.38 s | 1.38 s | |
| TTFB Time to First Byte | 513 ms | — | — | 513 ms | 513 ms |
What LCP is made of
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
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.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.28 s | good | 93.6% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 95 ms | good | 93.3% good |
| CLS CWV | 0 | good | 93.6% good |
| FCP | 1.17 s | good | 87.1% good |
| TTFB | 653 ms | good | 80.7% good |
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.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-15 | 1.25 s | 96 ms | 0 | 1.15 s | 612 ms |
| 2026-08-08 | 1.16 s | 93 ms | 0 | 1.01 s | 559 ms |
| 2026-08-01 | 1.15 s | 95 ms | 0 | 998 ms | 592 ms |
| 2026-07-25 | 1.09 s | 92 ms | 0 | 963 ms | 549 ms |
| 2026-07-18 | 1.07 s | 90 ms | 0 | 972 ms | 546 ms |
| 2026-07-11 | 1.09 s | 90 ms | 0 | 992 ms | 583 ms |
| 2026-07-04 | 1.08 s | 87 ms | 0 | 990 ms | 570 ms |
| 2026-06-27 | 1.08 s | 89 ms | 0 | 982 ms | 587 ms |
| 2026-06-20 | 1.10 s | 90 ms | 0 | 1.00 s | 581 ms |
| 2026-06-13 | 1.11 s | 91 ms | 0 | 1.01 s | 576 ms |
| 2026-06-06 | 1.13 s | 94 ms | 0 | 1.04 s | 582 ms |
| 2026-05-30 | 1.17 s | 93 ms | 0 | 1.07 s | 594 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 928.7 kB | — | — | 928.7 kB | 928.7 kB | |
| Requests | 37 | — | — | 37 | 37 | |
| Third-party Weight | 451.6 kB | — | — | 451.6 kB | 451.6 kB | |
| Third-party CPU | 131 ms | — | — | 131 ms | 131 ms | |
| Unused JS | 179.7 kB | — | — | 179.7 kB | 179.7 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 6 entities
451.6 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
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 1.04 s | — | — | 1.04 s | 1.04 s | |
| Long Tasks | 5 | — | — | 5 | 5 | |
| DOM Elements | 1,006 | — | — | 1,006 | 1,006 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 74 | — | — | 74 | 74 | |
| A11y Failures | 7 | — | — | 7 | 7 | |
| A11y Failing Nodes | 43 | — | — | 43 | 43 |
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.
| When | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 21, 2026, 6:51 AM UTC | 82 | 4.75 s | 0.019 | 120 ms | 928.7 kB | 3/3 | ±7 | 2,489 | 27.6s |
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 speedlify-score.js component code into your site!
<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://quickchart.io/"></speedlify-score>