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.
Tilda's own homepage weighs 0.7 MB and scores 62 on mobile. The weight is not where the points go
Measured October 2026: tilda.cc ships only 0.7 MB to a phone and blocks the main thread for 33 ms, yet scores 62 on mobile. A 30 KB preview image that is 20 pixels wide, a 100 KB icon library that draws no icons, and where the 38 lost points actually go.
62 → 68 PageSpeed mobile · 2 Oct 2026 divi-tutorials.com · DiviIn September 2026, divi-tutorials.com held back its own scripts with WP Rocket. The Twitch player in its hero loaded 76 more
Measured September 2026: divi-tutorials.com runs WP Rocket with delayed JavaScript, and only 7 of its own scripts load. A Twitch embed in the hero accounts for 117 of 167 mobile requests and 76 scripts no plugin can reach. And the 768px copy of one image weighs 6.8 times the full-size file.
32 → 64 PageSpeed mobile · 29 Sept 2026 squarespace.com · SquarespaceIn October 2026, Squarespace's homepage downloaded most of its hero videos in every format it had
Measured October 2026: squarespace.com scores 30 on mobile PageSpeed. A phone fetched four of its five hero clips as both WebM and MP4, a desktop fetched them in all four encodings, and the hero image sat downloaded for 5.4 s before it was drawn. The markup, the headers, and what moved through our proxy (not much).
30 → 35 PageSpeed mobile · 3 Oct 2026 1c-bitrix.ru · Bitrix1C-Bitrix serves its own homepage from a file cache, and a phone still waits 6.3 seconds for the first pixel
Measured September 2026: the 1C-Bitrix homepage comes out of an nginx file cache with every script already moved to the end of the body, and still takes 6.3 s to paint anything on mobile. Fourteen stylesheets, two images that weigh half the page, and a realtime client loaded for visitors it does not serve. The markup, the headers, and the fixes.
59 → 75 PageSpeed mobile · 25 Sept 2026 problogger.com · WordPressProBlogger 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 · DudaIn August 2026, Duda's own website took 15 seconds to finish drawing on mobile
Measured August 2026: duda.co shipped 26 MB to a phone, 92% of it autoplay video, and its largest element landed at 15.5 s — with the CPU idle the whole time. The markup, the headers, and the fixes. Duda has since rebuilt the page; the re-check is on the page.
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. What the report shows