This is exactly what I've been looking for. I had been using my own scripts with Sharp for image optimizations like this, but this eliminates the need for the that entirely and works much better! I ran Jampack after building my Quarto static site and got a 32% smaller folder with no noticeable drawbacks yet. Here are my metrics before Jampack and after using PageSpeed Insights: before Jampack: - mobile: - 52 Performa…
Hi! Happy you enjoyed it! I would have expected better results for Performance metrics! If you don't mind sharing your static site output pre-jampack I would enjoy checking out. georges [at] divriots [dot] com
Show HN: Jampack – Optimizes static websites as a post-processing step
21–30 of 65 posts
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#22Earlier quoted context omitted.
Needs a little bit of updates :) will do. If you can share your static website on GitHub repo or something I would love to have a look. georges [at] divriots [dot] com
Rolled back, https://www.amazingcto.com/ There where many errors, I'll try again later and send you the vitals + errors. [Edit] Generally I would love this.
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#23Ohhh, I like this is a lot! Will use it! Any unimpressed commenters willing to point any defects? To me this looks like the equivalent of compiling C to super-optimized assembly and is definitely doing things that I wouldn't want to do myself.
If we really have to ship super optimized assembly, then I would completely skip HTML and CSS altogether and just ship highly optimized web assembly and let developers use whatever language they want.
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#24Thanks for the project! Can I expect it to run out of the box for Next.js static-generated files? If so, any recommendations on how to set it up in a Next.js project?
If the site is 100% static then it should play nice. If it's hydrated with JS: results may vary. Let me know!
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#25Is there a reason for preferring them as a separate post-build step? I guess the tradeoff is faster rebuilds when you're developing vs the possibility that you miss subtle bugs resulting from introducing stuff like width declarations for images?
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#26Earlier quoted context omitted.
Rolled back, https://www.amazingcto.com/ There where many errors, I'll try again later and send you the vitals + errors. [Edit] Generally I would love this.
Heads up, you've got an h3 tag now on your website that says "Articlesnpm install -D @divriots/jampack from Stephan".
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#27This is exactly what I've been looking for. I had been using my own scripts with Sharp for image optimizations like this, but this eliminates the need for the that entirely and works much better! I ran Jampack after building my Quarto static site and got a 32% smaller folder with no noticeable drawbacks yet. Here are my metrics before Jampack and after using PageSpeed Insights: before Jampack: - mobile: - 52 Performa…
Hi! Happy you enjoyed it! I would have expected better results for Performance metrics! If you don't mind sharing your static site output pre-jampack I would enjoy checking out. georges [at] divriots [dot] com
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#28Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#29This is exactly what I've been looking for. I had been using my own scripts with Sharp for image optimizations like this, but this eliminates the need for the that entirely and works much better! I ran Jampack after building my Quarto static site and got a 32% smaller folder with no noticeable drawbacks yet. Here are my metrics before Jampack and after using PageSpeed Insights: before Jampack: - mobile: - 52 Performa…