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 ·

runawayracing.com

https://runawayracing.com/

72 89 100 92 CWV 111AXE

Data from Aug 21, 2026, 3:32 PM UTC — 3h old.

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

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.

Eleventy Built with Eleventy
Cloudflare Hosted by Cloudflare

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 1.32 s good
INP 75 ms good
CLS 0 good

Scores

72
Performance
no change
89
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 12.53 s 12.53 s 12.53 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.49 s 2.49 s 2.49 s
Speed Index 2.49 s 2.49 s 2.49 s
TTFB Time to First Byte 648 ms 648 ms 648 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.

element render delay 209 ms
resource load delay 97 ms
time to first byte 36 ms
resource load duration 31 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 1.32 s good 92.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 75 ms good 97.7% good
CLS CWV 0 good 98.3% good
FCP 1.06 s good 92.2% good
TTFB 487 ms good 92.5% good

Lab vs field

Lab LCP 12.53 s · field p75 1.32 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 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 2.07 s 0 1.19 s 604 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.30 MB 5.30 MB 5.30 MB
Requests 110 110 110
Third-party Weight 4.79 MB 4.79 MB 4.79 MB
Third-party CPU 121 ms 121 ms 121 ms
Unused JS 173.5 kB 173.5 kB 173.5 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 4.70 MB · 49 req
script 380.4 kB · 11 req
font 87.1 kB · 6 req
stylesheet 61.1 kB · 8 req
document 51.1 kB · 3 req
other 16.6 kB · 30 req
third party 4.90 MB · 41 req

Third parties 6 entities

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

Cloudinary 4.41 MB · 0 ms CPU
Google CDN 320.2 kB · 118 ms CPU
Adobe TypeKit 52.3 kB · 0 ms CPU
JSDelivr CDN 3.6 kB · 1 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.66 s 2.66 s 2.66 s
Long Tasks 7 7 7
DOM Elements 1,219 1,219 1,219
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 111 111 111
A11y Failures 3 3 3
A11y Failing Nodes 77 77 77

Main thread work

script evaluation 1.06 s
other 854 ms
style layout 326 ms
paint composite render 252 ms
script parse compile 99 ms
parse HTML 64 ms
garbage collection 6 ms

Axe violations axe-core 4.13.0, full rule set

111 violating nodes across 8 rules, 1479 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 60 nodes
  • serious link-name — Links must have discernible text 43 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 2 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-banner-is-top-level — Banner landmark should not be contained in another landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 3 of 32 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. 47 nodes
  • link-name — Links do not have a discernible name 29 nodes
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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

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, 3:32 PM UTC 72 12.53 s 0 0 ms 5.30 MB 3/3 ±12 2,355 49.4s

Embed this score

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