1107036 - 6 seconds to complete request on a specific webpage when in Chrome is instant

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[rimiperi]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141125180439

Steps to reproduce:

This specific page (http://bc.vc) is taking 6 seconds to load the request when in Chrome it's instant

It's an high traffic site, making an annoying wait to many people
http://www.alexa.com/siteinfo/bc.vc

I already talked to the admin but he's still trying to figure out whats the issue

I've tested the site with some firefox plugins

Page speed apptelemetry
http://i.imgur.com/BwGhv1Q.png

Firebug
http://i.imgur.com/KGysArh.png

Firebug on http://support.bc.vc
http://i.imgur.com/6USp9nf.png

Yslow plugin
http://i.imgur.com/oIoyLqo.png
http://i.imgur.com/5M1S5oo.png
http://i.imgur.com/XC2xGzV.png


Actual results:

(info above)


Expected results:

(info above)

Comment 1

[rimiperi]

The admin said that made a database optimization 4 days ago, when this issue started

Is it possible to troubleshoot?

Comment 2

[Matthias Versen [:Matti]]

I get a ~6s delay with Firefox34 and also IE11

Is that stupid page from a google fan or payed by google ?
Change your useragent in Firefox to the google chrome one and it loads in under 1s....
(about:config , right click, new string, name "general.useragent.override" without the "", value "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2227.1 Safari/537.36" )

Comment 3

[rimiperi]

This site has nothing to do with Google, the admin himself is trying to solve this issue

Can you figure out whats the real cause of this issue?

Comment 4

[Matthias Versen [:Matti]]

(In reply to rimiperi from comment #3)

> Can you figure out whats the real cause of this issue?
The issue appears if the user agent string is Firefox or IE but it works with the chrome/safari UA. 
the server answers the initial connection only after 6s with a Firefox UA and that means that there is some kind of user agent sniffing on the server side involved and that this is not a browser issue.

I can not know the real issue because it's an issue on the server setup.