Asset Minification Checker
List script and stylesheet references so you can review delivery and build output.
Run the asset minification checker
Public website checkWhat asset minification checker helps you do
List script and stylesheet references so you can review delivery and build output. A file named app.min.js is only a naming clue. Inspect transferred bytes and source contents before deciding whether a build already removed unnecessary whitespace.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
A filename is not proof of minification; external asset contents may require a separate fetch and build inspection. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Confirm the build output before changing the build
A file named bundle.js may already be minified, while an old vendor.min.js file may contain a readable license and unnecessary code. Naming is evidence about intention, not the final transformation. Inspect a representative asset and compare its transfer with the build configuration. Keep minification separate from code splitting, unused-code removal and compression because they solve different problems. Third-party assets may not be under your control, so assess whether the integration is necessary before trying to rewrite their source. Validate any build change against a functioning page rather than judging success by a shorter filename.
Verify the result and continue
Compare a real asset from the production response with the build output you intend to publish. A local minified file is irrelevant if the page still references an old bundle. Check caching and asset hashes when a deployment seems to ignore the build change, then test the page functionality. Continue with the javascript minifier or explore the performance tool cluster.
How this tool works
List script and stylesheet references so you can review delivery and build output. The server fetches the submitted public URL with bounded redirects and response sizes. The result reports observed HTML, headers or network evidence for this specific check.
What the result does and does not establish
A filename is not proof of minification; external asset contents may require a separate fetch and build inspection.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow