[wp-meta] [Making WordPress.org] #5858: Inline custom CSS on /news/ pages

[Making WordPress.org]

#5858: Inline custom CSS on /news/ pages
--------------------------------+-----------------------
 Reporter:  jonoaldersonwp      |       Owner:  (none)
     Type:  enhancement         |      Status:  reopened
 Priority:  lowest              |   Milestone:
Component:  WordPress.org Site  |  Resolution:
 Keywords:  performance seo     |
--------------------------------+-----------------------

Comment (by jonoaldersonwp):

 300ms for a tiny CSS file is, absolutely, "unreasonably slow"; if we care
 about (and want to compete on) performance, user experience and SEO -
 which we should - we should be aiming for < 60ms for these kinds of
 resources.

 Given that's unlikely to happen here - due to the limitations of our
 setup, resourcing and politics - we should be looking (regardless) for
 alternative ways to improve the overall speed and performance of our
 page(s). We'll find that by making a thousand tiny improvements to a
 thousand tiny things.

 Inlining this file is one such tiny thing. But if we have to spend hours
 arguing over each one, then we'll never make reasonable inroads on the
 overall speed and performance of the site(s).

 These pages will load more quickly (from cold) if this is inline'd, and
 the benefits to every cold visit we get warrants the relatively minor
 investment to implement it.

 Warm visits will indeed miss out on having the resource cached by their
 browser (though they'll benefit from the gzip'd as part of the document
 content), but there are a thousand other small optimizations that we can
 make to claw back that difference and to improve ''both'' flavours of
 experience by an order of magnitude.

 Whilst it can seem counter-intuitive, there are good reasons why we're
 gradually moving to inlining resources like this in WordPress core (e.g.,
 for G'berg blocks). This isn't dissimilar to the approach which AMP (and
 other, similar performance frameworks) implement which are some of the
 fastest sites on the net by design - and the same logic applies in this
 case.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5858#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org