From 7015c954088b525b95a2ee0179c94ea56d92e67c Mon Sep 17 00:00:00 2001 From: Boris Schapira Date: Thu, 30 Jan 2020 01:11:40 +0100 Subject: [PATCH] Missing end of code snippet (#651) --- src/content/en/2019/resource-hints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/en/2019/resource-hints.md b/src/content/en/2019/resource-hints.md index 8f176bcdd48..e848d4b3dc1 100644 --- a/src/content/en/2019/resource-hints.md +++ b/src/content/en/2019/resource-hints.md @@ -247,4 +247,4 @@ Native lazy loading is available in browsers based on Chromium 76 and up. The AP ## Conclusion -Overall, this data seems to suggest that there is still room for further adoption of resource hints. Most sites would benefit from adopting and/or switching to `preconnect` from `dns-prefetch`. A much smaller subset of sites would benefit from adopting `prefetch` and/or `preload`. There is greater nuance in successfully using `prefetch` and `preload`, which constrains its adoption to a certain extent, but the potential payoff is also greater. HTTP/2 Push and the maturation of machine learning technologies is also likely to increase the adoption of `preload` and `prefetch. +Overall, this data seems to suggest that there is still room for further adoption of resource hints. Most sites would benefit from adopting and/or switching to `preconnect` from `dns-prefetch`. A much smaller subset of sites would benefit from adopting `prefetch` and/or `preload`. There is greater nuance in successfully using `prefetch` and `preload`, which constrains its adoption to a certain extent, but the potential payoff is also greater. HTTP/2 Push and the maturation of machine learning technologies is also likely to increase the adoption of `preload` and `prefetch`.