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 ·

jmhobbs.github.io

https://jmhobbs.github.io/

100 76 100 90 CWV 884AXE

Data from Aug 20, 2026, 11:35 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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.

Eleventy Built with Eleventy
GitHub Pages Hosted by GitHub Pages

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.03 s 1.03 s 1.03 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.03 s 1.03 s 1.03 s
Speed Index 1.03 s 1.03 s 1.03 s
TTFB Time to First Byte 602 ms 602 ms 602 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 77 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 19.1 kB 19.1 kB 19.1 kB
Requests 2 2 2
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

document 18.1 kB · 1 req
stylesheet 948 B · 1 req
third party 19.1 kB · 2 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 291 ms 291 ms 291 ms
Long Tasks 1 1 1
DOM Elements 3,772 3,772 3,772
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 884 884 884
A11y Failures 4 4 4
A11y Failing Nodes 302 302 302

Main thread work

style layout 122 ms
other 102 ms
paint composite render 31 ms
parse HTML 29 ms
script evaluation 9 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

884 violating nodes across 5 rules, 8213 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.

  • moderate region — All page content should be contained by landmarks 582 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 288 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 12 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 4 of 14 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.

  • link-in-text-block — Links rely on color to be distinguishable. 288 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 12 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • landmark-one-main — Document does not have a main landmark. 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:35 PM UTC 100 1.03 s 0 0 ms 19.1 kB 3/3 ±0 2,326 40.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show jmhobbs.github.io'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://jmhobbs.github.io/"></speedlify-score>