speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

developer.chrome.com

https://developer.chrome.com/

45PERF 93A11Y 77BEST 92SEO ✗AXE !CWV

Ranks Overall #1,763 Built Awesome #1,110

Data from Oct 3, 2026, 7:44 AM UTC old Measured once a week · 7 runs since Aug 20, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

Uses Lit 3.3.3Lit 3.3.3
Google Frontend Hosted by Google Frontend

Lighthouse Scores LAB Simulated

45
Performance
↓ -3 (-6.2%)
93
Accessibility
no change
77
Best Practices
no change
92
SEO
no change

Metrics LAB FIELD

Core Web Vitals: failing 3 of 3 assessed from real Chrome users.

Field figures are the p75 across real Chrome users over a 28-day trailing window (2026-09-04 → 2026-10-01), url-level.

Metric Lab Simulated Field
Value Change / range Trend p75 Distribution
LCP CWV Largest Contentful Paint 7.71 s poor ↑ +563 ms (+7.9%) significant 6.72 s – 7.71 s 3.08 s needs work 64.6% 19.4% 16.1%
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a — 297 ms needs work 58.4% 29.9% 11.7%
CLS CWV Cumulative Layout Shift 0.003 good → no change 0.003 – 0.003 0.020 good 86.8% 6.9% 6.3%
TBT Total Blocking Time 933 ms poor ↓ -187 ms (-16.7%) 582 ms – 1.12 s n/a —
FCP First Contentful Paint 3.89 s poor ↑ +1169 ms (+42.9%) 2.71 s – 3.90 s 3.01 s poor 45.3% 29.7% 25%
Speed Index 3.89 s needs work ↑ +956 ms (+32.6%) 2.82 s – 3.90 s n/a —
TTFB Time to First Byte 712 ms good ↓ -17 ms (-2.3%) 694 ms – 801 ms 1.87 s poor 20.7% 52.7% 26.6%

LCP Subparts LAB Unthrottled

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

element render delay 321 ms
time to first byte 247 ms

LCP LAB Simulated vs LCP FIELD

Lab 7.71 s
Field p75 3.08 s

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

Page weight

Metric Value Change / range Trend
Page Weight 1.86 MB ↑ +41.7 kB (+2.4%) 1.74 MB – 1.86 MB
Requests 68 ↓ -1 (-1.4%) 68 – 73
Third-party Weight 1.62 MB ↓ -169.3 kB (-9.7%) significant 1.61 MB – 1.79 MB
Third-party CPU 427 ms ↓ -63 ms (-12.9%) 298 ms – 490 ms
Unused JS 541 kB ↑ +3.3 kB (+0.6%) 526 kB – 541 kB
Unused CSS 135 kB → no change 134 kB – 135 kB

By resource type

Type Transfer Share Size Requests
script 66.7% 1.24 MB 42
image 14.6% 271 kB 11
font 8.9% 165 kB 2
stylesheet 8.7% 161 kB 3
document 1.1% 20.4 kB 1
other 0.1% 1.6 kB 9
Total 1.86 MB 68

Third parties 6 entities

Entity Transfer Size Main thread Simulated
Google Tag Manager script 798 kB 320 ms
Google CDN scriptstylesheet 628 kB 104 ms
Google Fonts font 169 kB 0 ms
Unpkg 15.7 kB 2 ms
Google/Doubleclick Ads 7.9 kB 1 ms
All 6 1.62 MB 427 ms

Page health

Metric Value Change / range Trend
Main Thread Work 3.39 s ↓ -503 ms (-12.9%) 2.52 s – 3.90 s
Long Tasks 11 → no change 10 – 11
DOM Elements 845 ↑ +8 (+1%) 828 – 845
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 29 ↑ +4 (+16%) 23 – 29
A11y Failures 2 → no change 2 – 2
A11y Failing Nodes 28 ↑ +4 (+16.7%) significant 22 – 28

Main thread work

Task Time Share Duration Simulated
script evaluation 50% 1.69 s
other 20% 680 ms
style layout 14% 467 ms
script parse compile 11% 363 ms
paint composite render 2% 77 ms
parse HTML 2% 61 ms
garbage collection 2% 56 ms
Total 3.39 s

Axe violations axe-core 4.13.0, full rule set

