What is a good page load time?

A widely used target is full load under 3 seconds, since Google found 53% of mobile visitors leave past that point. For Core Web Vitals specifically, Largest Contentful Paint should be 2.5 seconds or less at the 75th percentile of real users. Faster is always better, but 2 to 3 seconds is the practical bar for most marketing and commerce pages.

How is page load time different from response time?

Response time measures a single request to the server, often just tens or low hundreds of milliseconds, and ends when the first response is returned. Page load time covers the whole experience: the initial response plus every image, stylesheet, font, and script the page needs before it is painted and interactive. A page with a 100 ms response time can still take 4 seconds to load if it pulls dozens of additional assets.

What milestones make up page load time?

In order, the main milestones are TTFB (first server byte), First Contentful Paint (first pixel of content), Largest Contentful Paint (main content rendered), DOMContentLoaded (HTML parsed), and onload (every subresource finished). Most performance tools report several of these so you can see which stage is slow. LCP and FCP are the two most tied to perceived speed.

Should I measure page load time with lab or field data?

Use both. Lab (synthetic) tests run on a fixed connection and device, giving stable numbers you can compare release to release and catch regressions before deploy. Field data from real user monitoring shows actual visitor experience across thousands of real devices and networks, and the 75th percentile is what Google uses to score Core Web Vitals. Lab data finds problems early, and field data confirms whether real users feel them.

What Is Page Load Time?

Reviewed by Ionut Caval · Updated June 2026

Page load time is the total elapsed time for a web page to download, render, and become usable, measured from navigation start to the point the page is fully painted and interactive. It is a composite of many smaller milestones, not a single server request like response time.

Page load time is the wall-clock duration a browser needs to fetch, parse, and paint a full page after navigation begins. It bundles dozens of network round trips, render steps, and script executions into one number, which is why a single page can feel "loaded" at three different moments depending on what you measure.

The milestones that make up page load time

A page does not load in one instant. The browser passes through ordered milestones, each of which a monitoring tool can report separately:

Time to First Byte (TTFB), when the server's first response byte arrives. See TTFB.
First Contentful Paint (FCP), when the first text or image is painted. Google rates an FCP of 1.8 seconds or less as good.
Largest Contentful Paint (LCP), when the main content block finishes rendering. See LCP.
DOMContentLoaded, when the HTML is parsed and the DOM is ready, before images and stylesheets necessarily finish.
onload (fully loaded), when every subresource, including images and fonts, has finished downloading.

Page load time differs from response time, which measures one server request in isolation. A 120 ms response time can still sit inside a 4 second page load if the page then pulls 60 more assets and runs heavy JavaScript before becoming interactive.

Why the seconds matter

Google's "The Need for Mobile Speed" study found that 53% of mobile visits are abandoned when a page takes longer than 3 seconds to load, and Akamai research links each additional 1 second of load time to roughly a 7% drop in conversions. Google's Core Web Vitals program treats an LCP of 2.5 seconds or less as good, 2.5 to 4.0 seconds as needs improvement, and above 4.0 seconds as poor.

Two measurement modes capture this. Lab (synthetic) tools load the page from a controlled agent on a fixed connection, giving repeatable numbers for regression testing. Field data, gathered through real user monitoring, records load times from actual visitors across their devices and networks, where the 75th percentile is the figure Google scores. The two often disagree, so teams track both.

Frequently asked questions

What is a good page load time?

A widely used target is full load under 3 seconds, since Google found 53% of mobile visitors leave past that point. For Core Web Vitals specifically, Largest Contentful Paint should be 2.5 seconds or less at the 75th percentile of real users. Faster is always better, but 2 to 3 seconds is the practical bar for most marketing and commerce pages.
How is page load time different from response time?

Response time measures a single request to the server, often just tens or low hundreds of milliseconds, and ends when the first response is returned. Page load time covers the whole experience: the initial response plus every image, stylesheet, font, and script the page needs before it is painted and interactive. A page with a 100 ms response time can still take 4 seconds to load if it pulls dozens of additional assets.
What milestones make up page load time?

In order, the main milestones are TTFB (first server byte), First Contentful Paint (first pixel of content), Largest Contentful Paint (main content rendered), DOMContentLoaded (HTML parsed), and onload (every subresource finished). Most performance tools report several of these so you can see which stage is slow. LCP and FCP are the two most tied to perceived speed.
Should I measure page load time with lab or field data?

Use both. Lab (synthetic) tests run on a fixed connection and device, giving stable numbers you can compare release to release and catch regressions before deploy. Field data from real user monitoring shows actual visitor experience across thousands of real devices and networks, and the 75th percentile is what Google uses to score Core Web Vitals. Lab data finds problems early, and field data confirms whether real users feel them.

Put these metrics to work. Monitor your site free.

2-minute setup · Cancel any time
Create Free Account

Your Dashboard

No credit card needed