Skip to content
Permo Docs

HTML size of a WordPress page

HTML size is how large the page itself is: the text, the markup and everything written directly into it, but not the images, stylesheets and scripts it loads separately. It’s the first file a browser downloads for a page, and it has to read all of it.

Why it matters

Section titled “Why it matters”

The browser can’t show the page before it has read the HTML, and it learns about images and other files only as it reads. A large HTML file takes longer to transfer, especially on a mobile connection, and longer to process. Large pages often consist of many elements, and every element adds work for layout and drawing, which shows up in Total Blocking Time and Interaction to Next Paint.

Servers usually compress the HTML for the transfer, so what travels over the network is smaller. The browser still has to unpack and read the full size.

What influences it

Section titled “What influences it”

Browser: The most common cause of large HTML on WordPress sites is page builders. They wrap content in many layers of elements and often write styles for each section directly into the page. Inline SVG icons, styles and scripts written into the page, and data that plugins embed for their scripts add more.

WordPress: Long pages make HTML large too: home pages with many sections, category pages with dozens of products, menus that appear twice, once for desktop and once for mobile, and long comment threads. Some shop plugins write all product variations into the page as data.

Cache: A page cache doesn’t make the HTML smaller. It saves the work of building it, but the same file still travels to the browser.

In Permo

Section titled “In Permo”

Permo records the HTML size with the same request it uses for the uncached server response time: with every check, for each monitored page. The value is the length of the unpacked HTML in bytes, after decompression. Permo doesn’t store the content of the page. It reads at most 8 MB of an answer.

Reference values

Section titled “Reference values”

When crawling for Google Search, Googlebot reads the first 2 MB of an HTML file, measured uncompressed; content beyond that isn’t considered for indexing (source: Google Search Central, Googlebot, accessed October 16, 2026).

Section titled “Related”

Sources