29 violating nodes across 3 rules, 966 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious link-name — Links must have discernible text 26 nodes
    Offending elements (5 of 26)
    1. .dcc-bg-grey.devsite-landing-row-item[description-position="bottom"]:nth-child(1) > .devsite-landing-row-item-media > figure > a
      <a href="https://developer.chrome.com/blog/chrome-at-io26">
    2. .dcc-bg-grey.devsite-landing-row-item[description-position="bottom"]:nth-child(2) > .devsite-landing-row-item-media > figure > a
      <a href="https://io.google/2026/?utm_source=web&utm_medium=embedded_marketing&utm_campaign=hpp_ondemand_card&utm_content=">
    3. .devsite-landing-row-4-up.devsite-landing-row-header-centered[background="grey"] > .devsite-landing-row-inner > .devsite-landing-row-group > .devsite-landing-row-item[description-position="bottom"]:nth-child(1) > .devsite-landing-row-item-media > figure > a
      <a href="https://developer.chrome.com/docs/ai">
    4. .devsite-landing-row-item[description-position="bottom"]:nth-child(1) > .devsite-landing-row-item-description > .devsite-landing-row-item-body > .devsite-landing-row-item-list > .devsite-landing-row-item-list-item:nth-child(1) > .devsite-landing-row-item-list-item-content[icon-position="left"] > a
      <a href="https://developer.chrome.com/docs/ai"> <div class="devsite-landing-row-item-list-item-icon-container" foreground="theme" size="small"> <div class="devsite-landing-row-item-list-item-icon mat…
    5. .devsite-landing-row-item[description-position="bottom"]:nth-child(1) > .devsite-landing-row-item-description > .devsite-landing-row-item-body > .devsite-landing-row-item-list > .devsite-landing-row-item-list-item:nth-child(2) > .devsite-landing-row-item-list-item-content[icon-position="left"] > a
      <a href="https://developer.chrome.com/docs/capabilities">
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
    Offending elements
    1. .dcc-bg-grey.devsite-landing-row-item[description-position="bottom"]:nth-child(1) > .devsite-landing-row-item-description > .devsite-landing-row-item-body > .devsite-landing-row-item-buttons > .button
      <a href="https://developer.chrome.com/blog/chrome-at-io26" class="button ">Find out more</a>
    2. .dcc-bg-grey.devsite-landing-row-item[description-position="bottom"]:nth-child(2) > .devsite-landing-row-item-description > .devsite-landing-row-item-body > .devsite-landing-row-item-buttons > .button
      <a href="https://io.google/2026/?utm_source=web&amp;utm_medium=embedded_marketing&amp;utm_campaign=hpp_ondemand_card&amp;utm_content=" class="button ">Watch here</a>
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node
    Offending element
    1. html
      <html lang="en" dir="ltr">

Accessibility failures 2 of 29 audits

  • link-name — Links do not have a discernible name 26 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 nodes

Best Practices failures 2 of 17 audits

  • third-party-cookies — Uses third-party cookies 1 item
  • inspector-issues — Issues were logged in the `Issues` panel in Chrome Devtools 1 item

SEO failures 1 of 10 audits

  • link-text — Links do not have descriptive text 1 item

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-09-26 3.06 s 295 ms 0.020 3.00 s 1.87 s
2026-09-19 3.05 s 295 ms 0.020 2.99 s 1.87 s
2026-09-12 3.08 s 295 ms 0.020 3.03 s 1.92 s
2026-09-05 3.07 s 295 ms 0.020 3.02 s 1.92 s
2026-08-29 3.07 s 296 ms 0.020 3.02 s 1.91 s
2026-08-22 3.06 s 290 ms 0.020 3.01 s 1.92 s
2026-08-15 3.01 s 284 ms 0.020 2.95 s 1.88 s
2026-08-08 3.02 s 281 ms 0.020 2.95 s 1.87 s
2026-08-01 2.99 s 279 ms 0.020 2.93 s 1.87 s
2026-07-25 3.00 s 284 ms 0.020 2.93 s 1.87 s
2026-07-18 2.98 s 287 ms 0.020 2.91 s 1.84 s
2026-07-11 2.99 s 290 ms 0.020 2.93 s 1.84 s

Runs

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 3, 2026, 7:44 AM UTC 45 7.71 s 0.003 933 ms 1.86 MB 3/3 ±6 2,323 -7% 40.3s Wayback
Sep 26, 2026, 3:48 AM UTC 48 7.15 s 0.003 1.12 s 1.81 MB 3/3 ±5 2,477 0% 42.2s Wayback
Sep 19, 2026, 3:19 AM UTC 55 6.98 s 0.003 582 ms 1.74 MB 3/3 ±2 2,951 +19% 37.5s Wayback
Sep 12, 2026, 1:03 AM UTC 50 7.24 s 0.003 981 ms 1.81 MB 3/3 ±0 2,513 +1% 41.5s Wayback
Sep 4, 2026, 11:45 PM UTC 49 6.72 s 0.003 773 ms 1.79 MB 3/3 ±2 2,787 +12% 40.1s Wayback
Aug 28, 2026, 11:26 PM UTC 57 7.09 s 0.003 594 ms 1.75 MB 3/3 ±11 3,323 +34% 37.3s Wayback
Aug 20, 2026, 8:38 PM UTC 50 7.03 s 0.003 1.00 s 1.74 MB 3/3 ±3 2,337 -6% 48.9s Wayback

Embed this score

Use this web component to show developer.chrome.com's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://developer.chrome.com/"></speedlify2-score>