digitalocean.com
Data from Aug 23, 2026, 1:31 PM UTC 8h old
Web Hosts #2 · 3 measurements · since Aug 21, 2026
Core Web Vitals field data, url-level
Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 7.74 s.
-
967 ms
-
1.93 s
-
2.90 s
-
3.87 s
-
4.83 s
-
5.80 s
-
6.77 s
-
7.74 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 5.11 s | 3.47 s | ↑ +1647 ms (+47.5%) significant | 3.47 s | 5.11 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 1.76 s | 2.16 s | ↓ -397 ms (-18.4%) | 1.70 s | 2.16 s | |
| FCP First Contentful Paint | 1.06 s | 1.07 s | ↓ -2 ms (-0.2%) | 1.06 s | 1.07 s | |
| Speed Index | 4.45 s | 4.99 s | ↓ -549 ms (-11%) | 4.45 s | 5.44 s | |
| TTFB Time to First Byte | 614 ms | 617 ms | ↓ -3 ms (-0.5%) | 613 ms | 617 ms |
What LCP is made of observed, unthrottled
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 5.11 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.
Field data Chrome UX Report, url-level
Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 2.06 s | good | 82.8% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 198 ms | good | 75.1% good |
| CLS CWV | 0 | good | 95.8% good |
| FCP | 1.93 s | needs-improvement | 72.1% good |
| TTFB | 1.02 s | needs-improvement | 65.1% good |
Lab vs field
Lab LCP 5.11 s · field p75 2.06 s · real users are 0.4× 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 | 2.04 s | 198 ms | 0 | 1.92 s | 1.03 s |
| 2026-08-08 | 2.04 s | 198 ms | 0 | 1.92 s | 1.04 s |
| 2026-08-01 | 2.05 s | 200 ms | 0 | 1.90 s | 1.04 s |
| 2026-07-25 | 2.06 s | 202 ms | 0 | 1.89 s | 1.07 s |
| 2026-07-18 | 2.04 s | 201 ms | 0 | 1.84 s | 1.06 s |
| 2026-07-11 | 2.04 s | 196 ms | 0 | 1.82 s | 1.06 s |
| 2026-07-04 | 2.03 s | 195 ms | 0 | 1.82 s | 1.08 s |
| 2026-06-27 | 2.00 s | 194 ms | 0 | 1.79 s | 1.06 s |
| 2026-06-20 | 2.04 s | 195 ms | 0 | 1.82 s | 1.08 s |
| 2026-06-13 | 2.10 s | 196 ms | 0 | 1.85 s | 1.11 s |
| 2026-06-06 | 2.18 s | 201 ms | 0 | 1.88 s | 1.10 s |
| 2026-05-30 | 2.28 s | 204 ms | 0 | 1.93 s | 1.10 s |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 2.68 MB | 2.68 MB | ↓ -2.1 kB (-0.1%) | 2.68 MB | 2.68 MB | |
| Requests | 170 | 171 | ↓ -1 (-0.6%) | 168 | 171 | |
| Third-party Weight | 992 kB | 991 kB | ↑ +618 B (+0.1%) | 991 kB | 992 kB | |
| Third-party CPU | 390 ms | 411 ms | ↓ -20 ms (-5%) | 371 ms | 411 ms | |
| Unused JS | 626 kB | 626 kB | ↑ +513 B (+0.1%) | 626 kB | 637 kB | |
| Unused CSS | 0 B | 0 B | → no change | 0 B | 0 B |
By resource type
Third parties 10 entities
992 kB transferred, 390 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 | 31.51 s | 29.28 s | ↑ +2233 ms (+7.6%) | 26.73 s | 31.51 s | |
| Long Tasks | 20 | 20 | → no change | 20 | 20 | |
| DOM Elements | 1,487 | 1,487 | → no change | 1,487 | 1,487 | |
| A11y Failures | 2 | 2 | → no change | 2 | 2 | |
| A11y Failing Nodes | 2 | 2 | → no change | 2 | 2 |
Main thread work
Axe violations axe-core , full rule set
The axe run failed: Navigation timeout of 120000 ms exceeded
Accessibility failures 2 of 32 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. 1 node -
landmark-one-main— Document does not have a main landmark. 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 23, 2026, 1:31 PM UTC | 52 | 5.11 s | 0 | 1.76 s | 2.68 MB | 3/3 | ±21 | 2,385 | 311.6s |
| Aug 22, 2026, 12:41 PM UTC | 59 | 3.47 s | 0 | 2.16 s | 2.68 MB | 3/3 | ±17 | 2,279 | 315.6s |
| Aug 21, 2026, 11:37 AM UTC | 57 | 3.91 s | 0 | 1.70 s | 2.68 MB | 3/3 | ±11 | 2,499 | 309.4s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
digitalocean.com's scores, updated whenever this instance
re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.digitalocean.com/"></speedlify2-score>