Earlier quoted context omitted.
So brave.
So HN.
How we improved our website's performance
41–50 of 76 posts
Re: How we improved our website's performance
#4212 people for a static site seems like a huge team to me.
It's not a static site. It has a site-wide search. It lets users post comments on articles. It also has its own store selling books. And it serves ads too.
Re: How we improved our website's performance
#43> Around the same time we switched from an (outdated) manually created critical CSS file to an automated system that was generating critical CSS for every template — homepage, article, product page, event, job board, and so on — and inline critical CSS during the build time. Yet we didn’t really realize how much heavier the automatically generated critical CSS was. Is reducing the total amount of CSS per page so you…
That's one of the fastest loading modern pages I've ever been to. Kudos!
Re: How we improved our website's performance
#44Earlier quoted context omitted.
> It should load in an instant. FWIW, it does load in an instant for me. (Lighthouse Performance = 99, Speed Index = 0.4s.)
Me too, but I'm loading it on a $3000 computer with 150Mbps/<10ms internet. Generally it's a good idea to only focus on the mobile score. :)
Re: How we improved our website's performance
#45"Modern" web development is apparently a game of Jenga.
Only because developers absolutely insist on building things that way, for some reason I will never comprehend. What's the first thing most people do when starting a new project? They ask "what framework should I build this on?" and start their tiny portfolio site built upon a massively overpowered suite of enterprise-level software with a million features they'll never, ever need. Then they might drop in ten or fift…
Re: How we improved our website's performance
#46> Around the same time we switched from an (outdated) manually created critical CSS file to an automated system that was generating critical CSS for every template — homepage, article, product page, event, job board, and so on — and inline critical CSS during the build time. Yet we didn’t really realize how much heavier the automatically generated critical CSS was. Is reducing the total amount of CSS per page so you…
Re: How we improved our website's performance
#47"Modern" web development is apparently a game of Jenga.
Re: How we improved our website's performance
#48Earlier quoted context omitted.
Only because developers absolutely insist on building things that way, for some reason I will never comprehend. What's the first thing most people do when starting a new project? They ask "what framework should I build this on?" and start their tiny portfolio site built upon a massively overpowered suite of enterprise-level software with a million features they'll never, ever need. Then they might drop in ten or fift…
This is such a tired take. Logic has been moved from the backend to the frontend (again) which has justified the complexity.
Quite the opposite. It needs to be hammered into people. Your app isn't Notion or Google Docs. Your app is a form with a login menu and a couple of small logic elements and a date picker.
Re: How we improved our website's performance
#49Not fantastic: https://www.websitecarbon.com/website/smashingmagazine-com-2...
How do people come up with this shit?
Re: How we improved our website's performance
#50Earlier quoted context omitted.
Only because developers absolutely insist on building things that way, for some reason I will never comprehend. What's the first thing most people do when starting a new project? They ask "what framework should I build this on?" and start their tiny portfolio site built upon a massively overpowered suite of enterprise-level software with a million features they'll never, ever need. Then they might drop in ten or fift…
This is such a tired take. Logic has been moved from the backend to the frontend (again) which has justified the complexity.
For myself, I would appreciate more such takes.