[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:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.1.2
Component:  Themes                   |     Version:  6.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css, performance
-------------------------------------+-------------------------------

Comment (by wpgurudev):

 I have tested with TwentyTen theme with (attached are the links to
 WebPageTests)

 1.[https://www.webpagetest.org/result/230120_BiDcWY_4A4/?test=230120_BiDcWY_4A4&medianMetric=chromeUserTiming.LargestContentfulPaint
 External CSS File]

 2.[https://www.webpagetest.org/result/230120_AiDc0P_4H7/?test=230120_AiDc0P_4H7&medianMetric=chromeUserTiming.LargestContentfulPaint
 Inline CSS]


 a. It has been observed that `DomContentLoaded` event is occurring earlier
 when external script is used.

 b. We can see from the network tab screenshot,
 [https://i.postimg.cc/SNg9jDxz/external-style.png External stylesheet] and
 [https://i.postimg.cc/SKBCkRNT/inline-style.png Inline CSS] that
 `DomContentLoaded` is occurring earlier with external stylesheet.

 c. When we add the inline style to the page, the overall size of the page
 increases from 6.1 KB to 6.4 KB

 d. However; in the external request, size is only 391 Bytes.


 From the above results it looks like the external file is producing better
 results compared to inline style.

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