Avoid enormous network payloads

Published on Updated on

Translated to: Español, Português, 한국어, 中文, Pусский

Large network payloads are highly correlated with long load times. They also cost users money; for example, users may have to pay for more cellular data. So, reducing the total size of your page's network requests is good for your users' experience on your site and their wallets.

To see what accessing your site costs around the world, check out WebPageTest's What Does My Site Cost? You can adjust the results to factor in purchasing power.

How the Lighthouse network payload audit fails

Lighthouse shows the total size in kibibytes (KiB) of all resources requested by your page. The largest requests are presented first:

A screenshot of the Lighthouse Avoid enormous network payloads audit

Based on HTTP Archive data, the median network payload is between 1,700 and 1,900 KiB. To help surface the highest payloads, Lighthouse flags pages whose total network requests exceed 5,000 KiB.

See the Lighthouse performance scoring post to learn how your page's overall performance score is calculated.

How to reduce payload size

Aim to keep your total byte size below 1,600 KiB. This target is based on the amount of data that can be theoretically downloaded on a 3G connection while still achieving a Time to Interactive of 10 seconds or less.

Here are some ways to keep payload size down:

Stack-specific guidance


Apply route-level code splitting to minimize the size of your JavaScript bundles. Also, consider precaching assets with the Angular service worker.


Consider using Responsive Image Styles to reduce the size of images loaded on your page. If you are using Views to show multiple content items on a page, consider implementing pagination to limit the number of content items shown on a given page.


Consider showing excerpts in your article categories (one popular solution is a "read more" link), reducing the number of articles shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.


Consider showing excerpts in your post lists (you can use the "more" tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.


Source code for Avoid enormous network payloads audit

Updated on Improve article

This site uses cookies to deliver and enhance the quality of its services and to analyze traffic. If you agree, cookies are also used to serve advertising and to personalize the content and advertisements that you see. Learn more about our use of cookies.