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 ·

framer.com

https://www.framer.com/

55 91 54 92 !AXE CWV

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

Overall #966 Website Builders #1 · 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.

Framer Built with Framer
Fr Hosted by Framer

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 2.00 s good
INP 181 ms good
CLS 0 good

Scores

55
Performance
no change
91
Accessibility
no change
54
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 697 ms
  2. 1.39 s
  3. 2.09 s
  4. 2.79 s
  5. 3.48 s
  6. 4.18 s
  7. 4.88 s
  8. 5.57 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.71 s 4.71 s 4.71 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 1.40 s 1.40 s 1.40 s
FCP First Contentful Paint 1.72 s 1.72 s 1.72 s
Speed Index 3.75 s 3.75 s 3.75 s
TTFB Time to First Byte 619 ms 619 ms 619 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 4.71 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.

resource load delay 93 ms
element render delay 66 ms
resource load duration 27 ms
time to first byte 21 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 2.00 s good 82.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 181 ms good 77.1% good
CLS CWV 0 good 96.1% good
FCP 1.57 s good 79.1% good
TTFB 989 ms needs-improvement 67.8% good

Lab vs field

Lab LCP 4.71 s · field p75 2.00 s · real users are 0.42× 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 2.00 s 180 ms 0 1.56 s 983 ms
2026-08-15 1.92 s 171 ms 0 1.44 s 859 ms
2026-08-08 1.88 s 160 ms 0 1.36 s 768 ms
2026-08-01 1.97 s 150 ms 0 1.42 s 826 ms
2026-07-25 1.98 s 150 ms 0 1.47 s 871 ms
2026-07-18 2.04 s 146 ms 0 1.51 s 905 ms
2026-07-11 2.16 s 146 ms 0 1.55 s 933 ms
2026-07-04 2.25 s 151 ms 0 1.56 s 934 ms
2026-06-27 2.32 s 160 ms 0.010 1.56 s 921 ms
2026-06-20 2.39 s 170 ms 0.020 1.56 s 898 ms
2026-06-13 2.38 s 178 ms 0.050 1.55 s 856 ms
2026-06-06 2.36 s 182 ms 0.050 1.53 s 819 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.43 MB 4.43 MB 4.43 MB
Requests 202 202 202
Third-party Weight 4.57 MB 4.57 MB 4.57 MB
Third-party CPU 1.39 s 1.39 s 1.39 s
Unused JS 310 kB 310 kB 310 kB
Unused CSS 24.1 kB 24.1 kB 24.1 kB

By resource type

media 1.76 MB · 2 req
script 1.71 MB · 119 req
image 446 kB · 22 req
font 287 kB · 6 req
document 193 kB · 3 req
other 32.0 kB · 30 req
third party 4.21 MB · 158 req

Third parties 13 entities

4.57 MB transferred, 1.39 s of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Framer CDN 4.06 MB · 1.05 s CPU
Google Tag Manager 364 kB · 282 ms CPU
Hubspot 67.5 kB · 31 ms CPU
openai.com 26.7 kB · 9 ms CPU
debugbear.com 16.7 kB · 7 ms CPU

Page health

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

Main thread work

script evaluation 6.48 s
other 3.17 s
style layout 981 ms
paint composite render 380 ms
parse HTML 338 ms
script parse compile 269 ms
garbage collection 232 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 3 rules, 2952 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 region — All page content should be contained by landmarks 3 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 3 of 29 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. 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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 7 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 55 4.71 s 0.001 1.40 s 4.43 MB 3/3 ±31 2,474 71.9s

Embed this score

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