Current time: 11-19-2019, 09:42 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What's causing 1762ms "First Byte Time" & is it something I can fix?
05-30-2015, 02:58 AM (This post was last modified: 05-30-2015 02:59 AM by JamesAtPulsate.)
Post: #13
RE: What's causing 1762ms "First Byte Time" & is it something I can fix?
(05-30-2015 01:33 AM)ThePrez Wrote:  
(05-24-2015 07:08 AM)WebsiteSpeedExperts Wrote:  [*]Ensure that the google resources aren't fetched from the HTTPS url - it's only adding an extra HTTPS handshake for no gain

Ah. Yes if you're not using https for the site, then there's no point in pulling some objects over https if you don't need to. Depending on what is calling them it may or may not be easy to do this. But if you can get to where those url's are triggered, id reccomend you change the urls and NOT specify a protocol. By doing this they will pull down in either http or https depending on how the page is called down.

Lets go on the assumption that NON SSL + SPDY is not benefiting performance and you want to get rid of the other SSl handshakes.
Example URL in your site's code would display say https://targetURL
Conventional wisdom would say change this to http://targetURL
What you SHOULD do is set it as simply //targetURL. No http or https

This gives you the maximum flexibility to swap back an forth between delivering over http and https without having to get back into the code each time.

Same to you.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: What's causing 1762ms "First Byte Time" & is it something I can fix? - JamesAtPulsate - 05-30-2015 02:58 AM

Forum Jump:


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