News for hackers. Stuff that matters.
Re:How we improved our website's performance by sdoering on Sunday January 24, 2021 @04:39PM (#25896374)
But with 8kb zipped (I assume that following pages aren't that much worse) why should one optimize with a solution that adds that much complexity?

I believe that shaving a few additional kb from this already low number isn't worth the proposed complexity.

But this is a tradeoff that everybody has to decide for themselves.

Re:How we improved our website's performance by markdown on Sunday January 24, 2021 @05:07PM (#25896645)
> But with 8kb zipped (I assume that following pages aren't that much worse) why should one optimize with a solution that adds that much complexity?

If that's the argument, why not just let them take the (tiny) initial 8kb hit as an external css file, and make the rest of the experience even "zippier"?

Re:How we improved our website's performance by seanwilson on Sunday January 24, 2021 @05:12PM (#25896701)
> why not just let them take the (tiny) initial 8kb hit as an external css file,

One reason is Google will likely ding your Core Web Vitals score for it, which is becoming a ranking signal in May this year (https://developers.google.com/search/blog/2020/11/timing-for...) so you have less of a choice here for what you prioritise.

Re:How we improved our website's performance by sdoering on Monday January 25, 2021 @01:50AM (#25900111)
I would believe that 8k via an additional request would harm performance more than to inline it.

But haven't tested that yet.

Re:How we improved our website's performance by markdown on Monday January 25, 2021 @05:23AM (#25901610)
It would most certainly marginally harm performance a single time, but every additional page load would be much improved.