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 ·

bunny.net

https://bunny.net/

65 92 96 100 ✗CWV 17AXE

Data from Aug 20, 2026, 7:31 PM UTC — 23h old.

Web Hosts · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.

Gatsby 4.25.9 Built with Gatsby 4.25.9
Bu Hosted by Bunny CDN

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 2.77 s needs-improvement
INP 207 ms needs-improvement
CLS 0.050 good

Scores

65
Performance
no change
92
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.01 s — — 6.01 s 6.01 s
CLS Cumulative Layout Shift 0.006 — — 0.006 0.006
TBT Total Blocking Time 168 ms — — 168 ms 168 ms
FCP First Contentful Paint 4.51 s — — 4.51 s 4.51 s
Speed Index 4.51 s — — 4.51 s 4.51 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.

element render delay 329 ms
time to first byte 8 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 2.77 s needs-improvement 71% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 207 ms needs-improvement 73.7% good
CLS CWV 0.050 good 88.8% good
FCP 1.61 s good 78.7% good
TTFB 845 ms needs-improvement 74.1% good

Lab vs field

Lab LCP 6.01 s · field p75 2.77 s · real users are 0.46× 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.71 s 210 ms 0.050 1.50 s 806 ms
2026-08-08 2.58 s 213 ms 0.050 1.33 s 739 ms
2026-08-01 2.57 s 218 ms 0.050 1.30 s 693 ms
2026-07-25 2.52 s 213 ms 0.050 1.23 s 640 ms
2026-07-18 2.51 s 212 ms 0.040 1.20 s 613 ms
2026-07-11 2.54 s 209 ms 0.040 1.22 s 611 ms
2026-07-04 2.52 s 209 ms 0.040 1.22 s 611 ms
2026-06-27 2.53 s 213 ms 0.050 1.22 s 582 ms
2026-06-20 2.56 s 214 ms 0.050 1.23 s 577 ms
2026-06-13 2.57 s 219 ms 0.050 1.21 s 563 ms
2026-06-06 2.58 s 222 ms 0.060 1.16 s 515 ms
2026-05-30 2.69 s 303 ms 0.080 1.08 s 479 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.73 MB — — 4.73 MB 4.73 MB
Requests 140 — — 140 140
Third-party Weight 3.11 MB — — 3.11 MB 3.11 MB
Third-party CPU 36 ms — — 36 ms 36 ms
Unused JS 359.6 kB — — 359.6 kB 359.6 kB
Unused CSS 157.5 kB — — 157.5 kB 157.5 kB

By resource type

media 2.87 MB · 1 req
script 762.6 kB · 16 req
image 519.2 kB · 93 req
font 355.0 kB · 7 req
document 186.1 kB · 6 req
other 41.0 kB · 11 req
stylesheet 1.6 kB · 1 req
third party 3.14 MB · 19 req

Third parties 3 entities

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

b-cdn.net 2.87 MB · 0 ms CPU
Cookiebot 232.5 kB · 27 ms CPU
Trust Pilot 8.3 kB · 9 ms CPU

Page health

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

Main thread work

other 1.26 s
script evaluation 776 ms
style layout 475 ms
script parse compile 158 ms
parse HTML 142 ms
paint composite render 137 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 3 rules, 1462 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 link-name — Links must have discernible text 8 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 6 nodes
  • moderate heading-order — Heading levels should only increase by one 3 nodes

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

  • link-name — Links do not have a discernible name 8 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 6 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 3 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 9 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 20, 2026, 7:31 PM UTC 65 6.01 s 0.006 168 ms 4.73 MB 3/3 ±14 4,246 96.6s

Embed this score

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