Today I Learned - Rocky Kev

TIL critical 14kb

POSTED ON:

TAGS:

On the OSI Model -- the physical layer, we send data in 14kb packets.
And servers respond to HTTP requests in 14kb chunks. (Note: It can be set to different sizes, but by default... 14kb is the standard/magic number)

A real-world example:

If you had a 250kb image, it'll take 18 packets of data. It'll be will be sent one-at-a-time for it: 17 packets 14kb in size, plus one not-quite-12kb one.

And if you had a 5kb CSS file, it'll take 1 packet of data.

The thing about each request and packet, it requires a tiny handshake. It's in the milliseconds.

Major takeaway

I'm purposely ignoring the whole "make critical resources under 14kb" argument.

My argument is more about little things like SVGs or CSS files that are super-tiny. Rather than turn them into separate file requests, make them inline for performance.

Via https://www.tunetheweb.com/blog/critical-resources-and-the-first-14kb/


Related TILs

Tagged:

TIL critical 14kb

On the OSI Model -- the physical layer, we send data in 14kb packets. And servers respond to HTTP requests in 14kb chunks. (Note: It can be set to different sizes, but by default... 14kb is the standard/magic number)

TIL critical 14kb

On the OSI Model -- the physical layer, we send data in 14kb packets. And servers respond to HTTP requests in 14kb chunks. (Note: It can be set to different sizes, but by default... 14kb is the standard/magic number)

TIL critical 14kb

On the OSI Model -- the physical layer, we send data in 14kb packets. And servers respond to HTTP requests in 14kb chunks. (Note: It can be set to different sizes, but by default... 14kb is the standard/magic number)