kuma
kuma copied to clipboard
mdn
E - Assess getting lighthouse performance score to 95 (mobile)
Epic
Assess getting lighthouse performance score to 95 (mobile)
Acceptance criteria
- [x] Time-boxed investigation of performance on mobile maybe 1 week each front-end/back-end
- [x] Report based on investigation
- [x] Low hanging fruits identified and possibly selected for upcoming sprints
Note-to-those-with-access: https://search.google.com/search-console/speed?resource_id=https%3A%2F%2Fdeveloper.mozilla.org%2F
Also, a sample report: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FAPI%2FFileList
Notes:
Google Search Console: https://search.google.com/search-console/speed/summary?resource_id=https%3A%2F%2Fdeveloper.mozilla.org%2F&device=2&hl=en
Speedcurve: https://speedcurve.com/mozilla-add-ons/mdn/favorite/?cs=lg&d=7&db=17534&dc=1&de=1&ds=1 in 'options' you can emulate a older phone, like Nexus6 and see that it performs significantly slower.
Page for testing Array.prototype.forEach() is the recommended page for testing.
Simulate a slow CPU on mobile.
UserStories:
- report list of possible changes that would have an effect on perf
- define effort of each possible effect
- report list of possible changes that would have an effect on perf
some ideas on tasks...
- LIST all the possible things you want to hypothesis test (e.g. lazy load bcd-signal.js, minimize CSS, inline CSS, lazy-load sidebar, reduce react bundle, switch to preat, etc. etc.)
- Download a page like https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach so it works 100% on its own so it doesn't depend on kuma.
- Figure out a basic framework for running Lighthouse against a page you can edit. And re-run easily to be able to write down the quantitative effects of changes.
- Ability to do ^^ but do it on a remote network via a CDN.
Report is here:
https://github.com/mdn/kuma/issues/6934#issuecomment-622497603