heyflow.com
Data from Aug 20, 2026, 11:25 PM UTC — 19h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h
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-22 → 2026-08-18). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 20.63 s | — | — | 20.63 s | 20.63 s | |
| CLS Cumulative Layout Shift | 0.030 | — | — | 0.030 | 0.030 | |
| TBT Total Blocking Time | 1.57 s | — | — | 1.57 s | 1.57 s | |
| FCP First Contentful Paint | 1.10 s | — | — | 1.10 s | 1.10 s | |
| Speed Index | 6.85 s | — | — | 6.85 s | 6.85 s | |
| TTFB Time to First Byte | 638 ms | — | — | 638 ms | 638 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-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 2.18 s | good | 77.9% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 514 ms | poor | 45% good |
| CLS CWV | 0.020 | good | 95.6% good |
| FCP | 1.74 s | good | 75.8% good |
| TTFB | 810 ms | needs-improvement | 75.1% good |
Lab vs field
Lab LCP 20.63 s · field p75 2.18 s · real users are 0.11× 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 | 2.35 s | 555 ms | 0.020 | 1.80 s | 862 ms |
| 2026-08-08 | 2.60 s | 495 ms | 0.020 | 1.87 s | 924 ms |
| 2026-08-01 | 2.48 s | 441 ms | 0.020 | 1.76 s | 907 ms |
| 2026-07-25 | 2.27 s | 467 ms | 0.020 | 1.73 s | 880 ms |
| 2026-07-18 | 2.77 s | 473 ms | 0.030 | 2.13 s | 1.38 s |
| 2026-07-11 | 2.37 s | 548 ms | 0.030 | 2.14 s | 1.35 s |
| 2026-07-04 | 2.18 s | 593 ms | 0.030 | 2.13 s | 1.44 s |
| 2026-06-27 | 2.06 s | 562 ms | 0.030 | 2.00 s | 1.30 s |
| 2026-06-20 | 1.69 s | 565 ms | 0.020 | 1.70 s | 789 ms |
| 2026-06-13 | 1.62 s | 510 ms | 0.030 | 1.65 s | 663 ms |
| 2026-06-06 | 1.64 s | 422 ms | 0.030 | 1.61 s | 585 ms |
| 2026-05-30 | 1.46 s | 372 ms | 0.020 | 1.45 s | 538 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 12.41 MB | — | — | 12.41 MB | 12.41 MB | |
| Requests | 201 | — | — | 201 | 201 | |
| Third-party Weight | 6.93 MB | — | — | 6.93 MB | 6.93 MB | |
| Third-party CPU | 565 ms | — | — | 565 ms | 565 ms | |
| Unused JS | 573.6 kB | — | — | 573.6 kB | 573.6 kB | |
| Unused CSS | 18.5 kB | — | — | 18.5 kB | 18.5 kB |
By resource type
Third parties 15 entities
6.93 MB transferred, 565 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 | 12.12 s | — | — | 12.12 s | 12.12 s | |
| Long Tasks | 20 | — | — | 20 | 20 | |
| DOM Elements | 1,005 | — | — | 1,005 | 1,005 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 3 | — | — | 3 | 3 | |
| A11y Failing Nodes | 10 | — | — | 10 | 10 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 73 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.
-
critical
meta-refresh— Delayed refresh under 20 hours must not be used 1 node
Accessibility failures 3 of 28 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.
-
target-size— Touch targets do not have sufficient size or spacing. 8 nodes -
list— Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node -
svg-img-alt— SVG elements with an `img` role do not have an accessible text alternative 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 20, 2026, 11:25 PM UTC | 42 | 20.63 s | 0.030 | 1.57 s | 12.41 MB | 3/3 | ±7 | 2,482 | 65.2s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
heyflow.com'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://heyflow.com/"></speedlify-score>