Page 1 of 1
Multistore - first byte problem
Posted: Mon Sep 01, 2014 4:41 pm
by madfish
Hello,
I have a multi-store opencart, but i have problems accessing the non-default stores.
the default store is :
http://profumino.it
and the secondary store is
http://profumino.hr
The default store opens quickly, but the other is lagging.
What should I look for ?
Re: Multistore - first byte problem
Posted: Tue Sep 02, 2014 3:44 pm
by madfish
Anyone ?
Re: Multistore - first byte problem
Posted: Tue Sep 02, 2014 5:56 pm
by k2tec
here they are identical fast. But you have some DNS problems with .hr (look in dnsstuff.com)
Re: Multistore - first byte problem
Posted: Tue Sep 02, 2014 10:58 pm
by madfish
Yes, I see but all are mail problems..
The thing is, when the page is loaded it works fast. I don't know why the primary .it loads (first load) faster than the .hr.
Re: Multistore - first byte problem
Posted: Thu Sep 18, 2014 11:59 pm
by madfish
Is here anyone able to help ?
I will pay for the service.
Re: Multistore - first byte problem
Posted: Fri Sep 19, 2014 2:03 am
by Dhaupin
It doesn't get slow for every refresh, but when it does, Chrome was saying the first byte was being "blocked". So it sounds like its something server/domain related? There is 1 extra DNS server your site uses that isnt available for ping...maybe its internal and slowwwww
The 'Blocked' time is the delta between the 'requestTime' and the 'startTime'. Basically, this is a measure of the amount of time between the UI thread initiating the request for the network resource and the HTTP GET for the request bits getting onto the wire. In between, there can be internal queuing/message passing delay, cache lookup, dns resolution, and TCP connection setup.
This value isn't really all that interesting on its own, but if you're just trying to pin down network effects for a particular resource, then you can subtract this value from the RequestTiming duration (which measures from base 'startTime') since it's not really a variable you can control by making your server closer/faster or making the payload smaller. It would be a lot easier to see this sort of thing if we displayed this information visually rather than (or in addition to) a table.
From
https://groups.google.com/forum/?fromgr ... lF_gTvMRD8
Also there is this
http://stackoverflow.com/questions/1053 ... work-panel