Even this is more complex than many websites need to be. A few months ago I wrote about why I often create pages in pure html and css.

https://joeldare.com/why-im-writing-pure-html-and-css-in-202...

▲

inigyou a day ago | parent [-]

Regarding small pages - there's a certain size threshold where the entire HTTP response is sent back in the first TCP window for most client OSes, which allows minimum round-trips.

▲

codazoda a day ago | parent [-]

Yes. You might be talking about the 14Kb problem.

https://joeldare.com/the-14kb-problem

▲

lelandfe a day ago | parent [-]

That post is so abbreviated as to be wrong in a few places (for instance, it's not that your "HTML" needs to be under 14kB, the packet, incl. headers needs to be). Fuller link: https://www.tunetheweb.com/blog/critical-resources-and-the-f...

It's not worth chasing except for personal curiosity and some truly extreme cases.

	▲	inigyou a day ago \| parent [-]
		The response needs to be. The response can span several packets, up to the maximum receive window chosen by the client's OS.