Apache Mod Pagespeed合并JS功能未完全生效问题排查

Let’s walk through the likely reasons your combine_javascript filter isn’t merging every JavaScript file into single bundles, using the code snippets you shared:

• File size thresholds
  ModPagespeed has default limits on how large a combined JS file can be (usually around 200KB by default via ModPagespeedMaxCombinedJsBytes). If some of your individual JS files are large, or combining a group would exceed this limit, Pagespeed will split them into smaller bundles instead of creating one oversized file—this is intentional, as overly large files hurt load times rather than improving them.

• Dependency preservation
  Look at your original scripts: jQuery loads first, followed by jQuery UI. ModPagespeed is built to avoid breaking your site’s functionality—since jQuery UI depends entirely on jQuery being available before it runs, Pagespeed will keep these two separate to maintain the correct execution order. Combining them could lead to errors where jQuery UI tries to run before jQuery is fully loaded.

• Cache-busting query string inconsistencies
  Notice that main.min.js still uses its original ?v=45.3.68 cache-buster instead of being processed into the ,qv=... format like others. Pagespeed treats query strings as part of the file’s identity by default—if files have different query strings, it may not combine them, assuming they’re distinct versions. You can adjust this behavior or switch to using filename hashes for cache-busting instead of query strings.

• Dynamic script logic
  The eval(mod_pagespeed_...) calls in your processed output indicate that some scripts contain dynamic code (like document.write, or logic that depends on the script’s execution context). Pagespeed can’t safely combine these scripts into a bundle without risking broken functionality, so it splits them out and rewrites them as inline eval calls instead.

• Filter interactions or excluded paths
  While collapse_whitespace and elide_attributes shouldn’t conflict with combine_javascript, it’s worth checking if you have any ModPagespeedDisallow directives in your .htaccess or server config that exclude specific JS paths from processing. Also, double-check that all your JS files are served with the correct MIME type (application/javascript)—Pagespeed won’t process files it doesn’t recognize as JavaScript.

Quick Tests to Confirm #

To narrow down the issue:

1. Temporarily increase the combined file size limit with ModPagespeedMaxCombinedJsBytes 500000 in your .htaccess and reload the page to see if more files are bundled.
2. Check your Apache error logs for Pagespeed-specific warnings—they’ll often log why a file was skipped from combination.
3. Remove the ?v=45.3.68 cache-buster from one or two files and see if Pagespeed then includes them in a bundle.

内容的提问来源于stack exchange，提问作者Vivek Tankaria