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 ·

gsap.com

https://gsap.com/

89 90 100 100 CWV 2AXE

Data from Aug 20, 2026, 11:29 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

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

LCP 4.25 s poor
INP 128 ms good
CLS 0 good

Scores

89
Performance
no change
90
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

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

time to first byte 293 ms
element render delay 124 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 4.25 s poor 60.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 128 ms good 86.3% good
CLS CWV 0 good 98.8% good
FCP 1.92 s needs-improvement 69.9% good
TTFB 1.60 s needs-improvement 37% good

Lab vs field

Lab LCP 3.36 s · field p75 4.25 s · real users are 1.26× slower 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 4.44 s 128 ms 0 1.91 s 1.59 s
2026-08-08 4.61 s 130 ms 0 1.91 s 1.60 s
2026-08-01 4.58 s 128 ms 0 1.90 s 1.59 s
2026-07-25 4.27 s 129 ms 0 1.90 s 1.59 s
2026-07-18 3.75 s 130 ms 0 1.88 s 1.59 s
2026-07-11 3.35 s 130 ms 0 1.87 s 1.57 s
2026-07-04 3.37 s 132 ms 0 1.85 s 1.55 s
2026-06-27 3.48 s 130 ms 0 1.84 s 1.54 s
2026-06-20 3.51 s 130 ms 0 1.84 s 1.54 s
2026-06-13 3.50 s 128 ms 0 1.83 s 1.52 s
2026-06-06 3.60 s 129 ms 0 1.87 s 1.54 s
2026-05-30 3.53 s 130 ms 0 1.87 s 1.53 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.02 MB 2.02 MB 2.02 MB
Requests 36 36 36
Third-party Weight 181.2 kB 181.2 kB 181.2 kB
Third-party CPU 77 ms 77 ms 77 ms
Unused JS 128.5 kB 128.5 kB 128.5 kB
Unused CSS 12.8 kB 12.8 kB 12.8 kB

By resource type

media 1.34 MB · 13 req
script 302.0 kB · 7 req
image 217.4 kB · 6 req
document 79.7 kB · 1 req
font 77.3 kB · 2 req
other 4.1 kB · 3 req
third party 181.2 kB · 2 req

Third parties 2 entities

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

Google Tag Manager 169.8 kB · 74 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

other 1.41 s
script evaluation 822 ms
style layout 478 ms
paint composite render 239 ms
parse HTML 85 ms
script parse compile 70 ms
garbage collection 13 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 846 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 heading-order — Heading levels should only increase by one 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 3 of 23 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.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-name — Links do not have a discernible name 1 node
  • target-size — Touch targets do not have sufficient size or spacing. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1

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 20, 2026, 11:29 PM UTC 89 3.36 s 0 153 ms 2.02 MB 3/3 ±7 2,474 37s

Embed this score

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