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 ·

scottmurphytennis.net

https://www.scottmurphytennis.net/

99 100 96 100 CWV 0AXE

Data from Aug 21, 2026, 6:39 PM UTC — 33m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 33m

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 2.0.1 Built with Eleventy 2.0.1
Netlify Hosted by Netlify

Scores

99
Performance
no change
100
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

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

Page weight

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

By resource type

image 1.70 MB · 10 req
script 913.7 kB · 8 req
font 112.4 kB · 3 req
stylesheet 76.0 kB · 5 req
document 63.1 kB · 2 req
other 39.6 kB · 10 req
third party 1.18 MB · 25 req

Third parties 3 entities

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

Unpkg 59.4 kB · 0 ms CPU
Google Fonts 27.2 kB · 0 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU

Page health

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

Main thread work

other 283 ms
style layout 131 ms
script evaluation 56 ms
paint composite render 37 ms
parse HTML 22 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 231 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.

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 21, 2026, 6:39 PM UTC 99 1.68 s 0.002 0 ms 2.91 MB 3/3 ±4 2,385 28.1s
Aug 21, 2026, 11:34 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 23.6s

Embed this score

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