Start a project

Tool 92 of 194 · Performance

Page Load Simulator

List what your page loads, or paste a HAR file, and see how long it takes on Slow 3G through to fibre, which requests decide it, and which fix helps most.

Page Load Simulator at a glanceIllustration: 1, Budget; 2, processed in your browser; 3, Simulated load.Page Load Simulator2.5 s1Budget3Simulated load2In yourbrowser
1 Budget 2 processed on your device 3 Simulated load

Page Load Simulator

Your page's resources

Flags: blocking, async, defer, lcp, preload, raw (not compressed), h1 (HTTP/1.1 host), from=URL (found by that CSS or script), server=ms (server think time).
What if you...

    Every network at a glance

    NetworkFCPLCPFully loadedJS main threadWhat-if changeBudget

    Simulated waterfall

    Critical path

    ResourceRoleFoundDone

    FCP and LCP per network

    01

    What it does

    Simulates a page load on four networks, request by request, and estimates FCP and LCP against your budget, with what-if switches for common fixes.

    • DNS, TCP and TLS round trips per origin
    • TCP slow start and bandwidth shared between connections
    • HTTP/1.1's six connections against HTTP/2 multiplexing and priorities
    • Resources found by the HTML, by CSS or by scripts

    02

    Private by design

    Everything happens in your browser. Nothing you type, paste or upload is sent anywhere, and it keeps working offline once the page has loaded.

    03

    What you get

    FCP and LCP per network, a simulated waterfall and the critical path, with a Copy and a Download button on every result.

    • Performance
    • Core Web Vitals
    • HTTP/2
    • Budgets

    Why it matters

    A budget like "200 KB of JavaScript" is easy to set and hard to feel. What it costs depends on round trips as much as bytes: every new origin needs DNS, TCP and TLS before a byte moves, TCP starts slowly and speeds up each round trip, a font isn't requested until its stylesheet arrives, and a blocking script has to download and run before anything paints. On a phone over 4G those add up to seconds.

    This simulator plays a page load in 2 ms steps with those rules. It opens connections per origin, grows each congestion window, shares the bandwidth, discovers each resource when its parent arrives, runs scripts on one main thread, and estimates First Contentful Paint and Largest Contentful Paint for four standard networks. Flip the what-if switches to see what deferring scripts, preloading the hero image or compressing text would save before you build it. It's a model with its constants written down, so use it to compare options; Lighthouse and field data measure the real thing.

    How it works

    1. InputA resource list or HAR file
    2. In your browserRound trips, slow start, priorities and the main thread, simulated
    3. OutputFCP and LCP per network, with what-ifs

    Where it fits in a designer's workflow

    1. Plan
    2. Design
    3. Build
    4. Test
    5. Launch
    Deciding which performance fix to build first.

    By the numbers

    Estimated LCP for the sample page, before and after three fixesSlow 3G: LCP as it is: 13.76 s; Slow 3G: LCP with defer, preload and compression: 9.32 s; Slow 4G: LCP as it is: 3.88 s; Slow 4G: LCP with defer, preload and compression: 2.64 s; Fast 4G: LCP as it is: 1.28 s; Fast 4G: LCP with defer, preload and compression: 0.79 s; Cable / fibre: LCP as it is: 0.91 s; Cable / fibre: LCP with defer, preload and compression: 0.42 s2.5 sSlow 3G: LCP as it is13.76 sSlow 3G: LCP with defer, preload and compression9.32 sSlow 4G: LCP as it is3.88 sSlow 4G: LCP with defer, preload and compression2.64 sFast 4G: LCP as it is1.28 sFast 4G: LCP with defer, preload and compression0.79 sCable / fibre: LCP as it is0.91 sCable / fibre: LCP with defer, preload and compression0.42 s
    Simulated by this tool for its sample 13-request page on a mid-range phone. Deferring two blocking scripts, preloading the hero image and compressing two raw text files moves LCP under Google's 2.5 second 'good' line on Fast 4G and fibre and close to it on Slow 4G; on Slow 3G the bytes themselves are the problem. Source: web.dev: Largest Contentful Paint; Chrome DevTools: network throttling presets.
    Show the numbers as a table
    NetworkFCPLCPFCP after fixesLCP after fixes
    Slow 3G9.59 s13.76 s3.14 s9.32 s
    Slow 4G3.00 s3.88 s1.29 s2.64 s
    Fast 4G1.28 s1.28 s0.67 s0.79 s
    Cable / fibre0.91 s0.91 s0.41 s0.42 s

    How to use it

    1. List each resource with its type and transferred size, or paste a HAR file from DevTools.
    2. Mark render-blocking files, the LCP image, and anything found by CSS or a script.
    3. Set your FCP and LCP budgets and pick a network and device.
    4. Read the critical path, then try the what-if switches.

    FAQ

    How accurate is it?

    It's a model, not a measurement. It leaves out layout, image decoding beyond a small allowance, server variation and third-party work, so real numbers are usually a little slower. It's best for comparing options on the same page.

    What are the network profiles?

    The throttling presets Chrome DevTools and Lighthouse use: Slow 3G (400 kbps, 400 ms round trip), Slow 4G (1.6 Mbps, 150 ms, Lighthouse's mobile setting), Fast 4G (9 Mbps, 60 ms) and a 50 Mbps, 20 ms fixed line.

    Why does a new domain cost so much?

    Each origin needs a DNS lookup, a TCP handshake and a TLS handshake before the first request: three round trips here, 450 ms on Slow 4G. Fewer origins, or preconnect hints, avoid it.

    How is JavaScript cost worked out?

    From uncompressed size (transferred size times 3.3 for compressed files) at 0.25 ms per KB on desktop, 1 ms on a mid-range phone (Lighthouse's 4x CPU slowdown) and 2 ms on a low-end phone.

    Can I use a HAR file?

    Yes. Paste it and the table is built from its requests: CSS and first-party scripts are treated as blocking, the largest image as the LCP element. Check and edit those guesses.

    Work with me

    Want a site that gets these right?

    I build fast, accessible websites and web apps that pass these checks from day one. Tell me about your project and I'll reply personally with honest next steps.

    All developer tools · Back to leej.uk