LiteSpeed Web Server supports QUIC and powers more than 97% of QUIC-enabled web sites wordwide.

What Is QUIC?

QUIC is the next generation internet protocol initially developed by Google. It's enabled by default in the Google Chrome browser.


  • A new protocol developed by Google to improve upon HTTP/2, and constructed with security in mind.
  • The next generation internet protocol, engineered to reduce latency due to handshake and packet loss.
  • Currently undergoing standardization with the IETF's QUIC working group.

A New Protocol

QUIC QUIC is a new protocol developed by Google, currently undergoing standardization with the IETF's QUIC working group.

QUIC (or, Quick UDP Internet Connection) is an experimental protocol initially developed by Google in 2012, and announced publicly the following year.
As of mid-2015, roughly half of all requests from Chrome to Google servers were served over QUIC.
Google's goal since then has been to ramp up QUIC traffic , eventually making it the default transport from Google clients to Google servers.
Just as with SPDY, Google is encouraging the efforts to make QUIC an internet standard, a move which is bound to speed up its widespread adoption.

Enabled By Default

QUIC has been enabled by default in Chrome since August 2013 and was recently made available in Opera.

Chrome and Opera web browsers support QUIC by default and will use it if the server supports it.
Chrome dominates the browser market; together with Opera, these two browsers represent about 62% of web users.
Enable QUIC on your site, and the majority of visitors will see the difference.
Enabled by Default

The Next Generation

Next GenerationQUIC is the next generation internet protocol, designed to make up for the shortcomings of HTTP/2.

Web protocols are always evolving and improving.
HTTP gave way to SPDY, which was refined into HTTP/2, and now there's QUIC.
Just as SPDY's aim was to improve upon the inadequacies of HTTP/1, so too is QUIC poised to improve and replace HTTP/2.

Built With Security In Mind

QUIC was built with security in mind, incorporating features missing within UDP itself.

Due to concern for their users' privacy, more and more websites have been switching to using secure connections.
HTTPS and HTTP/2 are TCP-based, secure web protocols.
Their security, however, comes with a price: it takes longer to establish a connection.
QUIC reduces the time it takes to begin serving content by a factor of two or three, while maintaining data security.
Built with Security

Engineered To Reduce Latency

Reduce LatencyQUIC was engineered to reduce latency due to handshake and packet loss.

Traditionally, HTTP connections have relied on TCP to deliver packets,
but TCP brings with it a time-consuming handshake and a tendency toward head-of-line blocking due to lost packets.
QUIC addresses these inadequacies by replacing TCP with UDP.
This allows QUIC to define its own more efficient handshake protocol,
and employ multiplexing streams to avoid blockages caused by individual lost packets.