It is typically advised to use preconnect optimization hint "wisely", because it can result in unnecessary CPU/network load when expected requests are not made.
It is not at all clear to me, however, if this hint should be used for cacheable resources. Does this hint incur performance costs on a page where all the resources have been previously loaded and cached on the client side?
Should I take caching into account at all when using this hint or should I optimize for the first load?
Aucun commentaire:
Enregistrer un commentaire