🔍 What the Warning Means
The Site Audit flag Server compression not enabled means a page, script, or stylesheet was delivered without being compressed (usually with Gzip or Brotli). Compressed files are smaller, so pages load faster and use less bandwidth. Faster pages support better user experience and SEO performance.
The audit reports the problem but cannot see how your site is hosted, so it does not tell you where the fix has to happen.
🧭 Why GHL Sites Are Different
Compression is set on the server that delivers your pages, not at your domain registrar or DNS provider. A site built in GoHighLevel (GHL) is delivered from GHL's servers. That has two practical effects:
- You normally cannot edit server settings such as compression rules inside GHL, as you could on your own hosting account.
- Changing DNS records at another provider, such as Hostinger, does not switch compression on. DNS only tells browsers where to find your site. It does not change how the files are sent.
If your domain is registered or managed at Hostinger but your site is built and hosted in GHL, Hostinger's hosting and compression settings do not apply to your GHL pages.
✅ Step 1: Check Whether Compression Is Actually Active
Sometimes the warning is triggered by one file rather than the whole site. Confirm what is really happening before making changes:
- Open the affected page in Google Chrome.
- Right-click anywhere on the page and choose Inspect, then open the Network tab.
- Refresh the page.
- Click the main page file (the first item in the list) and open the Headers section.
- Under Response Headers, look for content-encoding. If it shows gzip or br, that file is compressed.
- Click a few of the larger script and stylesheet files and repeat the check.
- Create an account with the CDN or proxy provider and add your domain.
- Copy your current DNS records from Hostinger and save them somewhere safe. This is your backup.
- Recreate the same records in the CDN provider, making sure the records that point to GHL stay exactly as GHL instructs.
- Update the nameservers at Hostinger to the ones the CDN provider gives you, if the provider requires it.
- Enable compression in the CDN settings (often called Gzip or Brotli).
- Wait for DNS changes to take effect, which can take a few hours, then confirm your site loads correctly and the SSL certificate is valid.
- Compress images before uploading them, and use modern formats such as WebP where possible.
- Remove unused sections, large videos, and animations.
- Limit custom code, plugins, and third-party widgets.
- Avoid uploading large PDF or media files that are embedded directly on the page.
- Your main page is already compressed: No action is needed. The warning is likely caused by third-party files.
- Your page is not compressed and you want to fix it: Use the CDN or proxy method in Step 2. Since your DNS is at Hostinger, you would make the change there, either by updating nameservers or the records the CDN asks for.
- You prefer not to change DNS: Focus on Step 3 to reduce page size and improve speed.
If the main page is compressed and only a few third-party files are not, the warning is low risk. Those files are usually served by other companies, such as tracking or chat tools, and you cannot change how they are delivered.
🌐 Step 2: Add a CDN or Proxy in Front of GHL (Optional)
If your pages are not being compressed and you want to control this yourself, the usual approach is to place a content delivery network (CDN) or proxy service, such as Cloudflare, between visitors and GHL. These services can compress files before delivering them.
Because your DNS records are managed at Hostinger, this path involves changes at the DNS level:
Important: A mistake in DNS can take your site offline or break your GHL domain connection. Always keep a backup of your original records, and make changes during a quiet period. If your CDN has a proxy mode, test your GHL domain verification and SSL after any change.
⚡ Step 3: Reduce Page Weight Inside GHL
Even if you cannot control server compression, you can make your pages lighter so the warning matters less:
🔄 Step 4: Re-run Your Site Audit
After making changes, clear your browser cache and run a new audit in Search Atlas. If the warning remains, check the Network tab again to see which files are still uncompressed.
❓ Which Option Should I Choose?
If you were given a numbered list of options and are not sure what Option 2 refers to for your setup, our team can confirm the best choice for your specific site before you change any DNS records.
💬 Need More Help?
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.