ninerakes.com
Data from Aug 21, 2026, 4:44 AM UTC — 13h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 13h
https://www.ninerakes.com/.
Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.
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.35 s | — | — | 2.35 s | 2.35 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.70 s | — | — | 1.70 s | 1.70 s | |
| Speed Index | 1.70 s | — | — | 1.70 s | 1.70 s | |
| TTFB Time to First Byte | 620 ms | — | — | 620 ms | 620 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 72.3 kB | — | — | 72.3 kB | 72.3 kB | |
| Requests | 10 | — | — | 10 | 10 | |
| Third-party Weight | 12.5 kB | — | — | 12.5 kB | 12.5 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
Third parties 2 entities
12.5 kB transferred, 2 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 | 162 ms | — | — | 162 ms | 162 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 90 | — | — | 90 | 90 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 2 | — | — | 2 | 2 | |
| A11y Failures | 2 | — | — | 2 | 2 | |
| A11y Failing Nodes | 2 | — | — | 2 | 2 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
2 violating nodes across 2 rules, 27 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 1 node -
moderate
page-has-heading-one— Page should contain a level-one heading 1 node
Accessibility failures 2 of 11 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.
-
meta-viewport— `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node -
landmark-one-main— Document does not have a main landmark. 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:44 AM UTC | 97 | 2.35 s | 0 | 0 ms | 72.3 kB | 2/3 | ±0 | 4,468 | 19.1s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
ninerakes.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://ninerakes.com/"></speedlify-score>