Live data from Hacker News

Show HN: Jampack – Optimizes static websites as a post-processing step

github.com

21–30 of 65 posts

Re: Show HN: Jampack – Optimizes static websites as a post-processing step

#21

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

Just want to say this two comment interaction is a perfect distilled example of value of posting to HN for such things.

Re: Show HN: Jampack – Optimizes static websites as a post-processing step

#22

Earlier 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.

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

#23
post #7

Ohhh, 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.

I don't know if we are on the right track if we have to ship "super optimized assembly" for HTML and CSS. I think we should be able to write the most simple and straightforward HTML and CSS and the Browser on all devices should just render it fine.

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

#24
post #17

Thanks 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?

Hi! If the static output of your Next.js project is `./build` then add `&& jampack ./build` to your build command.

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

#25
This looks like it covers several use cases people are picking the SSG and its plugins to handle in the first place, especially if they're picking Astro or Eleventy.

Is 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

#26

Earlier 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".

Lol, thank you. Fixed.

Re: Show HN: Jampack – Optimizes static websites as a post-processing step

#27

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

I've zipped it up and sent a link.

Re: Show HN: Jampack – Optimizes static websites as a post-processing step

#28
This looks great! Although personally I hate it when I scroll a page beyond the 'fold' and have to wait for images to load. By default, does this load the remaining below-the-fold content in the background once the above-the-fold stuff is complete?

Re: Show HN: Jampack – Optimizes static websites as a post-processing step

#29

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…

Remember that Lighthouse (and therefore PageSpeed Insights) scores fluctuate. Consider running multiple times and taking median scores when doing comparisons of performance like this. "The median Lighthouse score of 5 runs is twice as stable as 1 run" https://developers.google.com/web/tools/lighthouse/variabili...
Post reply on HN