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 ·

mattdecamp.com

https://mattdecamp.com/

100 73 96 80 CWV 6AXE

Data from Aug 21, 2026, 4:37 AM UTC — 14h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 14h

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.

Netlify Hosted by Netlify

Scores

100
Performance
no change
73
Accessibility
no change
96
Best Practices
no change
80
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 790 ms 790 ms 790 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 790 ms 790 ms 790 ms
Speed Index 790 ms 790 ms 790 ms
TTFB Time to First Byte 628 ms 628 ms 628 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.

time to first byte 29 ms
element render delay 26 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 6.0 kB 6.0 kB 6.0 kB
Requests 3 3 3
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

other 4.4 kB · 2 req
document 1.6 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 65 ms 65 ms 65 ms
Long Tasks 0 0 0
DOM Elements 67 67 67
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 6 6
A11y Failures 4 4 4
A11y Failing Nodes 13 13 13

Main thread work

other 46 ms
style layout 8 ms
script evaluation 7 ms
paint composite render 3 ms
parse HTML 2 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 5 rules, 142 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 2 nodes
  • serious document-title — Documents must have <title> element to aid in navigation 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 10 nodes
  • document-title — Document doesn't have a `<title>` element 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 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 2 console errors

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 21, 2026, 4:37 AM UTC 100 790 ms 0 0 ms 6.0 kB 3/3 ±0 4,517 23s

Embed this score

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