Teardowns
One site per page: what actually makes it slow, what we measured before and after, and what you could fix yourself. Real sites, real Lighthouse runs, numbers you can re-check.
ProBlogger runs a caching plugin and still takes 11 seconds to paint its main image on mobile
ProBlogger runs W3 Total Cache, so its server answers fast. On a phone its largest image still lands at 11.3 seconds and it scores 58. The cache never touched the reason — 193 KB of unused CSS blocking the first paint and 848 KB of unused JavaScript. Here's the measurement and the fix.
58 → 97 PageSpeed mobile · 23 Jul 2026 nasa.gov · WordPressIn July 2026, NASA's homepage sent 18 MB to a phone — and two photographs were 12.8 of them
Measured July 2026: nasa.gov was a carefully built WordPress site — scripts deferred, images sized, 37 KB of CSS — that still took 34 seconds to finish drawing on a phone, because two photographs were requested at full resolution, twice each, from an image service that would have resized them on request. NASA has since rebuilt the page; the re-check is on the page.
64 → 71 PageSpeed mobile · 22 Jul 2026 duda.co · DudaDuda's own website takes 15 seconds to finish drawing on mobile
duda.co ships 26 MB to a phone, 92% of it autoplay video, and its largest element lands at 15.5 s — with the CPU idle the whole time. The markup, the headers, and the fixes.
67 → 68 PageSpeed mobile · 16 Aug 2026A site gets a teardown only when the answer is not obvious — a page whose story is “we deferred the analytics and compressed the images” already has one, and it's the audit showcase. Every page here names the audit it came from, the day it was measured, and what got worse as well as better.
Want the same breakdown for your site?
A free before / after PageSpeed comparison on mobile and desktop. No signup.
That doesn’t look like a website address. Enter a domain — for example example.com or https://example.com/page.
No signup. See your before/after PageSpeed score in about a minute.