- This topic has 1 reply, 2 voices, and was last updated 2 weeks, 5 days ago by
vako.
-
AuthorPosts
-
December 18, 2025 at 11:43 pm #77560
While using WP-Optimize 4.4.0, I ran into the following two errors. Is there a way to fix these?
1. Error: Unable to Check GZIP Compression. We encountered a problem while checking if GZIP compression is enabled.
The server responded with a 403 403 Forbidden error whilst trying to open the URL: https://simplygreatrecipes.com/wp-content/themes/ashe-pro-premium/style.css. Please contact your website administrator to resolve this. Once the issue is addressed, try again.
2. Error: Unable to Check browser cache. We encountered a problem while checking if browser cache is enabled.
The server responded with a 403 403 Forbidden error whilst trying to open the URL: https://simplygreatrecipes.com/wp-content/themes/ashe-pro-premium/style.css. Please contact your website administrator to resolve this. Once the issue is addressed, try again.
December 19, 2025 at 10:12 pm #77563Hi,
Thank you for the details.
Those two WP-Optimize errors are **not related to the Ashe Pro theme**. The key point is the **403 Forbidden** response when WP-Optimize tries to fetch this file:
https://simplygreatrecipes.com/wp-content/themes/ashe-pro-premium/style.cssA **403** is a server/security permission block, typically caused by one of the following:
* Hosting/firewall rules (WAF)
* A security plugin (Wordfence, iThemes, Sucuri, etc.)
* Server rules in
.htaccess/ Nginx config* Hotlink protection or bot protection
* Cloudflare / CDN rules
Because WP-Optimize cannot access that file, it fails to verify GZIP and browser cache.
What to do next:
1. Check your hosting/security layer for rules blocking automated requests to
/wp-content/or specificallystyle.css.2. Temporarily disable any security plugin and test again.
3. Contact your hosting provider and ask them to whitelist WP-Optimize’s check requests or remove the rule generating the 403.
4. If needed, contact **WP-Optimize support**, since it is their tool running the checks and they can tell you exactly what user-agent/IP/request pattern is being blocked.
From the theme side, there is nothing to change — the theme is simply a file being requested, and your server is refusing access.
Kind Regards
-
AuthorPosts
- You must be logged in to reply to this topic.
