[wp-trac] [WordPress Trac] #57548: Stop concatenating scripts and stylesheets in wp-admin and retire load-scripts.php and load-styles.php

WordPress Trac noreply at wordpress.org
Mon Sep 1 22:41:07 UTC 2025


#57548: Stop concatenating scripts and stylesheets in wp-admin and retire load-
scripts.php and load-styles.php
---------------------------+---------------------
 Reporter:  azaozz         |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  6.9
Component:  Script Loader  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+---------------------

Comment (by peterwilsoncc):

 My understanding is that there are still benefits from concatenation with
 HTTP/2, particularly on servers configured with compression.

 While it is true that assets can be downloaded in parallel, each file will
 have it's own compression dictionary. For example, each CSS file will have
 entries for `color`, `background`, `font`, `font-size`, etc.

 By concatenating the requests WordPress is reducing the number of
 dictionaries that need to be transferred across the wire. Harry Roberts
 documents the results in a post on [https://csswizardry.com/2023/10/the-
 three-c-concatenate-compress-cache/?ref=urbanisierung-dev#-concatenate
 HTTP performance].

 Rather than rely on instinct, it would be good to get some data on the
 benefits for common screens: the dashboard, the post list, the post
 editor.

 As WP is all-or-nothing at the moment with concatenation, another
 comparison point is to check limiting the number of script in a single
 concatenated request to N files.

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


More information about the wp-trac mailing list