vitraggroup.com
Data from Aug 21, 2026, 8:45 AM UTC — 10h old.
11ty Emeritus · 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-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 3.12 s | — | — | 3.12 s | 3.12 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 375 ms | — | — | 375 ms | 375 ms | |
| FCP First Contentful Paint | 921 ms | — | — | 921 ms | 921 ms | |
| Speed Index | 1.49 s | — | — | 1.49 s | 1.49 s | |
| TTFB Time to First Byte | 621 ms | — | — | 621 ms | 621 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 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 | — | — | — | — | — |
| 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.16 MB | — | — | 1.16 MB | 1.16 MB | |
| Requests | 44 | — | — | 44 | 44 | |
| Third-party Weight | 746.1 kB | — | — | 746.1 kB | 746.1 kB | |
| Third-party CPU | 121 ms | — | — | 121 ms | 121 ms | |
| Unused JS | 222.2 kB | — | — | 222.2 kB | 222.2 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 5 entities
746.1 kB transferred, 121 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 | 1.75 s | — | — | 1.75 s | 1.75 s | |
| Long Tasks | 6 | — | — | 6 | 6 | |
| DOM Elements | 320 | — | — | 320 | 320 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 553 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.
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:45 AM UTC | 85 | 3.12 s | 0 | 375 ms | 1.16 MB | 3/3 | ±39 | 2,824 | 30.7s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
vitraggroup.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://vitraggroup.com/"></speedlify-score>