Earlier quoted context omitted.
Yes, lots of cool things to do around fonts! I have in TODO to add automatic system font fallback with the right metrics in order to improve CLS automatically. Is it what you call "freeze opentype axes based on font-feature-settings" or is it something else? I would like to do the subset font optimization. I'm just not sure how much of an improvement it's going to be. Have you done it manually before?
> Is it what you call "freeze opentype axes based on font-feature-settings" or is it something else? I was talking in context of variable fonts which come with lots of features mapped to opentype tags and axes. font-feature-settings property selects (or activates) those features. Usually this is done at few CSS selector levels. The variable fonts can be trimmed by freezing those features. I did something like this wi…
Show HN: Jampack – Optimizes static websites as a post-processing step
11–20 of 65 posts
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#12After trying this (JS always amazing, 47 vulnerabilities (19 moderate, 24 high, 4 critical)), my web vitals went down from 84 to 77. So not sure about that one. Also some svg images went missing.
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#13After trying this (JS always amazing, 47 vulnerabilities (19 moderate, 24 high, 4 critical)), my web vitals went down from 84 to 77. So not sure about that one. Also some svg images went missing.
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#14It looks like a great idea and would probably help if I had any images in my project.
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#15Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#16After trying this (JS always amazing, 47 vulnerabilities (19 moderate, 24 high, 4 critical)), my web vitals went down from 84 to 77. So not sure about that one. Also some svg images went missing.
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
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
#17Can 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?
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#18I 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 Performance - 73 Accessibility - 100 Best Practices - 85 SEO
- desktop: - 90 Performance - 75 Accessibility - 100 Best Practices - 82 SEO
after Jampack:
- mobile: - 49 Performance - 80 Accessibility - 100 Best Practices - 92 SEO
- desktop: - 85 Performance - 82 Accessibility - 100 Best Practices - 91 SEO
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#19This 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…
Re: Show HN: Jampack – Optimizes static websites as a post-processing step
#20Hm, this didn't change anything hugely on one of my projects - for example, it reduced the total bundle size, but it increased the gzip'd size, so it's actually a net negative for me. But it looks like the CSS improvements actually did help. It looks like a great idea and would probably help if I had any images in my project.