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 and Bluesky.
Last updated ago. 1,763 measurements in the last week.

Charts Compare Measurement runs Embed a score Open to Work

statisweb.pages.dev

https://statisweb.pages.dev/

84PERF 85A11Y 100BEST 100SEO ✗AXE –CWV

Ranks Overall #1,536 Build Awesome Starters #156

Data from Nov 17, 2026, 11:01 PM UTC old Measured once a week · 13 runs since Aug 21, 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 3,957, 59% faster than this project's median of 2,493. 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

Eleventy 2.0.1 Built with Eleventy 2.0.1
Cloudflare Hosted by Cloudflare
Rendered At build time Eleventy builds static pages

Lighthouse Scores LAB Simulated

84
Performance
no change
85
Accessibility
no change
100
Best Practices
no change
100
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 1.75 s good ↑ +40 ms (+2.3%) 1.71 s – 3.23 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.293 poor ↓ -0.006 (-2%) 0 – 0.299
TBT Total Blocking Time 0 ms good → no change 0 ms – 0 ms
FCP First Contentful Paint 1.75 s good ↑ +40 ms (+2.3%) 1.71 s – 3.23 s
Speed Index 1.75 s good ↑ +40 ms (+2.3%) 1.71 s – 3.31 s
TTFB Time to First Byte 684 ms good ↑ +188 ms (+37.9%) 465 ms – 684 ms
RTT Round-trip time to the server — field only, and ungraded: Google publishes no threshold for it n/a —

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 144 ms
time to first byte 96 ms

Page weight

Metric Value Change / range Trend
Page Weight 111 kB ↓ -170 B (-0.2%) 111 kB – 122 kB
Requests 8 → no change 8 – 8
Third-party Weight 107 kB ↓ -9 B 107 kB – 117 kB
Third-party CPU 2 ms ↓ -0 ms (-14.3%) significant 0 ms – 2 ms
Unused JS 0 B → no change 0 B – 0 B
Unused CSS 19.5 kB → no change 19.5 kB – 29.3 kB

By resource type

Type Transfer Share Size Requests
font 74.9% 83.3 kB 2
stylesheet 20.5% 22.8 kB 4
document 3.1% 3.4 kB 1
other 1.5% 1.7 kB 1
Total 111 kB 8

Third parties 3 entities

Entity Transfer Size Main thread Simulated
Google Fonts font 84.6 kB 0 ms
JSDelivr CDN stylesheet 20.5 kB 2 ms
11ty.dev 1.7 kB 0 ms
Total 107 kB 2 ms

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.

Page health

Metric Value Change / range Trend
Main Thread Work 143 ms ↓ -38 ms (-20.8%) significant 143 ms – 220 ms
Long Tasks 0 → no change 0 – 0
DOM Elements 114 → no change 114 – 114
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 14 → no change 14 – 14
A11y Failures 2 → no change 2 – 2
A11y Failing Nodes 10 → no change 10 – 10

Main thread work

Task Time Share Duration Simulated
other 48% 69 ms
style layout 32% 46 ms
parse HTML 8% 12 ms
script evaluation 6% 8 ms
paint composite render 5% 8 ms
script parse compile 0% 1 ms
Total 143 ms

Axe violations axe-core 4.14.0, full rule set

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

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 8 nodes
    Offending elements (5 of 8)
    1. .nav-item-active
      <a class="p-1 nav-item nav-item-active text-white linki" href="/">Home</a>
    2. .p-1.nav-item[href$="posts/"]
      <a class="p-1 nav-item text-white linki" href="/posts/">Blog</a>
    3. a[href$="template/"]
      <a class="p-1 nav-item text-white linki" href="/template/">Themes</a>
    4. .p-1.nav-item.linki:nth-child(4)
      <a class="p-1 nav-item text-white linki" href="https://github.com/mesinkasir/cool11ty">
    5. header > .danger.btn.text-white
      <a href="https://github.com/mesinkasir/cool11ty/archive/refs/heads/master.zip" class="btn danger text-white">
  • moderate region — All page content should be contained by landmarks 4 nodes
    Offending elements
    1. .mt-5 > .col-md-4
      <div class="col-md-4"> <div class="p-3 danger text-center"> <div class="p-3 black images"> <h1 class="title">11</h1> </div> <p class="p-3 text-white">Saat nya menggunakan eleventy 11ty dalam pengemba…
    2. .row:nth-child(3)
      <div class="row p-3">
    3. .row.mt-3
      <div class="row p-3 mt-3">
    4. .container > .col-md-12.text-center
      <div class="col-md-12 p-3 text-center"> <a href="https://www.hockeycomputindo.com/en/jamstack/" class="btn danger text-white col-md-2 col-12">👉 HIRE ME 👈</a> </div>
  • moderate heading-order — Heading levels should only increase by one 2 nodes
    Offending elements
    1. .col-md-3:nth-child(1) > h4
      <h4>Kecepatan</h4>
    2. a[href$="whyeleventy/"] > .mt-3
      <h4 class="mt-3"> Why Eleventy</h4>

Accessibility failures 2 of 11 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 8 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes

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 RunsSpreadBenchLighthouseTook Archive
Nov 17, 2026, 11:01 PM UTC 84 1.75 s 0.293 0 ms 111 kB 3/3 ±13 3,957 +59% 13.6.0 23s Wayback
Nov 10, 2026, 5:59 PM UTC 84 1.71 s 0.299 0 ms 111 kB 3/3 ±0 2,478 -1% 13.6.0 22.3s Wayback
Nov 3, 2026, 3:54 PM UTC 86 3.23 s 0 0 ms 121 kB 3/3 ±4 2,486 0% 13.4.1 24s Wayback
Oct 26, 2026, 4:33 PM UTC 74 3.00 s 0.293 0 ms 120 kB 3/3 ±1 2,900 +16% 13.4.1 21.5s Wayback
Oct 19, 2026, 12:17 PM UTC 76 2.79 s 0.293 0 ms 120 kB 3/3 ±2 2,457 -1% 13.4.1 23.1s Wayback
Oct 12, 2026, 8:42 AM UTC 83 1.89 s 0.293 0 ms 120 kB 3/3 ±5 4,190 +68% 13.4.1 19.8s Wayback
Oct 4, 2026, 10:49 PM UTC 77 2.74 s 0.293 0 ms 120 kB 3/3 ±3 3,079 +24% 13.4.1 20.1s Wayback
Sep 27, 2026, 8:59 PM UTC 83 1.91 s 0.293 0 ms 120 kB 3/3 ±4 2,434 -2% 13.4.1 23.9s Wayback
Sep 20, 2026, 6:05 PM UTC 75 2.94 s 0.293 0 ms 120 kB 3/3 ±3 2,474 -1% 13.4.1 21.9s Wayback
Sep 13, 2026, 5:23 PM UTC 75 2.91 s 0.293 0 ms 120 kB 3/3 ±2 2,470 -1% 13.4.1 21.6s Wayback
Sep 6, 2026, 2:02 PM UTC 75 2.90 s 0.293 0 ms 120 kB 3/3 ±4 2,490 0% 13.4.1 21.5s Wayback
Aug 30, 2026, 1:35 PM UTC 73 3.05 s 0.293 0 ms 122 kB 3/3 ±1 2,406 -4% 13.4.1 21.6s Wayback
Aug 21, 2026, 3:52 PM UTC 83 1.92 s 0.293 0 ms 120 kB 3/3 ±3 2,308 -7% 13.4.1 23s Wayback

Embed this score

Use this web component to show statisweb.pages.dev'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://statisweb.pages.dev/"></speedlify2-score>