myclientwants.com
Data from Aug 21, 2026, 4:48 AM UTC — 13h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 13h
https://www.myclientwants.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 | 3.82 s | — | — | 3.82 s | 3.82 s | |
| CLS Cumulative Layout Shift | 0.185 | — | — | 0.185 | 0.185 | |
| TBT Total Blocking Time | 5 ms | — | — | 5 ms | 5 ms | |
| FCP First Contentful Paint | 2.14 s | — | — | 2.14 s | 2.14 s | |
| Speed Index | 4.33 s | — | — | 4.33 s | 4.33 s | |
| TTFB Time to First Byte | 612 ms | — | — | 612 ms | 612 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 | 9.51 MB | — | — | 9.51 MB | 9.51 MB | |
| Requests | 692 | — | — | 692 | 692 | |
| Third-party Weight | 37.4 kB | — | — | 37.4 kB | 37.4 kB | |
| Third-party CPU | 33 ms | — | — | 33 ms | 33 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 24.0 kB | — | — | 24.0 kB | 24.0 kB |
By resource type
Third parties 3 entities
37.4 kB transferred, 33 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 | 4.05 s | — | — | 4.05 s | 4.05 s | |
| Long Tasks | 5 | — | — | 5 | 5 | |
| DOM Elements | 568 | — | — | 568 | 568 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 51 | — | — | 51 | 51 | |
| A11y Failures | 7 | — | — | 7 | 7 | |
| A11y Failing Nodes | 27 | — | — | 27 | 27 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
51 violating nodes across 9 rules, 549 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 15 nodes -
moderate
region— All page content should be contained by landmarks 15 nodes -
critical
image-alt— Images must have alternative text 10 nodes -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 3 nodes -
serious
frame-title— Frames must have an accessible name 2 nodes -
serious
list— <ul> and <ol> must only directly contain <li>, <script> or <template> elements 2 nodes -
moderate
meta-viewport— Zooming and scaling must not be disabled 2 nodes -
serious
html-has-lang— <html> element must have a lang attribute 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
Accessibility failures 7 of 20 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. 13 nodes -
image-alt— Image elements do not have `[alt]` attributes 7 nodes -
list— Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 2 nodes -
meta-viewport— `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 2 nodes -
frame-title— `<frame>` or `<iframe>` elements do not have a title 1 node -
html-has-lang— `<html>` element does not have a `[lang]` attribute 1 node -
link-name— Links do not have a discernible name 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:48 AM UTC | 76 | 3.82 s | 0.185 | 5 ms | 9.51 MB | 3/3 | ±6 | 2,491 | 241.1s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
myclientwants.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://myclientwants.com/"></speedlify-score>