{"id":51990,"date":"2020-02-20T13:16:41","date_gmt":"2020-02-20T12:16:41","guid":{"rendered":"https:\/\/www.humanlevel.com\/sin-categorizar\/http3-y-quic.html"},"modified":"2023-11-27T18:28:47","modified_gmt":"2023-11-27T17:28:47","slug":"http3-and-quic","status":"publish","type":"post","link":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic","title":{"rendered":"HTTP\/3 and QUIC, what do they mean for the web?"},"content":{"rendered":"<div id=\"toc_container\" class=\"no_bullets\"><p class=\"toc_title\">Index<\/p><ul class=\"toc_list\"><li><a href=\"#What_is_QUIC\">What is QUIC?<\/a><ul><li><a href=\"#How_does_it_work\">How does it work?<\/a><\/li><li><a href=\"#QUIC_protocol_characteristics\">QUIC protocol characteristics:<\/a><\/li><\/ul><\/li><li><a href=\"#Brief_history_of_QUIC\">Brief history of QUIC<\/a><\/li><li><a href=\"#Current_HTTP3_usage\">Current HTTP\/3 usage<\/a><\/li><li><a href=\"#How_do_I_know_if_a_website_uses_HTTP3\">How do I know if a website uses HTTP\/3?<\/a><\/li><li><a href=\"#Conclusion\">Conclusion<\/a><\/li><li><a href=\"#Bibliography\">Bibliography<\/a><\/li><\/ul><\/div>\n<p>In 2015 we announced the release <a href=\"https:\/\/www.humanlevel.com\/en\/blog\/web-development\/http-2-protocol-standard-approved\" target=\"_blank\" rel=\"noopener noreferrer\">of the HTTP\/2 protocol standard<\/a>. Only 5 years later, we can already analyze the upcoming implementation of the <strong>HTTP\/3 protocol and the QUIC protocol<\/strong> on which it relies. <a href=\"https:\/\/cloudplatform.googleblog.com\/2018\/06\/Introducing-QUIC-support-for-HTTPS-load-balancing\" target=\"_blank\" rel=\"noopener noreferrer\">According to Google, it will improve performance by 8% to 15%<\/a>.<\/p>\n<p><a href=\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/javascript-optimization\" target=\"_blank\" rel=\"noopener noreferrer\">HTTP\/2 brought performance improvements<\/a> and the ability of the server to send unsolicited files with <a href=\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/improve-wpo-with-http2-server-push\" target=\"_blank\" rel=\"noopener noreferrer\">server push transfers<\/a>, although it is still difficult to find hosting services that allow the latter.<\/p>\n\n<p>Since it took <strong>15 years from the definition of the HTTP\/1.1 standard to HTTP\/2<\/strong> and <strong>only 5 or 6 years from HTTP\/2 to HTTP\/3<\/strong>, there will not be enough time for HTTP\/2 to completely replace HTTP\/1.1, so <strong>the laggards will move directly to HTTP\/3<\/strong>. Among these laggards, we can include <strong>the Google spider (Googlebot), which continues to index only with HTTP\/1.1<\/strong> when it should take advantage of the speed of HTTP\/2 if the crawled web server allows it.<\/p>\n<p>The reason you should make this change is that <strong>many sites have discarded the domain sharding optimization technique, which is counterproductive with HTTP\/2 and HTTP\/3<\/strong>, but made sense under HTTP\/1.1.<\/p>\n<p>The following graph shows that HTTP\/2 usage has not yet reached 50%, with a current growth rate of approximately 10% per year:<\/p>\n<figure id=\"attachment_38528\" aria-describedby=\"caption-attachment-38528\" style=\"width: 599px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-38528 size-full\" src=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http2-uso.png\" alt=\"http2 usage graph \" width=\"599\" height=\"400\" \/><figcaption id=\"caption-attachment-38528\" class=\"wp-caption-text\">Current HTTP\/2 usage graph (source: <a href=\"https:\/\/w3techs.com\/technologies\/details\/ce-http2\" target=\"_blank\" rel=\"noopener noreferrer\">W3Techs<\/a>)<\/figcaption><\/figure>\n<h2><span id=\"What_is_QUIC\">What is QUIC?<\/span><\/h2>\n<p>QUIC stands for Quick UDP Internet Connections and Quick UDP Internet Connections protocol and <strong>is much more important than HTTP\/3 <\/strong>since <strong>breaks with the foundations of the Internet<\/strong> by reinventing the layered architecture of the TCP\/IP model, taking over the <strong>TCP transport layer protocol functions<\/strong> and the <strong>TLS security layer functions<\/strong>. This is a <strong>radical change<\/strong> because since the Internet was invented in the 70s and 80s, its only transport protocols have been TCP and UDP.<\/p>\n<p>In order to be able to <strong>QUIC implementation without having to change all the Internet network devices<\/strong>, this <strong>is based on<\/strong> the <strong>UDP<\/strong> transport protocol, as its name suggests, although <strong>this does not prevent there being problems in the regulation of QUIC traffic<\/strong> <strong>that have not yet been resolved<\/strong> and which are the main reason why the protocol is still <strong>in the experimental phase<\/strong>. So despite using UDP, many routers and firewalls will have to adapt to this new protocol.<\/p>\n<h3><span id=\"How_does_it_work\">How does it work?<\/span><\/h3>\n<p>Visually, the protocol stack would look like the following image, in which<strong> we have assigned colors to the different functions of each protocol<\/strong>. Thus, we see how <strong>QUIC assumes the following functions<\/strong>:<\/p>\n<ul>\n<li><strong>Functions of the security layer<\/strong>: guarantees that no one modifies the data, that no one sees it and the identity of the company offering the service.<\/li>\n<li><strong>TCP transport layer functions<\/strong>: error detection and correction and congestion control.<\/li>\n<li><strong>Transport functions that had been included in HTTP\/2<\/strong>: HTTP\/2 included the multiplexing and flow prioritization functions, which are transport functions. By taking over QUIC these functions are removed from HTTP\/2, giving rise to HTTP\/3.<\/li>\n<\/ul>\n<figure id=\"attachment_38561\" aria-describedby=\"caption-attachment-38561\" style=\"width: 1000px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-38561\" src=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/pila-de-protocolos-http.png\" alt=\"http\/1.1 http\/2 and http\/3 protocol stack\" width=\"1000\" height=\"458\" srcset=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/pila-de-protocolos-http.png 1000w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/pila-de-protocolos-http-720x330.png 720w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/pila-de-protocolos-http-768x352.png 768w\" sizes=\"auto, (max-width: 1000px) 100vw, 1000px\" \/><figcaption id=\"caption-attachment-38561\" class=\"wp-caption-text\">Protocol stacks http\/1.1, http\/2 and http\/3<\/figcaption><\/figure>\n<p><strong>TCP is a connection-oriented protocol<\/strong> that ensures that data arrives <strong>error-free at the destination<\/strong>. The <strong>UDP<\/strong> protocol, on the other hand, is a transport protocol used for fast communications, <strong>without establishing a connection and through which data can arrive with errors<\/strong>. The latter is used in applications such as video streaming, where it is more important to receive the image in real time than for a piece of a frame to fail. But <strong>in a website we do need reliable data<\/strong>. So <strong>QUIC performs the functions that TCP did that UDP does not<\/strong>. In addition, it <strong>does so more efficiently, achieving reliable, secure data at higher speeds<\/strong>. The function performed by UDP is simply to chunk the information into packets called datagrams.<\/p>\n<p><strong>QUIC will initially be used only with the HTTP\/3 application protocol<\/strong>, but it is likely that other application protocols will rely on QUIC in the future.<\/p>\n<p>Since <strong>in practice HTTP\/2 is forced to work over TLS<\/strong>, it cannot be used if the website does not have HTTPS. The same is true for <strong>HTTP\/3<\/strong> which, being forced to run on top of QUIC, <strong>cannot be used on a website that does not have HTTPS<\/strong>.<\/p>\n<p>With HTTP\/3 and QUIC <strong>speed improvement will not be as noticeable as from HTTP\/1.1 to HTTP\/2 <\/strong>but <strong>will be an improvement especially in situations where transmission errors occur. <\/strong>This is very important considering that cell phones are the preferred means of navigation for users and that coverage conditions are not always the best. But let&#8217;s take a closer look at the features.<\/p>\n<h3><span id=\"QUIC_protocol_characteristics\">QUIC protocol characteristics:<\/span><\/h3>\n<ul>\n<li><strong>Multiplexing and improved error handling HTTP\/2<\/strong>: like HTTP\/2, it allowed all web files to be sent multiplexed in a single TCP connection, <strong>HTTP\/3 allows sending several multiplexed files over QUIC, with one connection per file.<\/strong> <strong>With HTTP\/2, an error in one packet caused all other packets to be discarded until the server retransmitted the packet with the error. <\/strong>On the other hand, <strong>with HTTP\/3 and QUIC, packets can still be received, even if some have arrived with errors<\/strong>. This defect, which could make HTTP\/2 slower than HTTP\/1.1 with a high error rate, does not occur with HTTP\/3.<\/li>\n<li><strong>QUIC avoids slow TCP startup and controls network congestion better<\/strong>: the <strong>TCP<\/strong> protocol uses a sliding window algorithm to control the amount of data sent and not saturate the network. This algorithm initially increases the amount of data sent little by little, so that <strong>the first bytes are downloaded more slowly<\/strong>. QUIC uses a smarter algorithm that lacks this slow start.<\/li>\n<li>QUIC uses the HTTP\/2 priority mechanism, allowing to have several flows with different priorities.<\/li>\n<li><strong>Fewer round-trip cycles and higher network utilization. <\/strong>The server, unlike TCP, is not able to <b>does not need to wait for packet receipt confirmations from the client for the server to send the next packets.<\/b> At the time of <strong>establish an encrypted connection, requires only one round-trip cycle<\/strong>, unlike TCP + TLS which may require up to 3. In addition, <strong>to establish multiple connections, once the first one has been established, QUIC only needs one one-way trip to do so<\/strong>. As the packets have to make fewer trips, <strong>the latency time will be less affected, <\/strong>so <strong>the margin for improvement when using a <a href=\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/css-optimization\" target=\"_blank\" rel=\"noopener noreferrer\">CDN will be smaller<\/a><\/strong>.<\/li>\n<li><strong>QUIC requires less use of CPhttps:\/\/www.humanlevel.com\/blog\/seo\/cdn-cuando-y-como-utilizar-unoU,<\/strong> which translates into small battery savings on cell phones.<\/li>\n<li><strong>QUIC enables connection migration:<\/strong> this allows connections to be reused when you disconnect from one network and connect to another. For example, when you switch from 4G to WiFi or from one WiFi to another.<\/li>\n<\/ul>\n\n<h2><span id=\"Brief_history_of_QUIC\">Brief history of QUIC<\/span><\/h2>\n<p><strong>QUIC started being developed by Jim Roskind at Google in 2012.<\/strong> Initially it used a proprietary encryption solution and was intended to work only with a different version of HTTP\/2 than the official one. However, when the work was presented as a draft in 2015 to the IETF (the Internet Engineering Task Force defines Internet standards) and started to be developed by a working group within it, its cipher was changed to the one used by TLS 1.3 and theoretically now supports any application protocol. Therefore, <strong>the original version is now called gQUIC<\/strong>.<\/p>\n<p>During the development of QUIC, the specification has been called <strong>HTTP\/2 over QUIC <\/strong>when in fact it was not really HTTP\/2, but a different version of the protocol which, apart from delegating multiplexing to QUIC, redefines its syntaxes, so that finally <strong>it was decided to rename the specification to HTTP\/3<\/strong>. The term is sometimes used to refer to both the new HTTP protocol and QUIC.<\/p>\n<h2><span id=\"Current_HTTP3_usage\">Current HTTP\/3 usage<\/span><\/h2>\n<p>Regarding <strong>web services:<\/strong> Google implements it in YouTube, Gmail and the search engine. In Facebook it is implemented only in some parts.<\/p>\n<p>As for <strong>hosting services<\/strong>: the pioneers in offering HTTP\/3 are <a href=\"https:\/\/cloudflare-quic.com\" target=\"_blank\" rel=\"noopener noreferrer\">CloudFlare&#8217;s CDN (in beta testing phase)<\/a> and <a href=\"https:\/\/www.siteground.es\/blog\/quic\/\" target=\"_blank\" rel=\"noopener noreferrer\">SiteGround&#8217;<\/a>s hosting.<\/p>\n<p>In <strong>browsers<\/strong>, it is currently supported by <strong>Chromium, Firefox, Opera and Chrome<\/strong> but, being an experimental protocol, it is <strong>not enabled by default in some of them<\/strong>.<\/p>\n<p><strong>For HTTP\/3 to work, both the client and server must support it and have a compatible implementation of the protocol:<\/strong> remember that this is experimental and the specification is in a draft state that may change, so it would not be uncommon for some client-server implementations not to be compatible with each other.<\/p>\n<h2><span id=\"How_do_I_know_if_a_website_uses_HTTP3\">How do I know if a website uses HTTP\/3?<\/span><\/h2>\n<p>To check whether a website uses HTTP\/3, you can use one of these <strong>online tools<\/strong>: <a href=\"https:\/\/domsignal.com\/http3-test\" target=\"_blank\" rel=\"noopener noreferrer\">HTTP\/3 Test<\/a> or <a href=\"https:\/\/www.http3check.net\" target=\"_blank\" rel=\"noopener noreferrer\">HTTP\/3 Check<\/a>.<\/p>\n<figure id=\"attachment_38575\" aria-describedby=\"caption-attachment-38575\" style=\"width: 883px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-38575\" src=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-test.png\" alt=\"HTTP\/3 Usage Check\" width=\"883\" height=\"519\" srcset=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-test.png 883w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-test-720x423.png 720w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-test-768x451.png 768w\" sizes=\"auto, (max-width: 883px) 100vw, 883px\" \/><figcaption id=\"caption-attachment-38575\" class=\"wp-caption-text\">HTTP\/3 Usage Check<\/figcaption><\/figure>\n<p><strong>It can also be checked from browsers that already support it<\/strong>.<\/p>\n<p>HTTP\/3 is enabled in Chrome from chrome:\/\/flags\/#enable-quic, in Opera from opera:\/\/flags\/#enable-quic and in Firefox by typing in the about:config bar, and then enabling the network.http.http3.enabled property. Then we restart the browser and we can see in the network window the HTTP\/3 protocol if the client and the server are using the same version of the protocol. In the following Firefox screenshot you can see an example:<\/p>\n<figure id=\"attachment_38578\" aria-describedby=\"caption-attachment-38578\" style=\"width: 803px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-38578\" src=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/firefox-http3.png\" alt=\"HTTP\/3 in Firefox\" width=\"803\" height=\"54\" srcset=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/firefox-http3.png 803w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/firefox-http3-720x48.png 720w, https:\/\/www.humanlevel.com\/wp-content\/uploads\/firefox-http3-768x52.png 768w\" sizes=\"auto, (max-width: 803px) 100vw, 803px\" \/><figcaption id=\"caption-attachment-38578\" class=\"wp-caption-text\">HTTP\/3 in Firefox<\/figcaption><\/figure>\n<h2><span id=\"Conclusion\">Conclusion<\/span><\/h2>\n<p><strong>HTTP\/3 and QUIC will reduce the time we spend waiting for web pages to load<\/strong> and, when it is finally standardized, <strong>it will be a priority to have it to give users a good performance against the competition<\/strong>. But, for the time being, we will have to wait for the problems to be solved for its implementation and for browsers and web services to implement the definitive version.<\/p>\n<h2><span id=\"Bibliography\">Bibliography<\/span><\/h2>\n<ul>\n<li><a href=\"https:\/\/quicwg.org\" target=\"_blank\" rel=\"noopener noreferrer\">Official IETF page for the QUIC working group, with all drafts of the standard.<\/a><\/li>\n<li><a href=\"https:\/\/blog.cloudflare.com\/http-3-from-root-to-tip\/\" target=\"_blank\" rel=\"noopener noreferrer\">Explanation of the operation of HTTP\/3 and QUIC by CloudFlare<\/a><\/li>\n<li><a href=\"https:\/\/cloud.google.com\/load-balancing\/docs\/https?hl=es#QUIC\" target=\"_blank\" rel=\"noopener noreferrer\">Google documentation on how to perform load balancing over QUIC<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.<\/p>\n","protected":false},"author":14,"featured_media":48297,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[349],"tags":[366],"class_list":["post-51990","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo","tag-technical-seo","entry"],"yoast_head":"\n<title>HTTP\/3 and QUIC, what do they mean for the web? | Human Level<\/title>\n<meta name=\"description\" content=\"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"HTTP\/3 and QUIC, what do they mean for the web? | Human Level\" \/>\n<meta property=\"og:description\" content=\"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\" \/>\n<meta property=\"og:site_name\" content=\"Human Level\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-20T12:16:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"400\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ram\u00f3n Saquete\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Daiatron\" \/>\n<meta name=\"twitter:site\" content=\"@humanlevel\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ram\u00f3n Saquete\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\"},\"author\":{\"name\":\"Ram\u00f3n Saquete\",\"@id\":\"https:\/\/www.humanlevel.com\/en#\/schema\/person\/11ad888926867985985a0210476bae94\"},\"headline\":\"HTTP\/3 and QUIC, what do they mean for the web?\",\"datePublished\":\"2020-02-20T12:16:41+00:00\",\"dateModified\":\"2023-11-27T17:28:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\"},\"wordCount\":1655,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.humanlevel.com\/en#organization\"},\"image\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg\",\"keywords\":[\"Technical SEO\"],\"articleSection\":[\"SEO\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\",\"url\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\",\"name\":\"HTTP\/3 and QUIC, what do they mean for the web? | Human Level\",\"isPartOf\":{\"@id\":\"https:\/\/www.humanlevel.com\/en#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg\",\"datePublished\":\"2020-02-20T12:16:41+00:00\",\"dateModified\":\"2023-11-27T17:28:47+00:00\",\"description\":\"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage\",\"url\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg\",\"contentUrl\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg\",\"width\":400,\"height\":400},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Portada\",\"item\":\"https:\/\/www.humanlevel.com\/en\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"HTTP\/3 and QUIC, what do they mean for the web?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.humanlevel.com\/en#website\",\"url\":\"https:\/\/www.humanlevel.com\/en\",\"name\":\"Human Level\",\"description\":\"Web positioning and online marketing consultant Human Level\",\"publisher\":{\"@id\":\"https:\/\/www.humanlevel.com\/en#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.humanlevel.com\/en?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.humanlevel.com\/en#organization\",\"name\":\"Human Level\",\"url\":\"https:\/\/www.humanlevel.com\/en\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.humanlevel.com\/en#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/logo-human-negro-1.jpg\",\"contentUrl\":\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/logo-human-negro-1.jpg\",\"width\":268,\"height\":51,\"caption\":\"Human Level\"},\"image\":{\"@id\":\"https:\/\/www.humanlevel.com\/en#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/humanlevel\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.humanlevel.com\/en#\/schema\/person\/11ad888926867985985a0210476bae94\",\"name\":\"Ram\u00f3n Saquete\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.humanlevel.com\/en#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/7a50f1a1974393853ee4f2423c9009f813cb107d3e7e20cf17cf8e86d407132e?s=96&d=simple_local_avatar&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/7a50f1a1974393853ee4f2423c9009f813cb107d3e7e20cf17cf8e86d407132e?s=96&d=simple_local_avatar&r=g\",\"caption\":\"Ram\u00f3n Saquete\"},\"description\":\"Desarrollador web y consultor SEO t\u00e9cnico en Human Level. Graduado en Ingenier\u00eda Inform\u00e1tica e Ingenier\u00eda T\u00e9cnica en Inform\u00e1tica de Sistemas. Tambi\u00e9n es T\u00e9cnico Superior en Desarrollo de Aplicaciones Inform\u00e1ticas y posteriormente obtuvo la Certificaci\u00f3n de Aptitud Pedag\u00f3gica. Experto en WPO e indexabilidad.\",\"sameAs\":[\"https:\/\/x.com\/Daiatron\"],\"url\":\"https:\/\/www.humanlevel.com\/en\/author\/ramon\"}]}<\/script>\n","yoast_head_json":{"title":"HTTP\/3 and QUIC, what do they mean for the web? | Human Level","description":"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic","og_locale":"en_US","og_type":"article","og_title":"HTTP\/3 and QUIC, what do they mean for the web? | Human Level","og_description":"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.","og_url":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic","og_site_name":"Human Level","article_published_time":"2020-02-20T12:16:41+00:00","og_image":[{"width":400,"height":400,"url":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg","type":"image\/jpeg"}],"author":"Ram\u00f3n Saquete","twitter_card":"summary_large_image","twitter_creator":"@Daiatron","twitter_site":"@humanlevel","twitter_misc":{"Written by":"Ram\u00f3n Saquete","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#article","isPartOf":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic"},"author":{"name":"Ram\u00f3n Saquete","@id":"https:\/\/www.humanlevel.com\/en#\/schema\/person\/11ad888926867985985a0210476bae94"},"headline":"HTTP\/3 and QUIC, what do they mean for the web?","datePublished":"2020-02-20T12:16:41+00:00","dateModified":"2023-11-27T17:28:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic"},"wordCount":1655,"commentCount":0,"publisher":{"@id":"https:\/\/www.humanlevel.com\/en#organization"},"image":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage"},"thumbnailUrl":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg","keywords":["Technical SEO"],"articleSection":["SEO"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic","url":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic","name":"HTTP\/3 and QUIC, what do they mean for the web? | Human Level","isPartOf":{"@id":"https:\/\/www.humanlevel.com\/en#website"},"primaryImageOfPage":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage"},"image":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage"},"thumbnailUrl":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg","datePublished":"2020-02-20T12:16:41+00:00","dateModified":"2023-11-27T17:28:47+00:00","description":"Find out what HTTP\/3 and QUIC are, how they will improve web performance, how to tell if your website uses them and how QUIC can make the Internet faster.","breadcrumb":{"@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#primaryimage","url":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg","contentUrl":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/http3-quic.jpg","width":400,"height":400},{"@type":"BreadcrumbList","@id":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/http3-and-quic#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Portada","item":"https:\/\/www.humanlevel.com\/en"},{"@type":"ListItem","position":2,"name":"HTTP\/3 and QUIC, what do they mean for the web?"}]},{"@type":"WebSite","@id":"https:\/\/www.humanlevel.com\/en#website","url":"https:\/\/www.humanlevel.com\/en","name":"Human Level","description":"Web positioning and online marketing consultant Human Level","publisher":{"@id":"https:\/\/www.humanlevel.com\/en#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.humanlevel.com\/en?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.humanlevel.com\/en#organization","name":"Human Level","url":"https:\/\/www.humanlevel.com\/en","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.humanlevel.com\/en#\/schema\/logo\/image\/","url":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/logo-human-negro-1.jpg","contentUrl":"https:\/\/www.humanlevel.com\/wp-content\/uploads\/logo-human-negro-1.jpg","width":268,"height":51,"caption":"Human Level"},"image":{"@id":"https:\/\/www.humanlevel.com\/en#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/humanlevel"]},{"@type":"Person","@id":"https:\/\/www.humanlevel.com\/en#\/schema\/person\/11ad888926867985985a0210476bae94","name":"Ram\u00f3n Saquete","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.humanlevel.com\/en#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/7a50f1a1974393853ee4f2423c9009f813cb107d3e7e20cf17cf8e86d407132e?s=96&d=simple_local_avatar&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7a50f1a1974393853ee4f2423c9009f813cb107d3e7e20cf17cf8e86d407132e?s=96&d=simple_local_avatar&r=g","caption":"Ram\u00f3n Saquete"},"description":"Desarrollador web y consultor SEO t\u00e9cnico en Human Level. Graduado en Ingenier\u00eda Inform\u00e1tica e Ingenier\u00eda T\u00e9cnica en Inform\u00e1tica de Sistemas. Tambi\u00e9n es T\u00e9cnico Superior en Desarrollo de Aplicaciones Inform\u00e1ticas y posteriormente obtuvo la Certificaci\u00f3n de Aptitud Pedag\u00f3gica. Experto en WPO e indexabilidad.","sameAs":["https:\/\/x.com\/Daiatron"],"url":"https:\/\/www.humanlevel.com\/en\/author\/ramon"}]}},"_links":{"self":[{"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/posts\/51990","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/comments?post=51990"}],"version-history":[{"count":4,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/posts\/51990\/revisions"}],"predecessor-version":[{"id":56569,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/posts\/51990\/revisions\/56569"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/media\/48297"}],"wp:attachment":[{"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/media?parent=51990"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/categories?post=51990"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.humanlevel.com\/en\/wp-json\/wp\/v2\/tags?post=51990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}