Intro to measuring page performance with Puppeteer & Playwright

The need for fast and responsive applications has never been greater because of the move from desktop to mobile. Still, web applications have been increasing in complexity and size, with rising load times. It is therefore clear why the topic of webpage performance is more popular today than it likely ever was.

This article aims at giving a practical introduction to the whys and hows of web performance, without getting lost in the depth or breadth of this massive topic.

Why performance matters

You can build the best web application in the world, but be mindful that each user will have a specific amount of time they are willing to invest in your service to solve their problems. Exceed that amount, and you risk losing them to a different, more performant solution. This is even truer for new users, who haven’t yet been given proof of the quality of your service, and are essentially investing their time up-front, hoping for a return.

A competitive differentiator

  1. Pinterest decreasing wait time for their users, increasing both traffic and conversions.
  2. Zalando applying small improvements in load time and finding a direct correlation with increased revenue per session.
  3. The BBC discovering that every extra second that a page took to load led to 10% of users leaving the page.

Measuring performance

  1. Real user monitoring to understand what performance actual end-users of your service are experiencing.
  2. Synthetic monitoring to proactively gather intel on service performance, as well as to find issues before users stumble into them.
  3. Performance testing to avoid releasing performance regression to production in the first place.
  4. Regular audits to get an overview of your page’s performance and suggestions on how to improve it, e.g. with tools such as Google Lighthouse.

Performance with headless tools

  1. Access to the Web Performance APIs, especially PerformanceNavigationTiming and PerformanceResourceTiming.
  2. Whenever testing against Chromium, access to the Chrome DevTools Protocol for traffic inspection, network emulation and more.
  3. Easy interoperability with performance libraries from the Node.js ecosystem.

Web Performance APIs

Navigation timings are metrics measuring a browser’s document navigation events. Resource timings are detailed network timing measurements regarding the loading of an application’s resources. Both provide the same read-only properties, but navigation timing measures the main document’s timings whereas the resource timing provides the times for all the assets or resources called in by that main document and the resources’ requested resources.

We can use the Navigation Timing API to retrieve timestamps of key events in the page load timeline.

With Puppeteer:

With Playwright:

The Resource Timing API allows us to zoom in to single resources and get accurate information about how quickly they are being loaded. For example, we could specifically look at our website’s logo:

With Puppeteer:

With Playwright:

Chrome DevTools for performance

One important example is network throttling, through which we can simulate the experience of users accessing our page with different network conditions.

With Puppeteer:

With Playwright:

The DevTools Protocol is quite extensive. We recommend exploring the documentation and getting a comprehensive overview of its capabilities.

Additional performance libraries

With Puppeteer:

With Playwright:

Further reading

  1.’s performance section
  2. Web Performance Recipes With Puppeteer by Addy Osmani
  3. Getting started with Chrome DevTools Protocol by Andrey Lushnikov
  4. Get Started with Google Lighthouse

Banner image: “Speed of Light” by Rhys A., licensed under CC BY 2.0

Originally published on

Head of Developer Relations @ Checkly, core contributor.