pauguerrero.com/en
Data from Aug 21, 2026, 6:44 AM UTC — 12h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 12h
https://pauguerrero.com/en/.
A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.
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.58 s | — | — | 2.58 s | 2.58 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.35 s | — | — | 1.35 s | 1.35 s | |
| Speed Index | 2.74 s | — | — | 2.74 s | 2.74 s | |
| TTFB Time to First Byte | 750 ms | — | — | 750 ms | 750 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 | 146.2 kB | — | — | 146.2 kB | 146.2 kB | |
| Requests | 10 | — | — | 10 | 10 | |
| Third-party Weight | 4.7 kB | — | — | 4.7 kB | 4.7 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
4.7 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 | 151 ms | — | — | 151 ms | 151 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 86 | — | — | 86 | 86 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 182 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.
-
moderate
page-has-heading-one— Page should contain a level-one heading 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, 6:44 AM UTC | 96 | 2.58 s | 0 | 0 ms | 146.2 kB | 3/3 | ±3 | 2,479 | 26.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
pauguerrero.com/en'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://pauguerrero.com/en"></speedlify-score>