Explore >> Select a destination
|
You are here 
|
byroot.github.io | ||
| | | | |
sookocheff.com
|
|
| | | | | Note: To make this easier to read (and write), h1 may be used in place of HTTP/1, and h2 may used in place of HTTP/2. HTTP/1 has a long and storied history. Originally developed as a sixty page specification documented in RFC 1945, it was designed to handle text-based pages that leverage hypermedia to connect documents to each other. Typical web pages would kilobytes of data. For example, the first web page was a simple text file with web links to other text documents. Now, the web is made up of media-rich sites containing images, scripts, stylesheets, fonts, and more. The size of a typical web page is measured in megabytes rather than kilobytes, and the number of requests required to assemble a full page can be over one hundred. The reality of how web pages... | |
| | | | |
scorpil.com
|
|
| | | | | Short history of HTTP protocol | |
| | | | |
shortdiv.com
|
|
| | | | | Though we as developers can influence how the browser downloads resources, the browser ultimately gets the last say when it comes to the order in which to load content. In this post, we dive into the new and exciting features that HTTP/2 brings. | |
| | | | |
ahrefs.com
|
|
| | | Cumulative Layout Shift measures the visual stability of a page as it loads, and it's a CWV metric Google uses. | ||
