-
-
Notifications
You must be signed in to change notification settings - Fork 17
Description
What Happened
Not sure if this belongs here (did not find a dedicated blog repo) but I checked the elementary blog out and the post for the odin release was 43(!)Megabyte in size, and other post include several images with more than 1meg in size and this is really not so smart using all the visitors bandwith (some are on metered connections and have no unlimited data plans).
Google Speed Analyser also says to optimize images:
- https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fblog.elementary.io%2Felementary-os-6-odin-released%2F
- https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fblog.elementary.io%2Felementary-os-6-odin-beta-2%2F
Expected Behavior
blog.elementary.io should not use such big images
Steps to Reproduce
- Visit blog.elementary.io with opened network utility in dev-tools of browsers.
- Inspect download size of website
Logs
- https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fblog.elementary.io%2Felementary-os-6-odin-released%2F
- https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fblog.elementary.io%2Felementary-os-6-odin-beta-2%2F
Platform Information
- None
Suggested solution
Solution would be to use compressed images where no absolute high quality media are neccessary and maybe some lazy loading here and there. You could also detect display sizes and use different images on desktop and mobile. Look into srcset https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/srcset, this allows you to use high quality on larger screen sizes and another low quality on mobile for example.
I also think some automation could solve this.. not sure what jekyll-developers are using for this though.
