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

jamstack-comments.netlify.app

https://jamstack-comments.netlify.app/

100PERF 97A11Y 100BEST 90SEO ✗AXE ✓CWV

Ranks Overall #1,250 Built Awesome #856

Data from Oct 3, 2026, 11:40 PM UTC old Measured once a week · 7 runs since Aug 21, 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

Netlify Hosted by Netlify

Lighthouse Scores LAB Simulated

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

Metrics LAB FIELD

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

Field figures are the p75 across real Chrome users over a 28-day trailing window (2026-08-23 → 2026-09-19), url-level. From the backfilled CrUX history rather than this measurement, which predates the API key.

Metric Lab Simulated Field
Value Change / range Trend p75 Distribution
LCP CWV Largest Contentful Paint 776 ms good ↓ -23 ms (-2.9%) 775 ms – 799 ms 1.44 s good 95.3% 2.9% 1.8%
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a — — —
CLS CWV Cumulative Layout Shift 0 good → no change 0 – 0 0 good 99% 1% 0%
TBT Total Blocking Time 0 ms good → no change 0 ms – 0 ms n/a —
FCP First Contentful Paint 776 ms good ↓ -23 ms (-2.9%) 775 ms – 799 ms — —
Speed Index 776 ms good ↓ -23 ms (-2.9%) 775 ms – 799 ms n/a —
TTFB Time to First Byte 608 ms good ↓ -20 ms (-3.2%) 608 ms – 633 ms — —

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 31 ms
time to first byte 10 ms

Page weight

Metric Value Change / range Trend
Page Weight 17.5 kB ↓ -9 B (-0.1%) 2.3 kB – 17.5 kB
Requests 2 → no change 1 – 2
Third-party Weight 0 B → no change 0 B – 0 B
Third-party CPU 0 ms → no change 0 ms – 0 ms
Unused JS 0 B → no change 0 B – 0 B
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
document 100% 2.3 kB 1
Total 17.5 kB 2

Page health

Metric Value Change / range Trend
Main Thread Work 79 ms ↓ -11 ms (-12.1%) 60 ms – 90 ms
Long Tasks 0 → no change 0 – 0
DOM Elements 33 → no change 33 – 33
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 6 → no change 6 – 6
A11y Failures 1 → no change 1 – 1
A11y Failing Nodes 1 → no change 1 – 1

Main thread work

Task Time Share Duration Simulated
other 65% 52 ms
style layout 17% 13 ms
script evaluation 10% 8 ms
parse HTML 3% 3 ms
paint composite render 3% 3 ms
script parse compile 2% 1 ms
Total 79 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 63 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • moderate region — All page content should be contained by landmarks 5 nodes
    Offending elements
    1. h1 
      <h1>Jamstack Comments Engine</h1>
    2. p:nth-child(3) 
      <p>This example site demonstrates a comments system build by combining form handling, serverless functions, and build triggers on Netlify. Try it out by exploring one of the pages listed below, and t…
    3. h2 
      <h2>Some pages with comments</h2>
    4. p:nth-child(5) 
      <p>There are some pages listed below which include comments. You can try adding a comment of your own, or just enjoy the delicious and insightful comments others have left there for you.</p>
    5. .listing 
      <ul class="listing">
  • moderate landmark-one-main — Document should have one main landmark 1 node
    Offending element
    1. html 
      <html lang="en">

Accessibility failures 1 of 13 audits

  • landmark-one-main — Document does not have a main landmark. 1 node

SEO failures 1 of 7 audits

  • meta-description — Document does not have a meta description

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 No data — 1 week under the CrUX reporting threshold
2026-09-19 1.44 s — 0 1.44 s 1.24 s
2026-09-12 1.43 s — 0 1.42 s 1.17 s
2026-09-05 1.47 s — 0 1.47 s 1.30 s
2026-08-29 1.48 s — 0 1.49 s 1.31 s
2026-08-22 1.49 s — 0 1.53 s 1.33 s
2026-08-15 1.58 s — 0 1.59 s 1.42 s
2026-08-08 1.49 s — 0 1.55 s 1.41 s
2026-08-01 1.49 s — 0 1.49 s 1.33 s
2026-07-25 1.45 s — 0 1.45 s 1.27 s
2026-07-18 1.37 s — 0 1.37 s 1.27 s
2026-07-11 1.42 s — 0 1.43 s 1.32 s

Runs

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 3, 2026, 11:40 PM UTC 100 776 ms 0 0 ms 17.5 kB 3/3 ±0 2,506 +1% 19.6s Wayback
Sep 26, 2026, 10:00 PM UTC 100 799 ms 0 0 ms 17.5 kB 3/3 ±0 2,486 0% 20.3s Wayback
Sep 19, 2026, 7:19 PM UTC 100 791 ms 0 0 ms 2.3 kB 3/3 ±0 2,354 -5% 20.3s Wayback
Sep 12, 2026, 6:16 PM UTC 100 775 ms 0 0 ms 2.3 kB 3/3 ±0 2,239 -10% 19.9s Wayback
Sep 5, 2026, 5:57 PM UTC 100 798 ms 0 0 ms 2.3 kB 3/3 ±0 2,498 0% 20.3s Wayback
Aug 29, 2026, 4:59 PM UTC 100 791 ms 0 0 ms 2.3 kB 3/3 ±0 2,488 0% 19.9s Wayback
Aug 21, 2026, 1:18 AM UTC 100 797 ms 0 0 ms 2.3 kB 3/3 ±0 3,403 +37% 18.9s Wayback

Embed this score

Use this web component to show jamstack-comments.netlify.app'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://jamstack-comments.netlify.app/"></speedlify2-score>