speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

realproducersmag.com

https://www.realproducersmag.com/

52 76 73 100 ✓CWV 24AXE

Data from Aug 21, 2026, 2:34 PM UTC — 4h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 4h

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.

Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

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

LCP 2.27 s good
INP 71 ms good
CLS 0.030 good

Scores

52
Performance
no change
76
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.71 s — — 6.71 s 6.71 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 787 ms — — 787 ms 787 ms
FCP First Contentful Paint 2.56 s — — 2.56 s 2.56 s
Speed Index 4.46 s — — 4.46 s 4.46 s
TTFB Time to First Byte 1.17 s — — 1.17 s 1.17 s

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.

time to first byte 1.17 s
resource load delay 572 ms
resource load duration 225 ms
element render delay 39 ms

Field data Chrome UX Report, origin-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 2.27 s good 79.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 71 ms good 94.8% good
CLS CWV 0.030 good 89.6% good
FCP 1.70 s good 78% good
TTFB 1.11 s needs-improvement 60.3% good

Lab vs field

Lab LCP 6.71 s · field p75 2.27 s · real users are 0.34× 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 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.65 MB — — 1.65 MB 1.65 MB
Requests 71 — — 71 71
Third-party Weight 1.41 MB — — 1.41 MB 1.41 MB
Third-party CPU 459 ms — — 459 ms 459 ms
Unused JS 402.3 kB — — 402.3 kB 402.3 kB
Unused CSS 49.9 kB — — 49.9 kB 49.9 kB

By resource type

script 1.02 MB · 22 req
image 442.1 kB · 14 req
font 64.7 kB · 4 req
other 64.3 kB · 20 req
stylesheet 43.3 kB · 7 req
document 9.5 kB · 2 req
third party 1.41 MB · 52 req

Third parties 13 entities

1.41 MB transferred, 459 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 491.2 kB · 212 ms CPU
Amazon Web Services 430.2 kB · 0 ms CPU
Facebook 173.7 kB · 86 ms CPU
LiveHelpNow 130.1 kB · 49 ms CPU
Netlify 55.2 kB · 24 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.37 s — — 3.37 s 3.37 s
Long Tasks 14 — — 14 14
DOM Elements 408 — — 408 408
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 24 — — 24 24
A11y Failures 6 — — 6 6
A11y Failing Nodes 21 — — 21 21

Main thread work

script evaluation 1.75 s
other 727 ms
script parse compile 371 ms
style layout 267 ms
parse HTML 113 ms
paint composite render 89 ms
garbage collection 49 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 7 rules, 508 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 10 nodes
  • serious link-name — Links must have discernible text 7 nodes
  • critical button-name — Buttons must have discernible text 3 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • serious frame-title — Frames must have an accessible name 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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

  • link-name — Links do not have a discernible name 7 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 5 nodes
  • button-name — Buttons do not have an accessible name 4 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • aria-allowed-attr — `[aria-*]` attributes do not match their roles 1 node
  • 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 h2 2 console errors

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 21, 2026, 2:34 PM UTC 52 6.71 s 0 787 ms 1.65 MB 3/3 ±10 2,322 38.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show realproducersmag.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://www.realproducersmag.com/"></speedlify-score>