speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Charts Measurement runs Embed a score

huggingface.co

https://huggingface.co/

73 69 77 100 AXE CWV

Data from Aug 31, 2026, 9:05 PM UTC old

Overall #1,432 AI #8 Developer Tooling #71 · 1 measurement · since Aug 31, 2026

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-08-02 → 2026-08-29).

LCP 1.39 s good
INP 186 ms good
CLS 0 good

Lighthouse Scores

73
Performance
no change
69
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.69 s 3.69 s 3.69 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 600 ms 600 ms 600 ms
FCP First Contentful Paint 1.82 s 1.82 s 1.82 s
Speed Index 1.82 s 1.82 s 1.82 s
TTFB Time to First Byte 616 ms 616 ms 616 ms

LCP Subparts lab observed, unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab metrics LCP metric shown above is throttled.

element render delay 264 ms
time to first byte 22 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-08-02 → 2026-08-29).

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.39 s good 90.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 186 ms good 77.2% good
CLS CWV 0 good 93.4% good
FCP 1.27 s good 85.7% good
TTFB 589 ms good 84.3% good

Lab LCP vs Field LCP

Lab 3.69 s
Field p75 1.39 s

The lab LCP is 2.65× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-29 1.39 s 186 ms 0 1.27 s 589 ms
2026-08-22 1.42 s 186 ms 0 1.27 s 592 ms
2026-08-15 1.45 s 183 ms 0 1.29 s 586 ms
2026-08-08 1.49 s 187 ms 0 1.31 s 590 ms
2026-08-01 1.52 s 190 ms 0 1.33 s 597 ms
2026-07-25 1.54 s 195 ms 0 1.35 s 610 ms
2026-07-18 1.58 s 199 ms 0 1.37 s 629 ms
2026-07-11 1.59 s 200 ms 0 1.38 s 632 ms
2026-07-04 1.61 s 203 ms 0 1.39 s 648 ms
2026-06-27 1.62 s 203 ms 0 1.40 s 661 ms
2026-06-20 1.62 s 202 ms 0 1.39 s 666 ms
2026-06-13 1.60 s 200 ms 0 1.39 s 671 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.27 MB 3.27 MB 3.27 MB
Requests 104 104 104
Third-party Weight 574 kB 574 kB 574 kB
Third-party CPU 173 ms 173 ms 173 ms
Unused JS 325 kB 325 kB 325 kB
Unused CSS 0 B 0 B 0 B

By resource type

  • image 69% 2.12 MB · 26 req
  • script 24.9% 764 kB · 60 req
  • stylesheet 2.8% 87.3 kB · 2 req
  • font 2% 61.5 kB · 4 req
  • document 1.1% 32.4 kB · 3 req
  • other 0.2% 5.4 kB · 6 req

Third parties 3 entities

574 kB transferred, 173 ms on the main thread.

awswaf.com script 314 kB · 89 ms CPU
Stripe script 257 kB · 84 ms CPU
Cloudflare CDN 3.3 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.39 s 3.39 s 3.39 s
Long Tasks 11 11 11
DOM Elements 989 989 989
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 18 18 18
A11y Failures 5 5 5
A11y Failing Nodes 11 11 11

Main thread work

other 1.24 s
script evaluation 1.02 s
style layout 584 ms
script parse compile 244 ms
parse HTML 157 ms
paint composite render 94 ms
garbage collection 56 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 8 rules, 1047 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • moderate heading-order — Heading levels should only increase by one 5 nodes
  • moderate landmark-main-is-top-level — Main landmark should not be contained in another landmark 5 nodes
  • critical button-name — Buttons must have discernible text 3 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • serious html-has-lang — <html> element must have a lang attribute 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
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 5 of 19 audits

  • heading-order — Heading elements are not in a sequentially-descending order 5 nodes
  • button-name — Buttons do not have an accessible name 3 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
  • html-has-lang — `<html>` element does not have a `[lang]` attribute 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 31, 2026, 9:05 PM UTC 73 3.69 s 0 600 ms 3.27 MB 3/3 ±7 2,481 0% 86.2s