Task: Audit performance of Request Removal page

[CodeWritingCow]

Describe the task

Audit performance of Clean and Green Philly's Request Removal page using Google Lighthouse. Document audit results, including areas of improvement.

Acceptance Criteria

• [x] Generate Lighthouse report for mobile devices
• [x] Generate Lighthouse report for desktop devices
• [x] Post screenshots of results in this issue's comments section
• [x] Write brief summary of audit highlights, including Lighthouse's recommendations for improvement

Additional context

• For instructions on using Lighthouse, see https://developer.chrome.com/docs/lighthouse/overview

[jgaye]

@CodeWritingCow here are the reports:

---

Mobile

Overview

Recommendations

1. LCP is the main text block and takes >5s to render after load, figure out how to reduce that. It could be cause by the element waiting for other elements to load
2. 1st party JS scripts take 2.8s to execute, reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
3. Hotjar load blocks the main thread and takes 480ms - try to load third-party code after your page has primarily finished loading

Report link

https://pagespeed.web.dev/analysis/https-www-cleanandgreenphilly-org-request-removal/26cgqtlvoh?form_factor=mobile

Performance issues details - High

---

Desktop

Overview

Recommendations

Already very good, but could be optimized by remove unused JS and CSS

Report Link

https://pagespeed.web.dev/analysis/https-www-cleanandgreenphilly-org-request-removal/26cgqtlvoh?form_factor=desktop

Performance issues details - High

[jgaye]

As I was trying to reproduce the low performance on my mobile phone and couldn't reproduce a load >1s I realized something:

Note that the mobile performance is simulated for a slow 4g connection. So do not be biased if the mobile page loads fast for you: users with a low 4G connection (bad reception at home, on the move, etc...) will have to wait 6secs to see the page.