netcarver Posted July 12, 2019 Share Posted July 12, 2019 Does anyone know why Chrome delays the favicon fetch, even when no other resource is being pulled from the source? Sometimes the delay in starting the fetch can be substantial, so I wonder if the browser is actually painting the contents and then going out for the favicon. Link to comment Share on other sites More sharing options...
wbmnfktr Posted July 12, 2019 Share Posted July 12, 2019 Is the favicon referenced in your HTML like <link rel="shortcut icon" href="/path/to/favicon.png" type="image/png"> or is it the last thing the browser does by looking in its default place? 1 Link to comment Share on other sites More sharing options...
netcarver Posted July 12, 2019 Author Share Posted July 12, 2019 @wbmnfktr I did try it both ways yesterday and it didn't seem to make a difference. I will re-add it to the page head and test again. Update: The picture posted was taken with the link in the HTML. Link to comment Share on other sites More sharing options...
Recommended Posts