If your website isn’t loading properly in Firefox while using Cloudflare, you’re not alone. Many webmasters have recently noticed that their sites either fail to load, get stuck on a white screen, or endlessly refresh — especially when Cloudflare’s HTTP/3 (with QUIC) is enabled.
Below, we’ll explain why this happens, how to fix it in minutes, and what it means for your website performance and SEO.
What Causes the Problem?
Cloudflare’s HTTP/3 (with QUIC) is an experimental protocol designed to make websites load faster and more securely. However, some versions of Firefox have compatibility issues with QUIC connections, resulting in incomplete TLS handshakes or page timeouts.
This problem is most common when:
-
You use Cloudflare’s “Always Use HTTPS” and “Automatic HTTPS Rewrites” together.
-
Your browser (Firefox) has HTTP/3 enabled but conflicts with the QUIC handshake.
-
The website relies on custom caching, redirects, or security headers that confuse the protocol negotiation.
How to Fix It: Disable HTTP/3 (with QUIC) in Cloudflare
-
Log in to your Cloudflare dashboard.
-
Select the domain that’s having the issue.
-
Go to Network settings in the left menu.
-
Find the option “HTTP/3 (with QUIC)”.
-
Toggle it off.
-
Wait a few minutes for Cloudflare’s cache and network settings to propagate.
-
Clear your browser cache and reload the page in Firefox.
After this change, your website should load normally again in Firefox, Chrome, Safari, and all other browsers.
Will Disabling HTTP/3 Affect Site Speed?
Only minimally — and often not at all. Most users are still connecting via HTTP/2, which is extremely fast and reliable. The benefits of HTTP/3 are marginal compared to having your site load inconsistently or not at all.
For SEO and user experience, stability and accessibility matter far more than experimental speed gains.
