Current time: 04-26-2018, 11:12 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Preconnect all the things!.. sure?
04-05-2018, 01:46 AM (This post was last modified: 04-05-2018 01:55 AM by dario.)
Post: #1
Preconnect all the things!.. sure?
Hi!

I've a dilema about the preconnect resource hint header.

The "preconnect all the things" approach means that i'm going to warm up every domain i will use in the current page load, that it's good because as far i know Chrome keeps the connection open to that wormed up domain for 60 seconds or something like that. The risk here (i think) it's to collapse the mobile connections right? to do too many things at the beginning.. and also to increase the size of the initial http request header..

The other approach is to preconnect only the domains that affects the critical rendering path, here the page total load time will be increased because the following domains are not going to be warmed up.

I did some test but i've no RUM so they are synthetic tests that can misslead the conclusions, also the results are a little weird. I left the two screenshots attached.


What do you think it's the best approach?


Thanks!


Attached File(s) Image(s)
       
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Preconnect all the things!.. sure? - dario - 04-05-2018 01:46 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)