addyosmani/puppeteer-webperf

Snippet: measure impact of SW caching

Open

#3 opened on Apr 28, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,758 stars) (84 forks)batch import
documentationenhancementgood first issuehelp wanted

Description

Some prior art here:

https://github.com/puppeteer/examples/blob/master/verify_sw_caching.js https://michaljanaszek.com/blog/test-website-performance-with-puppeteer/#cacheAndServiceWorker

Contributor guide

Tech stack
javascriptnodejs
Domain
frontendperformancetesting
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptPuppeteerService Workers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the prior art links (verify sw caching.js and blog post) to understand the approach. Create a new Puppeteer script that measures page load performance with and without service worker caching. Use Puppeteer's performance APIs to collect metrics. Add comments explaining the code. The file should be named measure sw caching.js.