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 ·

render.com

https://render.com/

22 84 54 100 CWV AXE

Data from Aug 21, 2026, 5:36 AM UTC — 13h old.

Web Hosts · 1 measurement · since Aug 21, 2026 · last attempt 13h

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.

LCP 2.17 s good
INP 308 ms needs-improvement
CLS 0.010 good

Scores

22
Performance
no change
84
Accessibility
no change
54
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.64 s 7.64 s 7.64 s
CLS Cumulative Layout Shift 0.832 0.832 0.832
TBT Total Blocking Time 2.03 s 2.03 s 2.03 s
FCP First Contentful Paint 1.56 s 1.56 s 1.56 s
Speed Index 3.93 s 3.93 s 3.93 s
TTFB Time to First Byte 662 ms 662 ms 662 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 217 ms
time to first byte 97 ms

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 2.17 s good 80.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 308 ms needs-improvement 56.2% good
CLS CWV 0.010 good 83.2% good
FCP 1.84 s needs-improvement 73.8% good
TTFB 1.09 s needs-improvement 60% good

Lab vs field

Lab LCP 7.64 s · field p75 2.17 s · real users are 0.28× 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 2.17 s 307 ms 0.010 1.85 s 1.08 s
2026-08-08 2.19 s 309 ms 0.010 1.86 s 1.09 s
2026-08-01 2.21 s 303 ms 0.010 1.87 s 1.09 s
2026-07-25 2.22 s 297 ms 0.020 1.87 s 1.09 s
2026-07-18 2.23 s 297 ms 0.020 1.87 s 1.09 s
2026-07-11 2.23 s 294 ms 0.030 1.87 s 1.08 s
2026-07-04 2.20 s 296 ms 0.030 1.85 s 1.07 s
2026-06-27 2.19 s 299 ms 0.030 1.84 s 1.06 s
2026-06-20 2.18 s 304 ms 0.020 1.83 s 1.05 s
2026-06-13 2.17 s 307 ms 0.010 1.83 s 1.03 s
2026-06-06 2.18 s 312 ms 0.010 1.84 s 1.04 s
2026-05-30 2.18 s 309 ms 0.010 1.84 s 1.04 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.62 MB 2.62 MB 2.62 MB
Requests 142 142 142
Third-party Weight 952.8 kB 952.8 kB 952.8 kB
Third-party CPU 305 ms 305 ms 305 ms
Unused JS 415.5 kB 415.5 kB 415.5 kB
Unused CSS 34.1 kB 34.1 kB 34.1 kB

By resource type

script 1.52 MB · 83 req
font 640.9 kB · 11 req
image 281.2 kB · 24 req
document 80.9 kB · 1 req
other 55.2 kB · 14 req
stylesheet 41.4 kB · 3 req
third party 952.8 kB · 45 req

Third parties 8 entities

952.8 kB transferred, 305 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 500.6 kB · 199 ms CPU
sanity.io 280.9 kB · 0 ms CPU
posthog.com 127.5 kB · 75 ms CPU
LinkedIn Ads 41.1 kB · 29 ms CPU
SalesLoft 2.5 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 8.27 s 8.27 s 8.27 s
Long Tasks 20 20 20
DOM Elements 2,552 2,552 2,552
A11y Failures 4 4 4
A11y Failing Nodes 95 95 95

Main thread work

script evaluation 5.11 s
other 1.44 s
style layout 667 ms
script parse compile 525 ms
paint composite render 260 ms
garbage collection 172 ms
parse HTML 99 ms

Axe violations axe-core , full rule set

The axe run failed: Navigation timeout of 120000 ms exceeded

Accessibility failures 4 of 25 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
  • svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 45 nodes
  • button-name — Buttons do not have an accessible name 2 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 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, 5:36 AM UTC 22 7.64 s 0.832 2.03 s 2.62 MB 3/3 ±23 2,386 167.6s

Embed this score

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