Expected behavior
I would expect that we'd be compressing our images and trying to upload them at an appropriate size.
I would think running images through https://tinypng.com/ would be a very good habit.
Not as good as using WebP or AVIF, but easier.
Describe the bug
From this quick review, we can drop significant Kb's just be optimizing the images:
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcivicactions.com%2F
| URL |
Resource size |
Potential savings |
Capitol building to represent government services that build public trust |
/static/homepage-hero-fdad1db….png(civicactions.com) |
518.3 KiB |
div.cases > div.press-release-teaser > a > img |
/static/blogpostimage-135ff83….png(civicactions.com) |
148.0 KiB |
div.cases > div.press-release-teaser > a > img |
/static/case-study-teaser-img-4-fd5a69a….png(civicactions.com) |
46.4 KiB |
Expected behavior
I would expect that we'd be compressing our images and trying to upload them at an appropriate size.
I would think running images through https://tinypng.com/ would be a very good habit.
Not as good as using WebP or AVIF, but easier.
Describe the bug
From this quick review, we can drop significant Kb's just be optimizing the images:
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcivicactions.com%2F