mina.codes
Data from Aug 21, 2026, 4:56 PM UTC 2d old
Built Awesome #425 · 2 measurements · since Aug 21, 2026
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.
Scores
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 observed, unthrottled
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 2.03 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 368 kB | — | — | 368 kB | 368 kB | |
| Requests | 22 | — | — | 22 | 22 | |
| Third-party Weight | 173 kB | — | — | 173 kB | 173 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
Third parties 3 entities
173 kB transferred, 68 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
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
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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 21, 2026, 4:56 PM UTC | 97 | 2.03 s | 0.015 | 125 ms | 368 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 speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://mina.codes/"></speedlify2-score>