PageSpeed Matters
    PageSpeed Matters
    Loading Performance · Glossary

    Fully Loaded Time · Definition & Explanation 2026

    Fully Loaded Time measures the point at which all resources on a page have finished downloading and processing — every image, script, stylesheet, font, and asynchronous request. In the Core Web Vitals era, it has diminished in importance, but remains useful for understanding total page weight and resource efficiency.

    WebPageTest tracks Fully Loaded Time as a primary metric, defining it as the point when network activity ceases for 2 seconds after the window load event.

    Updated 2026-02-28
    M
    By Matt Suffoletto

    TL;DR — Quick Summary

    Fully Loaded Time measures when all resources on a page have finished loading. Less important than CWV for ranking but indicates total page weight and resource efficiency. Useful for identifying unnecessary resource loading.

    What is Fully Loaded Time?

    Fully Loaded Time is the point at which all resources have finished downloading and processing — images, scripts, stylesheets, fonts, and asynchronous requests. WebPageTest defines it as 2 seconds of network quiet after the window load event, capturing lazy-loaded images, deferred scripts, and async API calls.

    History & Evolution

    • •1990s–2000s — 'Page load time' was the primary performance metric.
    • •2010s — User-centric metrics (FCP, LCP) begin replacing it.
    • •2020 — Core Web Vitals shift focus to perceived performance.
    • •2025–2026 — Still reported by WebPageTest and DevTools but not scored or tracked in CrUX.

    How Fully Loaded Time is Measured

    Available in WebPageTest (primary), Chrome DevTools Network panel, and Navigation Timing API. Not scored by Lighthouse or tracked in CrUX.

    Key rule: Field data (CrUX) determines Google rankings. Lab data (Lighthouse, WebPageTest) is for debugging and iteration.

    Common Causes of Poor Fully Loaded Time Scores

    1. 1Unoptimized images — Large, uncompressed images add seconds.
    2. 2Excessive third-party scripts — Analytics, ads, chat load many resources.
    3. 3No lazy loading — All images loaded immediately.
    4. 4Large video files — Auto-playing or preloaded video.
    5. 5Unnecessary fonts — Multiple unused font weights.

    Frequently Asked Questions

    For step-by-step optimization, platform-specific fixes, code examples, and case studies, read our full guide:

    The Ultimate Guide to Website Performance Measurement, Tools & Data: Lab, Field & Everything Between in 2026

    Struggling with Fully Loaded Time?

    Request a free speed audit and we'll identify exactly what's holding your scores back.