There are 1000s of small items you can address to improve your site’s page rendering profile. Improving each one will improve your user experience, which leads to better search rankings and more conversions. HTTP/2 is a simple web performance optimization technique that all web sites should implement today. Now you can consolidate all your progressive web application features under a single domain, making it easier to manage your website.

1. ©2018 | Love2Dev
Love2Dev.com
Free Page Speed Improvements
Anyone Can Implement for Free
HTTP/2 Multiplexing vs
Old School Domain
Sharding

2. ©2018 | Love2Dev
Love2Dev.com
Read the Blog Post
HTTP/2 Multiplexing
vs Old School
Domain Sharding -
Free Page Speed
Improvements
https://love2dev.com/blog/domain-sharding-http-2/
300 x 100 px
Read The Blog Post

3. ©2018 | Love2Dev
Love2Dev.com
Backlinko SEO Audit Guide
Can Splitting
Resources Across
Domains Improve
Page Load Time?
https://backlinko.com/seo-site-audit

4. ©2018 | Love2Dev
Love2Dev.com
What is Domain Sharding
Identified by Steve Souders as a best practice in
the 2007 book High Performance Web Sites to
reduce page load times
https://amzn.to/2NrhiYw
HTTP/1.1 Best Practice
HTTP/1.1 specified 2 parallel connections. Most
browsers increased limit to 6. Most web pages
require dozens of responses to render
Browsers Limit Connections
Sharding distributes web assets across multiple
domains to increase total parallel HTTP
connections
Split Requests Across Domains
Sharding is a way to leverage more parallel
connections to grab more responses at the same
time.
Allows More Requests

5. ©2018 | Love2Dev
Love2Dev.com
Creating a connection between a client and server is an
expensive process. It not only requires network resources, but
also taxes the CPU and browser, actually reducing resources
needed to render the content.
Each connection requires an initial dialog or handshake between
client and server. This creates extra network latency.
This cost is amplified on mobile.
HTTP Connections
are Expensive
300 x 50 px

6. ©2018 | Love2Dev
Love2Dev.com
• HTTP/1 Opens Multiple
Connections
• 2 By Standard
• 6 By Convention
• TCP Competition
• Breaks Resource Prioritization
Server Browser
HTTP/1 Connections

7. ©2018 | Love2Dev
Love2Dev.com
What is HTTP/2
Multiple responses loaded in parallel. So assets get to the
browser faster with optimized prioritization. This reduces time to
render.
Improve User Perceived Latency
The use of a single connection eliminates redundant overhead to
create ‘faux’ multiplexed HTTP/1.1 connections. This also makes
TLS much more efficient.
Uses a Single Connection
HOL blocking happens because requests are broken down to
small packets. In HTTP/1.1 packets must be received in order.
HTTP/2 allows packets to be received and reassembled later,
eliminating this blocking effect.
Address ‘Head of Line Blocking’
HTTP/2 extends, not replaces HTTP/1.1. This means legacy
browsers can still connect to HTTP2 servers.
Retain HTTP/1 Semantics

8. ©2018 | Love2Dev
Love2Dev.com
Steve Souders
Why Domain Sharding is Not Needed
“"There’s no need for domain sharding in the world of HTTP
2.0 across all popular browsers."”

9. ©2018 | Love2Dev
Love2Dev.com
Multiplexed streams
Improves Performance By
Reducing Connections and
Optimizing Response
Delivery
Server Browser
HTTP/2
Connection

10. ©2018 | Love2Dev
Love2Dev.com
Most Content Delivery Network
Services Support HTTP/2
1
2
Modern Server Operating Systems
Support HTTP/2

11. ©2018 | Love2Dev
Love2Dev.com
There are 1000s of small items you can address to improve your
site’s page rendering profile. Improving each one will improve your
user experience, which leads to better search rankings and more
conversions.
HTTP/2 is a simple web performance optimization technique that all
web sites should implement today. Now you can consolidate all your
progressive web application features under a single domain, making
it easier to manage your website.
HTTP/2 By Default
Improve Page Load
468 x 60 px