Skip to content
Permo Docs

Uncached total time

Uncached total time is how long it takes until a page built from scratch has fully arrived: from the request until the last byte of the HTML. It comes from the same request as the uncached server response time, which stops at the first byte.

Why it matters

Section titled “Why it matters”

The first byte shows when the server starts answering. The total time shows when the whole page is there and the browser knows about every image, stylesheet and script it still has to load.

Usually, the two values are close. Many servers send the page only once WordPress has finished building it, and the transfer from the server to itself is fast. A larger gap means the page took long to transfer or that the server started sending before the page was complete.

What influences it

Section titled “What influences it”

WordPress: Most of the total time is the time WordPress needs to build the page, so the same causes as for the uncached server response time apply first: the work of active plugins, database queries and calls to other services.

Browser: A large page takes longer to transfer. Page builders, long lists of products or posts, and styles and scripts written directly into the HTML make it larger. See HTML size.

Server: Some server setups send the page in parts while it’s still being built. Then the first byte arrives early and the gap to the total time grows, even though the total stays the same.

In Permo

Section titled “In Permo”

Permo measures the total time with the same request it uses for the uncached server response time: with every check, for each monitored page, from your own server, past the page cache. The total time runs until the whole HTML answer has arrived. The same rules apply: only status 200 with an HTML page counts, Permo waits up to 15 seconds, and it records whether the answer really came without a cache.

Section titled “Related”

Sources