speedlify2

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

Measurement runs · Embed a score ·

webflow.com

https://webflow.com/

31 100 73 100 !AXE ✗CWV

Data from Aug 25, 2026, 1:50 PM UTC 6h old

Overall #1,456 Website Builders #5 · 1 measurement · since Aug 25, 2026

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.

Webflow Built with Webflow

Core Web Vitals field data, url-level

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

LCP 5.06 s poor
INP 348 ms needs-improvement
CLS 0 good

Scores

31
Performance
no change
100
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 4.62 s.

  1. 578 ms
  2. 1.16 s
  3. 1.73 s
  4. 2.31 s
  5. 2.89 s
  6. 3.47 s
  7. 4.04 s
  8. 4.62 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 24.93 s — — 24.93 s 24.93 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1.43 s — — 1.43 s 1.43 s
FCP First Contentful Paint 8.84 s — — 8.84 s 8.84 s
Speed Index 9.81 s — — 9.81 s 9.81 s
TTFB Time to First Byte 661 ms — — 661 ms 661 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 24.93 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 2.20 s
time to first byte 57 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 5.06 s poor 42.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 348 ms needs-improvement 51.2% good
CLS CWV 0 good 90.8% good
FCP 4.42 s poor 38.3% good
TTFB 1.76 s needs-improvement 45.8% good

Lab vs field

Lab LCP 24.93 s · field p75 5.06 s · real users are 0.2× 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-22 5.06 s 349 ms 0 4.42 s 1.76 s
2026-08-15 5.01 s 351 ms 0 4.39 s 1.72 s
2026-08-08 4.99 s 366 ms 0 4.36 s 1.68 s
2026-08-01 4.95 s 373 ms 0 4.32 s 1.65 s
2026-07-25 5.00 s 382 ms 0 4.36 s 1.63 s
2026-07-18 5.11 s 393 ms 0 4.48 s 1.63 s
2026-07-11 5.23 s 388 ms 0 4.59 s 1.64 s
2026-07-04 5.29 s 428 ms 0 4.63 s 1.63 s
2026-06-27 5.28 s 491 ms 0 4.61 s 1.62 s
2026-06-20 5.21 s 551 ms 0 4.55 s 1.63 s
2026-06-13 5.35 s 624 ms 0.010 4.68 s 1.67 s
2026-06-06 5.45 s 597 ms 0.150 4.78 s 1.72 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.50 MB — — 3.50 MB 3.50 MB
Requests 186 — — 186 186
Third-party Weight 3.36 MB — — 3.36 MB 3.36 MB
Third-party CPU 846 ms — — 846 ms 846 ms
Unused JS 627 kB — — 627 kB 627 kB
Unused CSS 22.9 kB — — 22.9 kB 22.9 kB

By resource type

script 1.88 MB · 69 req
image 1.19 MB · 61 req
font 214 kB · 2 req
document 115 kB · 3 req
stylesheet 55.0 kB · 7 req
other 44.4 kB · 44 req
third party 3.36 MB · 182 req

Third parties 30 entities

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

website-files.com 1.60 MB · 46 ms CPU
Google Tag Manager 520 kB · 223 ms CPU
Facebook 232 kB · 116 ms CPU
transcend-cdn.com 163 kB · 62 ms CPU
qualified.com 127 kB · 44 ms CPU

Page health

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

Main thread work

script evaluation 4.03 s
other 1.40 s
style layout 1.35 s
script parse compile 474 ms
paint composite render 204 ms
parse HTML 169 ms
garbage collection 71 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 2565 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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 25, 2026, 1:50 PM UTC 31 24.93 s 0 1.43 s 3.50 MB 3/3 ±3 3,196 59.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show webflow.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://webflow.com/"></speedlify2-score>