Web - Timeline of a page load (Page Speed|Page Latency)

Page load is the latency performance metrics that cumulates:

• TCP latency (ie how fast, the network will receive the HTTP request and send back the HTTP response )
• HTTP latency (ie how fast the web server will create an HTTP document)
• and HTML latency (ie how fast a page will be rendered by the browser)

Load is not a single moment in time — it’s an experience that no one metric can fully capture. There are multiple moments during the load experience that can affect whether a user perceives it as “fast” or “slow”.

Page Load - Navigation (Browsing) - The user begins a page load with a navigation that executes a HTTP request

Browser - Page loading - The HTTP response has been received.

Metrics:

• Page Load Metrics - Time to First Bit (TTFB)
• Time To Response End (TTRE)

HTML code is processed by the browser in the order it appears in the file. Ie the code on the page (ie HTML, CSS, Javascript, …) is processed top down

Demo: Click on the button to start loading the HTML

<script>alert('The image is not yet downloaded because this alert is blocking. Click on the Ok button to close the alert, to resume the load process and load the image');</script>
<img src="/_media/lenna.png" width="200px"/>

Explanation:

• When the page is loaded, the browser execute the alert, the alert window will pop up and the page stops loading until the alert window is closed. Ie in this case, you will not see the image until you close the alert.

In this phase, the browser will build the DOM document from the HTML document received in the response.

Event:

• DomContentIoaded event is fired (same as ) when the DOM document has been build
• DOM - Ready event (Readiness|readyState)

Metrics:

• Page Load - Content Load Time - The amount of time to fully load the HTML and build the DOM (external resources like images & stylesheets not yet loaded).

In this phase, the browser will fetch resources present in the HTML page.

If the linked resources are:

• css stylesheet: they will be added to the CSS Object Model and trigger a re-rendering
• javascript: they will be executed depending on the async or defer attribute
• image: they will trigger a re-rendering and may cause a layout shift if the width and height attributes are not present or had bad values
• iframe: they will trigger another page load.

In this phase, the browser will transform all CSS (inline and stylesheet) into a CSSOM (tree)

The page is loaded. Image may still download. The page is not yet fully rendered.

Metrics:

• Page Speed - Load time - The amount of time to complete all the processing and resource (images, styles, etc) loading for the page.

Event:

• load event: occurs on a element or on the page (ie window)

Browser - Rendering

• Render tree: Building the render tree from the DOM and CSSOM
• Box Model tree creation
• Web Page - Painting

Metrics:

• Largest ContentFul Paint (LCP) / Page (Load|Speed) Metric - First Contentful Paint (FCP)
• Page Load - Time To Interactive (TTI)

Event:

• With the performance timeline observer, you can responds for instance to LCP.
• With the requestAnimationFrame callback, you can execute a script between rendering frames.

Your web analytics provider should provide you with them.

Example for Google Analytics

See Page Load Event (Timing)

You can get the metrics via:

• the performance timeline
• or a library such as perfume

Example:

// All results are reported to the analyticsTracker callback
new Perfume({
  analyticsTracker: options => {
    const { metricName, data, eventProperties, navigatorInformation, vitalsScore, } = options;
    switch (metricName) {
       case 'fp':
           console.log('firstPaint duration: '+data);
           return;
       case 'fcp':
           console.log('firstContentfulPaint duration: '+data);
           return;
       case 'lcp':
           console.log('largestContentfulPaint duration: '+data);
           return;
       default: 
          return;
    }  
  },
});

The below table lists the parameters that have an impact on the speed of your page load.

On a world scale, the location of the server has a great impact on the response time.

In a single server architecture can you guess where the server is located ?

Solution: Edge/Cdn server

• static cdn: you put a cdn proxy cache solution in front of your web server (cloudflare, ..)
• dynamic cdn: you locate multiple web servers and redirect the browser request via DNS or Anycast solution

Probability of bounce by page latency.

(Slow pages lose user)

• 100 ms: user perceives as instantaneous
• 1s: is about the upper limit of human flow of though. User loses the feeling direct feedback
• 10s: Upper limit of attention. Feedback is important and the chance of context switch is high.

To record a page load, you would use a headless browser

• side-by-side-pageload.js - Load 2 or more pages side-by-side to visually see the difference in page load. Optional desktop viewport and throttling settings.
• https://web.dev/vitals-tools-workflow/ - A performance-focused workflow based on Google tools
• https://zizzamia.github.io/perfume/

The Page lifecycle API ¹⁾ formalizes two new lifecycle states:

• Frozen: lifecycle state for CPU suspension. This means that the freeze steps algorithm was called
• Discarded: means that the discard algorithm was called

• The timeline event reference - all events triggered while making a recording.
• https://developers.google.com/web/fundamentals/performance/rail
• Key Moments In Web Page Loading, Totally Tooling Tips (S3, E9)
• Progressive Web Apps with React.js: Part 2 — Page Load Performance
• See Page load processing model for HTML files