Page Load Time

Page load time is the duration between starting a navigation and the page reaching a defined "loaded" state. Traditionally that state is the browser's load event, which fires when the HTML and all its dependent resources such as images and stylesheets have finished loading.

Why it matters

Speed affects bounce rate and conversions, so teams track it. The trouble is that no single number captures "loaded". The load event can fire long after the page is usable, or earlier than late-rendered content. Modern practice uses several metrics: TTFB for server response, FCP and LCP for visual progress, and INP for responsiveness.

Example

Reading the legacy timing from the browser:

const [nav] = performance.getEntriesByType('navigation');
console.log(nav.loadEventEnd - nav.startTime); // ms to load event

A single-page app may report 600 ms for this value, yet users wait another 3 seconds for API data to render. The load event misses that.

Common mistakes

• Reporting an average. Load times are skewed, so use medians and the 75th or 95th percentile.
• Testing on a fast office connection and desktop only.
• Ignoring cached versus first visits.

Related

• LCP
• TTFB
• Core Web Vitals
• Field data vs lab data

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.