blog.sanketpathak.com
https://blog.sanketpathak.com/
Data from Aug 20, 2026, 7:19 PM UTC — 22h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 22h
https://www.sanketpathak.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 | 12.63 s | — | — | 12.63 s | 12.63 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 3.06 s | — | — | 3.06 s | 3.06 s | |
| Speed Index | 3.06 s | — | — | 3.06 s | 3.06 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 | 2.10 MB | — | — | 2.10 MB | 2.10 MB | |
| Requests | 12 | — | — | 12 | 12 | |
| Third-party Weight | 13.8 kB | — | — | 13.8 kB | 13.8 kB | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
13.8 kB transferred, 0 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 | 539 ms | — | — | 539 ms | 539 ms | |
| Long Tasks | 1 | — | — | 1 | 1 | |
| DOM Elements | 82 | — | — | 82 | 82 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 4 | — | — | 4 | 4 | |
| A11y Failures | 2 | — | — | 2 | 2 | |
| A11y Failing Nodes | 4 | — | — | 4 | 4 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
4 violating nodes across 2 rules, 82 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
link-name— Links must have discernible text 3 nodes -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 1 node
Accessibility failures 2 of 12 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.
-
link-name— Links do not have a discernible name 3 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 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 20, 2026, 7:19 PM UTC | 69 | 12.63 s | 0 | 0 ms | 2.10 MB | 3/3 | ±0 | 2,347 | 22s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
blog.sanketpathak.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://blog.sanketpathak.com/"></speedlify-score>