vpnclear.com
Data from Aug 21, 2026, 8:46 AM UTC — 10h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 10h
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.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 2.62 s | — | — | 2.62 s | 2.62 s | |
| CLS Cumulative Layout Shift | 0.082 | — | — | 0.082 | 0.082 | |
| TBT Total Blocking Time | 285 ms | — | — | 285 ms | 285 ms | |
| FCP First Contentful Paint | 2.47 s | — | — | 2.47 s | 2.47 s | |
| Speed Index | 3.86 s | — | — | 3.86 s | 3.86 s | |
| TTFB Time to First Byte | 471 ms | — | — | 471 ms | 471 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.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.85 s | good | 81.6% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 277 ms | needs-improvement | 57.1% good |
| CLS CWV | 0.090 | good | 76.4% good |
| FCP | 1.85 s | needs-improvement | 73.6% good |
| TTFB | 1.15 s | needs-improvement | 63% good |
Lab vs field
Lab LCP 2.62 s · field p75 1.85 s · real users are 0.71× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-15 | 1.86 s | 261 ms | 0.100 | 1.86 s | 1.15 s |
| 2026-08-08 | — | — | — | — | — |
| 2026-08-01 | — | — | — | — | — |
| 2026-07-25 | — | — | — | — | — |
| 2026-07-18 | — | — | — | — | — |
| 2026-07-11 | — | — | — | — | — |
| 2026-07-04 | — | — | — | — | — |
| 2026-06-27 | — | — | — | — | — |
| 2026-06-20 | — | — | — | — | — |
| 2026-06-13 | — | — | — | — | — |
| 2026-06-06 | — | — | — | — | — |
| 2026-05-30 | — | — | — | — | — |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 1.32 MB | — | — | 1.32 MB | 1.32 MB | |
| Requests | 104 | — | — | 104 | 104 | |
| Third-party Weight | 684.9 kB | — | — | 684.9 kB | 684.9 kB | |
| Third-party CPU | 221 ms | — | — | 221 ms | 221 ms | |
| Unused JS | 354.2 kB | — | — | 354.2 kB | 354.2 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 7 entities
684.9 kB transferred, 221 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 | 2.89 s | — | — | 2.89 s | 2.89 s | |
| Long Tasks | 6 | — | — | 6 | 6 | |
| DOM Elements | 367 | — | — | 367 | 367 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 14 | — | — | 14 | 14 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 13 | — | — | 13 | 13 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
14 violating nodes across 1 rule, 665 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 14 nodes
Accessibility failures 1 of 27 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
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, 8:46 AM UTC | 84 | 2.62 s | 0.082 | 285 ms | 1.32 MB | 3/3 | ±44 | 2,830 | 98.3s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
vpnclear.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://vpnclear.com/"></speedlify-score>