[wp-trac] [WordPress Trac] #56990: Render blocking CSS `classic-themes.css` unnecessarily enqueued

[WordPress Trac]

#56990: Render blocking CSS `classic-themes.css` unnecessarily enqueued
----------------------------------------+-------------------------------
 Reporter:  adamsilverstein             |       Owner:  flixos90
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  6.3
Component:  Themes                      |     Version:  6.1
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:  css, performance
----------------------------------------+-------------------------------

Comment (by adamsilverstein):

 > As an external resource, there is some non-zero amount of overhead in
 getting the resource out of cache that is likely much higher than the
 transfer time of the additional 200 bytes in the existing stream. An
 external resource is also more likely to cause delays from scheduling
 contention with other requests depending on how the origin supports
 prioritization.

 right, that makes sense @patrickmeenan - inlining will provide a
 negligible boost usually, but in some cases the impact could be more
 significant. There is also the resource impact of an additional request to
 the server to consider. It is only one request, however it is one request
 for every page load for every (non-block theme ie. 99% of) WordPress site.

 > If there is not an existing practice of inlining styles then starting to
 do it just for this is probably a bad precedent.

 We are in fact inlining block styles now and this are block styles, so
 inlining follows current proactive.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/56990#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform