# CSS & JS Minification Test

https://rankproof.eu/tools/seo-minification-test

## Short answer

Check if CSS, JavaScript, and HTML are properly minified.

## What It Does

Scans the inline `<style>` blocks, inline `<script>` blocks, and raw HTML markup on the page for extra whitespace and comments, then estimates how much smaller each would be if minified. Returns an estimated byte saving for HTML, CSS, and JS separately.

## How It Works

1. Enter a page URL or paste its HTML
2. We scan the inline `<style>` and `<script>` blocks in the page HTML
3. Analyze byte-level whitespace and comment density in each block
4. Return pass/fail status for HTML, CSS, and JS with an estimated KB saving

## Sample input + output

INPUT

```text
url: https://rankproof.eu
```

OUTPUT

```text
HTML: minified              98% reduction      OK
CSS:  minified              94% reduction      OK
JS:   minified               91% reduction     OK
total size: 42.1 KB → 6.8 KB (84% smaller)     OK
external <link>/<script> tags: 4               —
comments stripped: yes                         OK
```

## Why It Matters

Unminified code is larger than it needs to be: the browser downloads the same instructions plus spaces and comments. Inline <style> and <script> blocks added by a CMS or page builder are easy to miss because they never pass through a build step. Smaller render-blocking CSS can help the page start rendering sooner.

## Who Uses This

- **Performance Engineer**: Before a big sales day, check the inline code on key pages; every kilobyte counts on slow mobile connections.
- **Frontend Developer**: Confirm any inline `<style>` or `<script>` your page builder injects is actually minified — catch the day a CMS export starts shipping raw, unminified blocks.
- **DevOps Engineer**: Re-check the page after every deploy — catch the day a CMS update starts shipping unminified inline blocks again.

## Frequently Asked Questions

### What's a typical size reduction?

It depends on how the code was written. Minification removes whitespace and comments; compression with gzip or Brotli, usually handled by your web server, saves more on top. Minify first, then let the server compress.

### Does minification affect SEO?

Indirectly. Smaller files can make the page render sooner, which helps Core Web Vitals. Core Web Vitals are one of many signals Google uses, not a guaranteed ranking boost.

### What about source maps?

Browsers download source maps only when someone opens the developer tools, so they do not slow the page. Publishing them makes your original source readable to anyone, so decide whether that is acceptable.

### What about third-party scripts I don't control?

You can't minify them — but you can self-host the latest minified version, use `defer`, or remove non-essential third-parties.

### Should I minify HTML too?

It helps a little. HTML compresses well, so the saving after compression is usually small, but it costs nothing if your CMS or build step supports it.

## Related Tools in SEO Analysis

- [Title & Meta Description Checker](https://rankproof.eu/tools/seo-meta-title)
- [Heading Tag Checker](https://rankproof.eu/tools/seo-heading-tags)
- [Image Alt Text Checker](https://rankproof.eu/tools/seo-image-alt)
- [Canonical URL Checker](https://rankproof.eu/tools/seo-canonical-url)
- [Robots.txt Analyzer](https://rankproof.eu/tools/seo-robots-txt)
- [robots.txt Generator](https://rankproof.eu/tools/seo-robots-txt-generator)