6 ms·
I reckon you could take the page weight of this site down from 426KB to about 100KB with very little effort. - There's 20KB of Bootstrap.css that could be repl
by onion2k 6y ago
I reckon you could take the page weight of this site down from 426KB to about 100KB with very little effort.
- There's 20KB of Bootstrap.css that could be replaced with native CSS that would be loads smaller.
- There's 96KB of jQuery that I can't see being used at all. Even if it is, it doesn't need to be the full fat version.
- There's a 138KB PNG image that can be shrunk to 91KB using OxiPNG (or 77KB as a WebP, or 52KB using AVIF) using a free tool like https://squoosh.app https://squoosh.app
- There's 80KB for the Material Design icons font that could be replaced with an optimized version that only includes the glyphs used on the page (using a free tool like https://www.fontsquirrel.com/tools/webfont-generator https://www.fontsquirrel.com/tools/webfont-generator).
- delfinom 6y agoGlad to see you are volunteering to submit PRs to resolve these issues on an open source project
- _joel 6y agoFor me, when someone is critical of another person having spent their time checking out if there are any optimisations for something submitted to HN with, lets face it, snarky, "Well, raise a PR then", that's quite a shame.
- madsbuch 6y agoThe question is if the feedback is in line with the announcement. Basically the same a pointing out a spelling error on a single slide in a CS class. You are technically correct about the feedback, but it is misplaced and not worth spending time on in class.
- jeltz 6y agoGiven that this post was about a website redesign I feel his comment seems on topic.
- madsbuch 6y agoPersonally I'd say the issues are not about the design, but infrastructure and potentially UX (dependent on who that target group is, how their usage pattern is, etc.).
- _joel 6y agoIt's not. For starters you need to get the repo, make a branch, do the changes add tests, you may need an account to raise the PR on whatever platform, then there's possibly a CLA to raise. Whereas whoever raised the submission in the first place probably has some interaction with the project, therefore mentioning this in HN could then be taken by the submitter and raised as a feature request so someone could make a PR.
- folkhack 6y agoFor me, I see an open source project that probably has limited resources/time/volunteer effort to support it. I read that comment as, "rip huge chunks of Bootstrap and jQuery out of it - should be quick"... well I am guessing given Bootstrap design patterns that they used these tools as a core library in-which they built their site around. They may be planning to leverage these tools in the future, or even just want to give themselves the option to... It's an over-simplification. Likely, this site got them to where they wanted to be... a much more modern-looking site without a ton of effort sunk into development. It's also completely disingenuous to talk about these filesizes in pre-gzip numbers vs. post. When you look at these "optimizations" without taking into account gzip you are looking at a "worst case scenario" that doesn't exist - this site is gzipping it's assets over the wire. The jQuery gripe is more like 33.6Kb vs 96Kb when you look at it through the gzip lens. --- This sort of response (and subsequent defense) is why I would never show my creations here. It's emotionally difficult for me to see such a stable and mature project as Munin accomplish a bit of modernization only to be nitpicked like this. Munin is a great tool. "Raise a PR" is perfectly valid here when it comes down to it. I think the internet will handle the extra ~100Kb/page load just fine.
- _joel 6y ago> They may be planning to leverage these tools in the future If that's the case then creating a PR and raising it would be a waste of time, as it'd be rejected.
- kijin 6y agoRaise an issue first, gauge the reaction, and then create a PR if you think they would welcome it. Whether it's a website or some other open source project, maintainers usually don't like it when you create a massive refactoring PR without talking with them first. If, luckily, the maintainers are on HN, I guess talking about the "problem" here could very well substitute for raising an issue on whatever platform they use.
- _joel 6y agoCompletely agree. It seems there's no repo for this site anyway, judging be other comments.
- onion2k 6y agoYour comment prompted me to check to see if I could do that. The website build process doesn't appear to be documented and it's been built in a template system I'm not familiar with. So I can't.
- e12e 6y agoThat is actually something I'd expect gp know/check before suggesting submit pr/make issue/submit patch. I mean, if the website repo isn't available - the only "better" way to give feedback, would be to submit a link/the text of the hn comment to the project mail list/chat channel etc. I certainly think "open an issue/please make a pr" is a fine suggestion regarding FOSS projects in general. Ed: isn't this the repo, built via github workflows ? https://github.com/munin-monitoring/munin-monitoring.github.io/blob/master/.github/workflows/jekyll.yml https://github.com/munin-monitoring/munin-monitoring.github.... Beyond that; is there much cause to spend (any) effort to go from 0.5mb to less, really? Especially considering gzip?
- thesnide 6y agoSorry about that. I actually commented on it at https://munin-monitoring.org/munin/website/2021/04/20/we-made-it-onto-hn.html https://munin-monitoring.org/munin/website/2021/04/20/we-mad...
- onion2k 6y agoFWIW I did mean my comment more as a suggestion of where people could look for optimizations (in this site or their own sites) rather than a criticism of what you've made. I apologize for not communicating that better.
- j3th9n 6y agoAre you going to recommend this for every website posted on HN?
- vimax 6y agoSeems like a valid critique for a site redesign post
- j3th9n 6y agoIt's like telling da Vinci, at the moment of the reveal of the Mona Lisa, he should have used more paint so it can last 100k years instead of only 98k years. We are not dealing with a 10MB website with seconds long loading time and screaming for smaller images.
- onion2k 6y agoWhen the story is specifically about a website redesign, yes.
- j3th9n 6y agoYes, a website redesign, not a page speed overhaul project.
- dpwm 6y agoIt seems a fair discussion point, even if you don’t agree that the payoff is worth the effort. I don’t read it as a negative thing, and for me <500kB seems reasonable. Page size is an aspect of design – even if many websites are suffering far greater needless bloat than this one.
- dspillett 6y agoPerformance is a feature, or at least it should be, of any good design. Of course it might be a very low priority feature, so it would be valid to close any issue reports as "WONTFIX" if the devs have no time or feel they are better spending their time on other matters, especially if people on slow connections are not expected to be a significant part of the target audience, but commenting on potential performance issues is perfectly valid when discussing a site (re)design IMO.
- ericwood 6y agoYour other points are great low-hanging fruit performance-wise, but replacing bootstrap in a site that has been fully designed around it goes well beyond "very little effort."
- dpwm 6y agoCould something like purgecss be effective with removing unused bootstrap classes?
- ericwood 6y agoI've never tried setting something like that up but Bootstrap itself is extremely modular and you can be selective about what you want bundled with it, so that's probably a more effective starting place: https://getbootstrap.com/docs/3.4/customize/ https://getbootstrap.com/docs/3.4/customize/
- Apofis 6y agoI don't know why I even have broadband...