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 ·

mina.codes

https://mina.codes/

97 100 100 100 –CWV 3AXE

Data from Aug 21, 2026, 4:56 PM UTC — 2h old.

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

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
Netlify Hosted by Netlify

Scores

97
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.03 s — — 2.03 s 2.03 s
CLS Cumulative Layout Shift 0.015 — — 0.015 0.015
TBT Total Blocking Time 125 ms — — 125 ms 125 ms
FCP First Contentful Paint 1.58 s — — 1.58 s 1.58 s
Speed Index 1.58 s — — 1.58 s 1.58 s
TTFB Time to First Byte 670 ms — — 670 ms 670 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 118 ms
time to first byte 71 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 367.7 kB — — 367.7 kB 367.7 kB
Requests 22 — — 22 22
Third-party Weight 173.1 kB — — 173.1 kB 173.1 kB
Third-party CPU 68 ms — — 68 ms 68 ms
Unused JS 70.0 kB — — 70.0 kB 70.0 kB
Unused CSS 11.0 kB — — 11.0 kB 11.0 kB

By resource type

script 180.6 kB · 3 req
font 159.3 kB · 5 req
stylesheet 15.3 kB · 3 req
document 6.5 kB · 1 req
image 3.5 kB · 3 req
other 2.4 kB · 6 req
third party 173.1 kB · 3 req

Third parties 3 entities

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

Google Tag Manager 171.8 kB · 68 ms CPU
Unpkg 1.2 kB · 0 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 263 ms
other 152 ms
style layout 79 ms
script parse compile 44 ms
paint composite render 14 ms
parse HTML 13 ms
garbage collection 12 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 154 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
  • moderate page-has-heading-one — Page should contain a level-one heading 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 21, 2026, 4:56 PM UTC 97 2.03 s 0.015 125 ms 367.7 kB 2/3 ±0 2,473 25.7s
Aug 21, 2026, 4:47 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 21.7s

Embed this score

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