Skip to content

Commit

Permalink
Missing end of code snippet (#651)
Browse files Browse the repository at this point in the history
  • Loading branch information
borisschapira authored Jan 30, 2020
1 parent 1d62816 commit 7015c95
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/content/en/2019/resource-hints.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

0 comments on commit 7015c95

Please sign in to comment.