Hi, Since the issue only happens when Jetpack is active, this is very likely related to one of Jetpack’s optimization features, not YouTube itself. Error 153 usually appears when the YouTube embed gets blocked, modified, or delayed.
Jetpack can sometimes interfere with iframe embeds through:
• Site Accelerator / CDN
• Lazy loading
• Script deferring / optimization
• Security or header filtering
I’d suggest testing step by step:
- Go to Jetpack → Settings → Performance
- Disable “Speed up static files” (Site Accelerator)
- Disable lazy loading for videos/images
- Turn off any script optimization features
- Clear cache and test again
In most cases, Site Accelerator or lazy load is the cause. If disabling those fixes it, you can re-enable features one by one to find the exact culprit. Let us know what you find 👍
Hi, thank you so much for your reply. As I mentioned, I have all Jetpack performance options disabled by default, since I control all those aspects with a caching plugin, specifically WP Rocket, which I also had disabled in my tests. It was the first thing I tried. After years of struggling with caching, that’s always the first thing to try 🙂
I’ve just found what’s causing the error, and it would be important to review it because it might be happening to other people as well. The problem disappears when you disable an option in the “Composing” section, the fourth option, “Compose using shortcodes to embed media from popular sites.”
By disabling this option, the videos load normally again, and error 153 disappears. I don’t know if this will affect other embeds; it’s something I had enabled many years ago and haven’t touched since.
Hi 🙂 thanks for sharing what you found — that’s actually a really helpful discovery.That Jetpack “Compose using shortcodes” option rewrites how embeds are rendered (it replaces the normal iframe with its own shortcode/output handling). In some cases this can modify the YouTube embed URL or add extra wrappers, which seems to trigger YouTube’s Error 153.
So it’s not really a caching issue — it’s Jetpack intercepting the embed before WordPress outputs the standard iframe. Disabling that option and letting WordPress handle native embeds is definitely the safest approach, especially if you already use WP Rocket for performance. Good catch 👍 this will probably help others too.
I certainly hope it helps someone.
