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 ·

gittings.studio

https://gittings.studio/

97 96 96 100 –CWV 25AXE

Data from Aug 20, 2026, 11:33 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 3.1.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Scores

97
Performance
no change
96
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 2.41 s — — 2.41 s 2.41 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 93 ms — — 93 ms 93 ms
FCP First Contentful Paint 789 ms — — 789 ms 789 ms
Speed Index 789 ms — — 789 ms 789 ms
TTFB Time to First Byte 609 ms — — 609 ms 609 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 71 ms
time to first byte 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.11 MB — — 1.11 MB 1.11 MB
Requests 14 — — 14 14
Third-party Weight 169.6 kB — — 169.6 kB 169.6 kB
Third-party CPU 50 ms — — 50 ms 50 ms
Unused JS 73.8 kB — — 73.8 kB 73.8 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 655.0 kB · 3 req
font 267.5 kB · 3 req
script 170.4 kB · 4 req
document 7.3 kB · 1 req
stylesheet 5.7 kB · 1 req
other 534 B · 1 req
third party 169.6 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 169.6 kB · 50 ms CPU

Page health

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

Main thread work

script evaluation 172 ms
other 110 ms
style layout 46 ms
script parse compile 44 ms
parse HTML 11 ms
paint composite render 9 ms
garbage collection 9 ms

Axe violations axe-core 4.13.0, full rule set

25 violating nodes across 1 rule, 337 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 25 nodes

Accessibility failures 1 of 23 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. 25 nodes

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 20, 2026, 11:33 PM UTC 97 2.41 s 0 93 ms 1.11 MB 3/3 ±10 2,351 24.8s

Embed this score

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