-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TRACKING] Benefits web performance improvements #2487
Comments
Wrote this out for @angela-tran so she can add this to the list of front-end fixes we are considering for Q4! Definitely don't think we need to do all of them, but I thought it would be interesting to:
And keep running these tests until we get our Time To First Byte, First/Largest Contentful Paint numbers down for the homepage. All the fixes we make for anything outside of that large image (like server response times) will help all the other pages as well. |
Tickets
The overall goal is to make the homepage (and by extension all pages) load faster on mobile devices, as tested on Google Lighthouse testing and WebPageTest.org, through the following methods:
Testing
This is a side-by-side comparison I made on WebPageTest.org showing how the site reders with some of the performance fixes listed below, versus how it renders now on a Mobile device:
Lighthouse
Full results: https://pagespeed.web.dev/analysis/https-benefits-calitp-org/rqzk6itbxm?form_factor=mobile
Web Page Test
Full results: https://www.webpagetest.org/result/241029_BiDcSX_ARH/
Suggestions: https://www.webpagetest.org/result/241029_BiDcSX_ARH/2/experiments/
The text was updated successfully, but these errors were encountered: