Title: Critical CSS Issue
Last modified: September 26, 2021

---

# Critical CSS Issue

 *  Resolved [DK.Enterprises](https://wordpress.org/support/users/dkenterprises/)
 * (@dkenterprises)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/critical-css-issue-3/)
 * Hi,
    I received an error message: ‘Failed to fetch’ and a message to contact 
   support.
 * Can you help me please?
 * Cheers,
 * Douglas
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-css-issue-3%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Support [Animesh Gaurav](https://wordpress.org/support/users/bizanimesh/)
 * (@bizanimesh)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/critical-css-issue-3/#post-14919186)
 * Hi there,
 * This error means that the specified URL is loading content from a different domain
   or protocol. It usually means the specified URL is a redirect to an external 
   site. It is worth deactivating any plugins which add redirect URLs to the site
   for the duration of generating Critical CSS.

Viewing 1 replies (of 1 total)

The topic ‘Critical CSS Issue’ is closed to new replies.

 * ![](https://ps.w.org/jetpack-boost/assets/icon.svg?rev=2818794)
 * [Jetpack Boost - Website Speed, Performance and Critical CSS](https://wordpress.org/plugins/jetpack-boost/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack-boost/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack-boost/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack-boost/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack-boost/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack-boost/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Animesh Gaurav](https://wordpress.org/support/users/bizanimesh/)
 * Last activity: [4 years, 8 months ago](https://wordpress.org/support/topic/critical-css-issue-3/#post-14919186)
 * Status: resolved