WEBVTT

00:00:00.000 --> 00:00:06.000
Can a website send the same content in fewer bytes?

00:00:06.000 --> 00:00:13.000
HTTP compression can shrink suitable responses during transfer.

00:00:13.000 --> 00:00:18.000
Understand compressed delivery.
6 useful checks.

00:00:18.000 --> 00:00:30.000
Start with suitable content
HTML, CSS and JavaScript are common candidates for compression.
HTML response · CSS stylesheet · JavaScript file

00:00:30.000 --> 00:00:42.000
The browser advertises support
A request can tell the server which encodings it understands.
Browser capability · Supported encodings · Request headers

00:00:42.000 --> 00:00:54.000
The server sends compressed data
The browser decodes the response before using the content.
Smaller transfer · Content encoding · Decoded content

00:00:54.000 --> 00:01:06.000
Know the common names
Gzip and Brotli are compression methods used on the web.
Gzip · Brotli · Suitable server setup

00:01:06.000 --> 00:01:18.000
Already compressed files differ
Compressing a photo or video again may offer little benefit.
Image encoding · Video encoding · Measure the saving

00:01:18.000 --> 00:01:30.000
Verify actual delivery
Ask your developer to inspect transferred size and response headers.
Correct encoding · Transferred bytes · Working page

00:01:30.000 --> 00:01:39.000
Your checklist
Start with suitable content · The browser advertises support · The server sends compressed data · Know the common names · Already compressed files differ · Verify actual delivery

00:01:39.000 --> 00:01:47.000
Check that compression helps the actual response.
jerseyweb.je
