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

eleventy-kickstart-blog.vercel.app

https://eleventy-kickstart-blog.vercel.app/

69PERF 89A11Y 100BEST 91SEO ✗AXE –CWV

Ranks Overall #1,555 Build Awesome Starters #162

Data from Oct 3, 2026, 1:06 PM 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

The measuring machine was faster than most in this project.

Lighthouse benchmark index was 4,160, 67% faster than this project's median of 2,486. CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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

Stack

Uses Font AwesomeFont Awesome
Vercel Hosted by Vercel

Lighthouse Scores LAB Simulated

69
Performance
no change
89
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 14.59 s poor ↓ -16 ms (-0.1%) 14.28 s – 14.75 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0 good → no change 0 – 0
TBT Total Blocking Time 26 ms good ↓ -47 ms (-64.4%) 0 ms – 586 ms
FCP First Contentful Paint 3.04 s poor ↓ -16 ms (-0.5%) 3.03 s – 4.55 s
Speed Index 3.21 s good ↑ +57 ms (+1.8%) 3.03 s – 5.18 s
TTFB Time to First Byte 641 ms good ↓ -16 ms (-2.4%) 630 ms – 671 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 1.20 s
resource load delay 145 ms
resource load duration 35 ms
time to first byte 21 ms

Page weight

Metric Value Change / range Trend
Page Weight 2.62 MB ↑ +1.1 kB 2.62 MB – 2.62 MB
Requests 11 → no change 10 – 11
Third-party Weight 172 kB ↑ +1.5 kB (+0.9%) 167 kB – 172 kB
Third-party CPU 43 ms ↓ -12 ms (-21.5%) 39 ms – 79 ms
Unused JS 72.0 kB ↑ +514 B (+0.7%) 69.0 kB – 73.2 kB
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
image 76.1% 1.99 MB 2
script 23.3% 612 kB 4
stylesheet 0.4% 9.9 kB 1
other 0.1% 3.1 kB 3
document 0.1% 2.6 kB 1
Total 2.62 MB 11

Third parties 3 entities

Entity Transfer Size Main thread Simulated
Google Tag Manager script 168 kB 37 ms
JSDelivr CDN 3.6 kB 6 ms
Google Analytics 48 B 0 ms
Total 172 kB 43 ms

Without JavaScript

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

Scripts disabled
As rendered

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

Page health

Metric Value Change / range Trend
Main Thread Work 1.16 s ↑ +517 ms (+80.7%) 641 ms – 1.92 s
Long Tasks 4 ↑ +1 (+33.3%) 3 – 5
DOM Elements 89 → no change 89 – 89
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 7 → no change 7 – 7
A11y Failures 2 → no change 2 – 2
A11y Failing Nodes 2 → no change 2 – 2

Main thread work

Task Time Share Duration Simulated
other 72% 833 ms
script evaluation 17% 196 ms
style layout 7% 77 ms
script parse compile 2% 25 ms
paint composite render 1% 12 ms
garbage collection 1% 8 ms
parse HTML 1% 8 ms
Total 1.16 s

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 3 rules, 127 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. #menu-drawer 
      <input id="menu-drawer" type="checkbox" class="drawer-toggle">
    2. select 
      <select class="select" onchange="changed()" data-choose-theme="">
    3. h1 
      <h1 class="mb-5 text-5xl">Hello there</h1>
    4. a[title="Posts"] > .ml-2 
      <span class="ml-2">Posts</span>
    5. a[title="Tags"] > .ml-2 
      <span class="ml-2">Tags</span>
  • moderate heading-order — Heading levels should only increase by one 1 node
    Offending element
    1. h3 
      <h3 class="font-semibold text-lg leading-tight truncate">Markdown</h3>
  • critical select-name — Select element must have an accessible name 1 node
    Offending element
    1. select 
      <select class="select" onchange="changed()" data-choose-theme="">

Accessibility failures 2 of 16 audits

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • select-name — Select elements do not have associated label elements. 1 node

Best Practices failures 1 of 18 audits

  • valid-source-maps — Missing source maps for large first-party JavaScript 1 item

SEO failures 1 of 8 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

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 3, 2026, 1:06 PM UTC 69 14.59 s 0 26 ms 2.62 MB 3/3 ±9 4,160 +67% 22s Wayback
Sep 26, 2026, 9:12 AM UTC 69 14.61 s 0 73 ms 2.62 MB 3/3 ±13 2,986 +20% 26.1s Wayback
Sep 19, 2026, 3:26 AM UTC 68 14.61 s 0 80 ms 2.62 MB 3/3 ±7 3,106 +25% 23.8s Wayback
Sep 12, 2026, 1:10 AM UTC 55 14.36 s 0 586 ms 2.62 MB 3/3 ±15 2,457 -1% 24.1s Wayback
Sep 4, 2026, 11:52 PM UTC 62 14.50 s 0 0 ms 2.62 MB 3/3 ±16 2,782 +12% 27.3s Wayback
Aug 28, 2026, 11:32 PM UTC 64 14.28 s 0 0 ms 2.62 MB 3/3 ±1 3,556 +43% 26.8s Wayback
Aug 20, 2026, 9:31 PM UTC 68 14.75 s 0 147 ms 2.62 MB 3/3 ±1 2,294 -8% 22.3s Wayback

Embed this score

Use this web component to show eleventy-kickstart-blog.vercel.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://eleventy-kickstart-blog.vercel.app/"></speedlify2-score>