[wp-trac] [WordPress Trac] #63018: Increase styles_inline_size_limit from 20, 000 bytes

[WordPress Trac]

#63018: Increase styles_inline_size_limit from 20,000 bytes
---------------------------+-------------------------------
 Reporter:  westonruter    |       Owner:  westonruter
     Type:  enhancement    |      Status:  closed
 Priority:  normal         |   Milestone:  6.9
Component:  Script Loader  |     Version:  5.8
 Severity:  normal         |  Resolution:  fixed
 Keywords:                 |     Focuses:  css, performance
---------------------------+-------------------------------

Comment (by westonruter):

 As I just [https://github.com/GoogleChromeLabs/wpp-
 research/pull/201#issuecomment-3447997500 commented] on the wpp-research
 PR, I just realized that I was testing without far-future expiry on the
 static assets. So the cached results were still involving conditional
 requests which returned `304 Not Modified`. I patched the wordpress-
 develop environment to ensure far-future expires were present:

 {{{#!diff
 diff --git a/tools/local-env/default.template b/tools/local-
 env/default.template
 index 995913fb45..ecce8ea780 100644
 --- a/tools/local-env/default.template
 +++ b/tools/local-env/default.template
 @@ -25,6 +25,11 @@ server {
                 try_files $uri $uri/ /index.php?$args;
         }

 +       location ~* \.(js|css|png|jpg|jpeg|gif|ico|svg)$ {
 +               expires 1y;
 +               add_header Cache-Control "public, no-transform";
 +       }
 +
         location ~ \.php$ {
                 try_files $uri =404;
                 fastcgi_split_path_info ^(.+\.php)(/.+)$;
 }}}

 And I re-ran the results. As seen in [attachment:"increasing-css-inline-
 size-limit.png"], the results are very similar.

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