How to Fix Total Page Weight: Get Your Homepage Under 2 MB
This check adds up the size of your homepage HTML and a sample of the images, scripts, stylesheets and fonts it loads. A result above about 2 MB gets a warning, and above about 4 MB it fails. By the end of this guide you will have found the heaviest files, shrunk or removed them, turned on server compression, and re-measured the page.

Why it matters
Every kilobyte has to be downloaded before the page is fully usable, and mobile visitors on slow or metered connections feel it most. Heavy pages usually fail Largest Contentful Paint, one of Google's Core Web Vitals and a page experience signal. Bloated pages also take longer for search and AI crawlers to fetch and render, which wastes crawl budget on large sites.
Large hero images, unused JavaScript libraries and extra font files are the usual causes, and all of them can be fixed without a redesign.
What you need
Step-by-step fix
Measure the page and list the heaviest files
com in Chrome, press F12, go to the Network tab, tick Disable cache and reload. Click the Size column header to sort largest first. The status bar at the bottom shows transferred size (compressed, over the network) and resources size (uncompressed).
Write down the 10 biggest files and their type (Img, JS, CSS, Font, Media). That list is your work order.
Resize and convert images to WebP or AVIF
Most oversized pages ship photos far larger than they are displayed. Resize each image to about 2x its largest displayed width (around 1600–2000 px for a full-width hero), then convert it to WebP or AVIF. Aim for less than 200 KB per hero image and less than 100 KB for content images.
Use srcset so phones download a smaller version.
cwebp -q 78 -resize 1600 0 hero.png -o hero.webp
avifenc --min 20 --max 35 hero.png hero.avif
<img src="/img/hero-1600.webp"
srcset="/img/hero-800.webp 800w, /img/hero-1600.webp 1600w"
sizes="100vw" width="1600" height="900"
alt="Example Co workshop" fetchpriority="high">Replace autoplay video and heavy embeds
A background hero video or an embedded YouTube player can add 1–3 MB on its own. Swap autoplay hero videos for a compressed poster image, or cap the video at under 1 MB, muted, with preload="none". For YouTube or Vimeo, show a thumbnail with a play button and load the real iframe only when the visitor clicks it.
Add loading="lazy" to all below-the-fold images and iframes.
<video muted playsinline preload="none" poster="/img/hero-poster.webp"> <source src="/video/hero-720.mp4" type="video/mp4"> </video> <iframe src="https://www.youtube-nocookie.com/embed/VIDEO_ID" loading="lazy" title="Example Co demo"></iframe>
Remove unused JavaScript and CSS libraries
In DevTools press Ctrl+Shift+P (Cmd+Shift+P on Mac), run Show Coverage, then reload. Red bars show bytes that downloaded but never ran. Common leftovers to remove:
- jQuery loaded only for one small effect
- Several slider or carousel libraries
- Full Font Awesome or Bootstrap when you use a few icons or classes
- Analytics or chat scripts from tools you no longer use
Remove the <script> or <link> tags, or uninstall the plugin or app that injects them.
<!-- Remove if unused --> <script src="/js/jquery-3.7.1.min.js"></script> <script src="/js/slick.min.js"></script> <link rel="stylesheet" href="/css/font-awesome-all.min.css">
Trim web fonts to what you actually use
Each font weight and style is a separate file, often 30–150 KB. Keep two or three weights, serve only WOFF2, and subset the font to the characters your site actually uses (for example Latin). Replace icon fonts with inline SVGs for the handful of icons you need.
pip install fonttools brotli pyftsubset Inter-Regular.ttf --unicodes="U+0000-00FF,U+2013-2014,U+2018-201D,U+20AC" --flavor=woff2 --output-file=inter-regular-latin.woff2
Enable Brotli or gzip compression on the server
Text files (HTML, CSS, JS, SVG, JSON) shrink by 70–80% when compressed. Check whether compression is on: open a CSS or JS file in the Network tab and look for a content-encoding: br or gzip response header. If it is missing, enable it.
Brotli on Nginx requires the ngx_brotli module; gzip is built in.
gzip on; gzip_comp_level 6; gzip_types text/css application/javascript application/json image/svg+xml text/plain; # requires ngx_brotli module brotli on; brotli_comp_level 5; brotli_types text/css application/javascript application/json image/svg+xml text/plain;
Re-measure and confirm you are under 2 MB
com with Disable cache ticked and read the transferred total in the Network tab. Then run PageSpeed Insights and check that the "Avoid enormous network payloads" warning is gone or much smaller. Finally, re-run the audit.
A result below 2048 KB passes, and 2–4 MB is a warning.
curl -s -o /dev/null -H "Accept-Encoding: br,gzip" -w "HTML: %{size_download} bytes\n" https://example.com/Platform-specific notes
WordPress
Use an image plugin such as ShortPixel, Imagify or EWWW to bulk-convert your existing media library to WebP or AVIF. Deactivate and delete unused plugins under Plugins > Installed Plugins, because many load CSS and JS on every page. Asset CleanUp or Perfmatters can stop scripts from loading where they are not needed. Page builders and slider plugins are frequent sources of page weight.
Shopify
Shopify's CDN serves WebP or AVIF automatically, but you still need to request the right size: use the `image_url: width: 1600` filter with `image_tag` and widths for srcset in your Liquid. Uninstalled apps can leave script snippets in theme.liquid, so search for them and remove them. Turn off unused App embeds in Online Store > Themes > Customize > App embeds.
Wix
Wix compresses images and serves WebP automatically, and you cannot change server compression. Your levers are content: remove unused apps under Settings > Apps, replace video backgrounds with images, upload images no wider than about 2500 px, and reduce the number of custom fonts.
Next.js
Use `next/image` for automatic resizing, AVIF/WebP and lazy loading (set `images.formats: ['image/avif','image/webp']` in next.config.js). Use `next/font` to self-host subset fonts. Run `@next/bundle-analyzer` to find large client bundles, and move heavy logic into Server Components so it never ships to the browser.
Cloudflare
Brotli is applied automatically to compressible content on the proxied (orange-cloud) traffic. Polish (Speed > Optimization > Image Optimization) can convert images to WebP on paid plans, but it does not resize them, so oversized images still need fixing at the source. Cloudflare's Auto Minify has been retired, so minify files in your build process instead.
Check that it worked
✅ How to verify
- In the Chrome DevTools Network tab, with cache disabled, the transferred total for the homepage is under 2 MB.
- Response headers for HTML, CSS and JS files show content-encoding: br or gzip.
- PageSpeed Insights no longer flags "Avoid enormous network payloads", or the flagged total is well under 2,048 KiB.
- Re-running the audit reports the homepage plus sampled assets below 2 MB.
⚠️ Common mistakes
- Compressing images but still serving 4000 px originals to every device instead of resizing them and using srcset.
- Uninstalling a plugin or app but leaving its script or link tags hard-coded in the theme.
- Lazy-loading the hero image, which hurts LCP even though it lowers initial bytes.
- Loading 6–10 font weights plus a full icon font when only two weights and a few icons are used.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What is a good total page weight in 2026?
Under 2 MB is a solid target for a homepage, and under 1 MB is excellent. The median mobile page is roughly 2 MB, so going above 4 MB puts you among the heaviest pages on the web.
Does page weight directly affect Google rankings?
Not as a standalone factor. It drives load-time metrics such as Largest Contentful Paint, which feed Core Web Vitals and page experience signals, and it affects whether visitors stay or leave.
Should I use WebP or AVIF?
AVIF is usually 20–30% smaller than WebP at similar quality, and all current major browsers support it. WebP encodes faster. Many sites serve AVIF with WebP as a fallback through the picture element or their CDN.
Does lazy loading reduce page weight?
It reduces what loads at first for real visitors, because off-screen images download only when they scroll near. However, the files are still referenced in the page, so the biggest reductions come from making those files smaller or removing them.
How to Fix Render-Blocking Resources on Your Website
How to Fix Slow Time to First Byte (TTFB) on Your Website
How to Fix Unminified CSS and JavaScript Files on Your Site
How to Fix Cumulative Layout Shift (CLS) on Your Website
How to Enable Gzip or Brotli Compression on Your Website
How to Fix Interaction to Next Paint (INP) Above 200ms