Title: Hummingbird Error
Last modified: February 10, 2022

---

# Hummingbird Error

 *  Resolved [gentixharavina](https://wordpress.org/support/users/gentixharavina/)
 * (@gentixharavina)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/hummingbird-error/)
 * So i just enabled the Gzip compression and now all over the WP Dashboard “There
   has been a critical error on this website. Please check your site admin email
   inbox for instructions.”
 * I did not receive an email and also the error is all over the dashboard and cant
   access any other sections to work on and fix the error, I tried renaming the 
   plugin folder but that didnt work either.
 * Please help.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fhummingbird-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [Nithin – WPMU DEV Support](https://wordpress.org/support/users/wpmudevsupport11/)
 * (@wpmudevsupport11)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/hummingbird-error/#post-15350726)
 * Hi [@gentixharavina](https://wordpress.org/support/users/gentixharavina/),
 * > I tried renaming the plugin folder but that didnt work either.
 * If the plugin folder is renamed, then if it was related to Hummingbird, then 
   the website should have been loading back again.
 * Since you did mention it occurred after enabling Gzip, could you please open 
   the .htaccess file located in the Root directory and check it makes any difference
   if the rules related to the Gzip inside the .htaccess is removed?
 * The root directory is where you have /wp-admin, /wp-content and /wp-includes 
   folders.
 * You should find the Gzip rules added inside the following comment in the .htaccess
   file:
 *     ```
       # BEGIN WP-HUMMINGBIRD-GZIP
   
       Gzip rules in here
   
       # END WP-HUMMINGBIRD-GZIP
       ```
   
 * Even after removing the code inside .htaccess and with the plugin folder renamed
   if you still face the same critical error then I’m afraid this might be more 
   related to some other conflict.
 * You could try enabling Debug mode and see whether it helps give a better idea
   of the critical error noticed.
 * You can find more details about debugging here:
 * > [Debugging in WordPress](https://wordpress.org/support/article/debugging-in-wordpress/)
 * Kind Regards,
    Nithin
 *  Plugin Support [Amin – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support2/)
 * (@wpmudev-support2)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/hummingbird-error/#post-15383059)
 * Hello [@gentixharavina](https://wordpress.org/support/users/gentixharavina/) ,
 * We haven’t heard from you for some time now, so it looks like you don’t need 
   our assistance anymore.
 * Feel free to re-open this ticket if needed.
 * Kind regards
    Kasia

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Hummingbird Error’ is closed to new replies.

 * ![](https://ps.w.org/hummingbird-performance/assets/icon-256x256.gif?rev=2633221)
 * [Hummingbird Performance - Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN](https://wordpress.org/plugins/hummingbird-performance/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hummingbird-performance/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hummingbird-performance/)
 * [Active Topics](https://wordpress.org/support/plugin/hummingbird-performance/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hummingbird-performance/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hummingbird-performance/reviews/)

## Tags

 * [dashboard](https://wordpress.org/support/topic-tag/dashboard/)

 * 2 replies
 * 3 participants
 * Last reply from: [Amin – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support2/)
 * Last activity: [4 years, 2 months ago](https://wordpress.org/support/topic/hummingbird-error/#post-15383059)
 * Status: resolved