6 ms·

I use Jekyll for my company website [1] and managed to get a lot of speed optimisations simply by using a post-processing tool on the statically generated outpu

I use Jekyll for my company website [1] and managed to get a lot of speed optimisations simply by using a post-processing tool on the statically generated output. The tool I use is Jampack and I'd highly recommend it: https://jampack.divriots.com https://jampack.divriots.com For my product website, it reduced the overall size by 590MB or approximately 59% in size, along with changing the HTML/CSS to make the optimisations that this article notes. [1] https://www.magiclasso.co/ https://www.magiclasso.co/

maccard 1y ago
Do you mean KB or do you have a 1GB website??
- vallode 1y ago
  They are most likely referring to the overall size of the whole website including all generated HTML for posts, static content, styles etc.
  - rossant 1y ago
    1gb is huge even for a whole website. Unless there are videos or hundred of high definition photos. Curious to know what makes up this space.
    - dewey 1y ago
      Maybe they included node_modules in that count.
- exiguus 1y ago
  I guess mostly picture. If you have 500 posts, one picture for each, and then optimize image for responsive and browser compatibility, there should be 3 to 12 images per image source set: Mobile, Tablet, Desktop as breakpoints / AVIF with webp or jpeg fallback, Retina/Normal. And this will increase the overall-size to 12 x 500 x 50kB = 300MB
  - broken-kebab 1y ago
    I doubt there's a practical reason for an average website, especially something blog-like to have pre-optimized pictures for that many screen types.
- bentocorp 1y ago
  It is a 991MB website, before optimisations. The large majority of this comes from large header images for the Insights post content: https://www.magiclasso.co/insights/ https://www.magiclasso.co/insights/ These are png images that are relatively large in size until optimisation creates smaller, multiple image set versions. I wouldn't say that this is an unusually large site. Any site with a medium amount of content would likely grow to such a size.
thomas_witt 1y ago
In my opinion the whole point of Jekyll is not having to use some npm/JS packages and dependencies.
raphinou 1y ago
Thanks for sharing. I'm using https://soupault.app/ https://soupault.app/ to generate my websites and this could come handy for optimisation.
arclight_ 1y ago
This looks fantastic! I really like how it's static site generator-agnostic, and the intelligent CSS and above-the-fold optimizations. I'll definitely give this a try - only wish I knew about it before I wrote my thing!

maccard 1y ago

Do you mean KB or do you have a 1GB website??

vallode 1y ago
They are most likely referring to the overall size of the whole website including all generated HTML for posts, static content, styles etc.
- rossant 1y ago
  1gb is huge even for a whole website. Unless there are videos or hundred of high definition photos. Curious to know what makes up this space.
  - dewey 1y ago
    Maybe they included node_modules in that count.
exiguus 1y ago
I guess mostly picture. If you have 500 posts, one picture for each, and then optimize image for responsive and browser compatibility, there should be 3 to 12 images per image source set: Mobile, Tablet, Desktop as breakpoints / AVIF with webp or jpeg fallback, Retina/Normal. And this will increase the overall-size to 12 x 500 x 50kB = 300MB
- broken-kebab 1y ago
  I doubt there's a practical reason for an average website, especially something blog-like to have pre-optimized pictures for that many screen types.
bentocorp 1y ago
It is a 991MB website, before optimisations. The large majority of this comes from large header images for the Insights post content: https://www.magiclasso.co/insights/ https://www.magiclasso.co/insights/ These are png images that are relatively large in size until optimisation creates smaller, multiple image set versions. I wouldn't say that this is an unusually large site. Any site with a medium amount of content would likely grow to such a size.

thomas_witt 1y ago

In my opinion the whole point of Jekyll is not having to use some npm/JS packages and dependencies.

raphinou 1y ago

Thanks for sharing. I'm using https://soupault.app/ https://soupault.app/ to generate my websites and this could come handy for optimisation.

arclight_ 1y ago

This looks fantastic! I really like how it's static site generator-agnostic, and the intelligent CSS and above-the-fold optimizations. I'll definitely give this a try - only wish I knew about it before I wrote my thing!