: What is the cause of page speed performing extremely poorly on Chrome on Windows and Safari on Linux? I am more interested in the cause of poor page loading speed on Chrome/Windows, since this

@Si4351233

Briefly as you mention your .htaccess file if you have access to the vHost file it is better to shift these declarations into the vHost file as Apache needs to check the .htaccess file for every request whereas in the vHost file the commands are loaded to memory on startup the same as the rest of the vHost settings. Having said that unless you have a .htaccess conditional statement that only affects Safari and Chrome browsers the .htaccess file can't be the issue as it would affect all browsers the same way and impart around the same amount of delay in the time to first byte.

You need to be careful about how you use Google's metrics in Google Analytics as Google uses sampling, and in any sampling situation because of the "random" data selections high outliers in the data (data that is greatly different to the rest of the data) can throw the figures way out. As an example even if only a few users with those browsers had issues (such as badly configured browser extensions) that can throw the data wildly out of wack, and that significant a variation (especially given most browser configurations will timeout the connection well before the 80+ second mark you cite tends to reinforce that to me. If you are concerned you can run performance tests yourself by doing a series of rapid page loads using the offending browsers to see if the delay is really that high or if it may have been unique to very few users. The trick here is that due to the high market saturation (browser-wise) of Safari and Chrome there is a much higher chance of data outliers.

Vote Up Vote Down