1.6 HTTPS / security / infrastructureLowInferred

HTTP/2 or HTTP/3 not enabled

Sitting on HTTP/1.1 only means losing the multiplexing and efficiency of HTTP/2 and HTTP/3. Most CDNs offer the newer protocols for free, so there is little reason not to use them.

What it is

Legacy HTTP/1.1 only.

Why it matters

Misses multiplexing/perf gains.

How to fix it

Enable HTTP/2+ at server/CDN.

How to find it on your site

  1. Check the protocol in the DevTools Network tab Protocol column.
  2. Confirm whether your server or CDN supports HTTP/2 and HTTP/3.
  3. Enable the newer protocols at the server or CDN level.
  4. Re-test that connections negotiate h2 or h3.

Cross-reference to ranking and citation factors

Newer protocols improve load efficiency, which indirectly supports Core Web Vitals. The gain is modest but free.

Impact

Low. Inferred.

Evidence

Modern protocols aid performance. web.dev, Core Web Vitals (Google)

← Mixed content warningsCSP blocking needed resources →