speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

hidegh.github.io/jamstack-eleventy-custom

https://hidegh.github.io/jamstack-eleventy-custom

Data from Aug 20, 2026, 11:39 PM UTC — 18h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 18h

This URL redirects to https://reflectivetechconsulting.com/jamstack-eleventy-custom.

Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

GitHub Pages Hosted by GitHub Pages

Scores

65
Performance
no change
76
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.09 s — — 6.09 s 6.09 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 5.19 s — — 5.19 s 5.19 s
Speed Index 5.19 s — — 5.19 s 5.19 s
TTFB Time to First Byte 612 ms — — 612 ms 612 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 302 ms
time to first byte 31 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 541.1 kB — — 541.1 kB 541.1 kB
Requests 46 — — 46 46
Third-party Weight 540.7 kB — — 540.7 kB 540.7 kB
Third-party CPU 33 ms — — 33 ms 33 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 73.1 kB — — 73.1 kB 73.1 kB

By resource type

font 195.0 kB · 4 req
script 113.2 kB · 15 req
stylesheet 108.9 kB · 11 req
other 70.9 kB · 4 req
image 36.6 kB · 1 req
document 16.6 kB · 1 req
third party 370.2 kB · 26 req

Third parties 4 entities

540.7 kB transferred, 33 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Cloudflare CDN 216.9 kB · 6 ms CPU
reflectivetechconsulting.com 170.6 kB · 18 ms CPU
JSDelivr CDN 107.6 kB · 10 ms CPU
Google Fonts 45.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.86 s — — 1.86 s 1.86 s
Long Tasks 2 — — 2 2
DOM Elements 1,029 — — 1,029 1,029
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 80 — — 80 80
A11y Failures 9 — — 9 9
A11y Failing Nodes 80 — — 80 80

Main thread work

paint composite render 614 ms
other 540 ms
style layout 314 ms
script evaluation 266 ms
parse HTML 72 ms
script parse compile 44 ms
garbage collection 10 ms

Axe violations axe-core 4.13.0, full rule set

80 violating nodes across 10 rules, 2349 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 43 nodes
  • serious aria-progressbar-name — ARIA progressbar nodes must have an accessible name 14 nodes
  • critical button-name — Buttons must have discernible text 11 nodes
  • moderate heading-order — Heading levels should only increase by one 6 nodes
  • serious aria-command-name — ARIA commands must have an accessible name 1 node
  • critical aria-required-children — Certain ARIA roles must contain particular children 1 node
  • critical image-alt — Images must have alternative text 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious link-name — Links must have discernible text 1 node
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 1 node

Accessibility failures 9 of 36 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 43 nodes
  • aria-progressbar-name — ARIA `progressbar` elements do not have accessible names. 14 nodes
  • button-name — Buttons do not have an accessible name 11 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 6 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 2 nodes
  • aria-command-name — `button`, `link`, and `menuitem` elements do not have accessible names. 1 node
  • image-alt — Image elements do not have `[alt]` attributes 1 node
  • link-name — Links do not have a discernible name 1 node
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 11:39 PM UTC 65 6.09 s 0.001 0 ms 541.1 kB 3/3 ±3 2,322 32s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show hidegh.github.io/jamstack-eleventy-custom's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site! 

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://hidegh.github.io/jamstack-eleventy-custom"></speedlify-score>