Minify CSS for WordPress

WordPress sites commonly load five to fifteen separate CSS files on a single page: the active theme's style.css, a child theme stylesheet, stylesheets enqueued by WooCommerce, a contact form plugin, a slider, a page builder, and any other active plugins that register their own styles. Each of these files is frequently unminified and ranges from a few kilobytes to over 100KB. The cumulative weight of unminified WordPress CSS on a typical small business site regularly exceeds 300KB, contributing to PageSpeed Insights performance scores in the 50 to 70 range and failing Core Web Vitals thresholds on mobile. Minifying each stylesheet individually can cut that total by 30 to 80KB and push scores meaningfully higher without adding a caching plugin, configuring a CDN, or touching the server.

The WordPress-specific consideration when minifying CSS is the theme header comment. WordPress reads the block comment at the very top of style.css to identify the theme name, author, version, description, and other metadata required for the theme to appear in the WordPress admin. A standard minifier removes all CSS comments, including this required header block. After minifying the stylesheet body, you must manually paste the original theme header comment above the minified output before saving the file to your server. If this header is absent, WordPress will not recognise the theme as valid and will refuse to activate it. Plugin stylesheets do not have this requirement and can be minified and replaced without any manual comment handling.

For WordPress sites where frequent theme updates would overwrite manually minified stylesheets, the most sustainable approach is to create a child theme. The child theme's style.css contains only the required WordPress theme header comment that declares the parent theme, plus any CSS customisations you have written. You minify only the child theme CSS, and a parent theme update will never overwrite it. This child theme workflow gives you the full performance benefit of minification while completely protecting your style customisations from being lost. It also means the parent theme can be kept up to date without any risk to your performance optimisations.

WordPress sites that sit behind a CDN such as Cloudflare or BunnyCDN benefit twice from CSS minification: once at the WordPress origin where the smaller file is served to the CDN, and again at every edge node where the file is cached and replicated globally. Most CDN configurations apply gzip or Brotli compression on top of the already minified stylesheet, so the bytes transferred to each visitor are even smaller than the file you uploaded. The interaction between WordPress and a CDN does add one operational consideration: when you upload a new minified stylesheet after editing the source, purge the CDN cache for that specific file path or use a versioned filename so the CDN immediately starts serving the new version. Without a purge, the CDN may continue serving the previous cached version for hours after your upload.

Caching plugin compatibility is the single biggest variable in any WordPress CSS minification workflow because the major caching plugins each take a different approach to combining and serving stylesheets. WP Rocket includes a Minify CSS option in its File Optimisation panel that minifies and optionally combines all enqueued stylesheets on the fly; if you have already manually minified a stylesheet, leave the WP Rocket option enabled for the remaining unminified plugin stylesheets because a second pass on an already-minified file is harmless. W3 Total Cache exposes a similar Minify CSS setting and additionally lets you pick exactly which stylesheets to include in its minification pass, which is useful when one plugin's stylesheet breaks under combined minification and needs to be excluded. The WordPress block editor stylesheets enqueued under wp-includes and wp-content/themes/themename/style-editor.css are regenerated by core on every WordPress update and should generally be left to the caching plugin rather than minified manually; the maintenance cost of re-minifying after each core update outweighs the saving for files that are typically already small.