-
Notifications
You must be signed in to change notification settings - Fork 2
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
Review Page Speed Insights for action items #305
Comments
Immediate thoughts for me -- the homepage hero image has loading type "eager" -- We can make that lazy loading and see if it helps. |
@komejo Can you take a look at the results from pagespeed and see if there's anything else obvious we could fix? I definitely see some things that would be hard but possible to work on, but I'm not sure if there are easy wins (I did add the lazy loading of the home page image). |
@mariacha Will do - FYI the homepage image lazy load actually hurts page speed b/c it's above the fold, so having lazy-load can impact layout shift. |
Three quick suggestions: Also, pass the link to https://jakearchibald.github.io/svgomg/ over to WRI so they can optimize things before uploading them. >>> YES
|
https://cmp.osano.com is a pretty big render-blocking script - ~1.6 seconds. It would definitely help if that could be |
|
Flagship PR: https://github.com/wri/wriflagship/pull/1256 Note: This should work with S3 after running |
I had some initial questions without digging in to this much yet. |
This is ready for QA now on develop: VR tests show images are looking good so far, and the map is now being lazy loaded to avoid high initial page load. I'm comparing tests between the live site and develop in Lighthouse, and it's looking better, but of course the content is not identical: The top issue there is "Layout shift" which will not be true once the donate links in the top are disabled. |
https://pagespeed.web.dev/analysis/https-wri-org/wwe8mjq8kk?form_factor=mobile
Sort by easy things to do and provide recommendations
Dev tasks
QA tasks
/our-work
-- same thing, but the page should be readableThe text was updated successfully, but these errors were encountered: