Compress resources with gzip or Brotli and enable HTTP/2.
- Compress resources with gzip or Brotli and enable HTTP/22 cited sources2 categories
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Compression and modern protocols reduce transfer sizes and latency improving load times.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Configure server or CDN to serve gzip or Brotli compressed files.
- Enable HTTP/2 protocol on web server to allow multiplexing.
- Test resources with browser devtools for compression and protocol usage.
- Check for asset fallback mismatches and fix accordingly.
- Monitor page load improvements post implementation.
Watch for
Uncompressed resources increase bandwidth usage and slow loading.
Definition of done
Server serves compressed files over HTTP/2 with significantly reduced initial load times.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.