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 ·

firebase.google.com/products/hosting

https://firebase.google.com/products/hosting

53 95 96 85 ✗CWV 7AXE

Data from Aug 20, 2026, 9:34 PM UTC — 21h old.

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

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.

Go Hosted by Google Frontend

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 3.00 s needs-improvement
INP 193 ms good
CLS 0 good

Scores

53
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
85
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 8.42 s — — 8.42 s 8.42 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 386 ms — — 386 ms 386 ms
FCP First Contentful Paint 4.96 s — — 4.96 s 4.96 s
Speed Index 5.47 s — — 5.47 s 5.47 s
TTFB Time to First Byte 629 ms — — 629 ms 629 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 2.18 s
time to first byte 183 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 3.00 s needs-improvement 63.1% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 193 ms good 77% good
CLS CWV 0 good 97.1% good
FCP 2.88 s needs-improvement 43.5% good
TTFB 2.12 s poor 5.5% good

Lab vs field

Lab LCP 8.42 s · field p75 3.00 s · real users are 0.36× 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 3.00 s 190 ms 0 2.87 s 2.13 s
2026-08-08 2.92 s 192 ms 0 2.81 s 2.08 s
2026-08-01 2.83 s 202 ms 0 2.73 s 2.01 s
2026-07-25 2.79 s 206 ms 0 2.69 s 1.99 s
2026-07-18 2.77 s 210 ms 0 2.68 s 1.91 s
2026-07-11 2.78 s 214 ms 0 2.68 s 1.86 s
2026-07-04 2.77 s 212 ms 0 2.63 s 1.86 s
2026-06-27 2.75 s 213 ms 0 2.61 s 1.83 s
2026-06-20 2.79 s 218 ms 0 2.62 s 1.86 s
2026-06-13 2.81 s 206 ms 0 2.63 s 1.89 s
2026-06-06 2.83 s 218 ms 0 2.68 s 1.87 s
2026-05-30 2.88 s 221 ms 0 2.73 s 1.92 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.50 MB — — 1.50 MB 1.50 MB
Requests 76 — — 76 76
Third-party Weight 2.94 MB — — 2.94 MB 2.94 MB
Third-party CPU 326 ms — — 326 ms 326 ms
Unused JS 381.4 kB — — 381.4 kB 381.4 kB
Unused CSS 203.7 kB — — 203.7 kB 203.7 kB

By resource type

script 837.1 kB · 50 req
font 197.3 kB · 3 req
image 194.7 kB · 8 req
stylesheet 170.4 kB · 6 req
document 88.8 kB · 2 req
other 7.1 kB · 7 req
third party 1.21 MB · 63 req

Third parties 3 entities

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

Google CDN 1.97 MB · 95 ms CPU
Google Tag Manager 764.1 kB · 232 ms CPU
Google Fonts 204.7 kB · 0 ms CPU

Page health

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

Main thread work

script evaluation 1.32 s
other 486 ms
style layout 305 ms
script parse compile 271 ms
parse HTML 90 ms
paint composite render 29 ms
garbage collection 22 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 4 rules, 737 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.

  • critical image-alt — Images must have alternative text 4 nodes
  • moderate landmark-main-is-top-level — Main landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 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.

  • image-alt — Image elements do not have `[alt]` attributes 4 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

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, 9:34 PM UTC 53 8.42 s 0 386 ms 1.50 MB 3/3 ±4 3,198 39.8s

Embed this score

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