amuck-landowner

NGINX Web Server issue. Time to load page

Hxxx

Active Member
Hi community,

I'm having this particular issue, i dont know if is the nginx or what but i will tell you what I've tested and maybe you guys know what i'm missing.

WinMTR tests to the website does not show significant packet loss, and the ping is a it should be, in this case from Puerto Rico to NY.

Here is the deal:

When I access the website through my local connection this being without VPN it take like 15 seconds to load. Like if the webserver put it on hold or something. Again no packet loss no unusual latency (ICMP).

If I test with a VPN the VPN being from NY or from Miami it loads extremely fast.

Pingdom test shows it loads faster than 60% of the rest of the websites tested, under 3 sec. Gtmetrix give a Page Speed Grade A, YSlow Grade C, load time 3.67, total number of request 43.

The thing is that the only website from which i have such issues is with mine. I can use my local connection to access any website and it will load in a reasonable time.

The Webserver is nginx, actually centmin mod or centminmod setup.

I though that maybe it was something within a route of the ISP I use, but i didnt noticed any loss and i'm confident that if I wipe out the vps and put the website with apache it will work as it should, so maybe im missing something for nginx. But based on the test it should be something in the route?

What is your opinion?

WinMTR test with and without VPN posted below:

---WITH VPN

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|

|          r-001-042-234-077.ff.avast.com -    8 |  103 |   95 |   41 |   51 |  100 |   56 |
|  border1.te12-3.avast-6.mia007.pnap.net -    2 |  126 |  124 |   41 |   49 |  182 |   41 |
|       core3.t6-1.bbnet1.mia003.pnap.net -    0 |  133 |  133 |   42 |   48 |   73 |   51 |
|ip67-94-116-37.z116-94-67.customer.algx.net -    3 |  121 |  118 |   41 |   46 |  348 |   43 |
|             216.156.1.253.ptr.us.xo.net -    3 |  122 |  119 |   41 |   46 |   97 |   44 |
|             206.111.1.218.ptr.us.xo.net -    0 |  133 |  133 |   41 |   47 |   78 |   44 |
|              xe-2-0-3.nyc39.ip4.gtt.net -    0 |  133 |  133 |   75 |   82 |  114 |   85 |
|                      gtt-gw.ip4.gtt.net -    0 |  133 |  133 |   74 |   81 |  116 |   77 |
|  as20473.ae7.ar1.nyc3.us.as4436.gtt.net -    0 |  133 |  133 |   76 |   86 |  111 |   85 |
|        vl351-c9-20-b2-1.pnj1.choopa.net -    0 |  133 |  133 |   77 |   86 |  279 |   85 |
|               104.207.129.172.vultr.com -    0 |  133 |  133 |   76 |   83 |  113 |   85 |
|________________________________________________|______|______|______|______|______|______|
 

----WITHOUT VPN:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|

|                              10.1.11.81 -    0 |   98 |   98 |   10 |   15 |   41 |   13 |
|                              10.65.17.5 -    0 |   98 |   98 |   11 |   16 |   43 |   18 |
|                              10.1.0.230 -    0 |   98 |   98 |   10 |   18 |   61 |   15 |
|                             10.65.200.1 -    0 |   98 |   98 |   12 |   20 |   48 |   14 |
|                              10.1.0.210 -    0 |   98 |   98 |   10 |   19 |   44 |   15 |
|                          213.140.51.249 -    0 |   98 |   98 |   12 |   19 |   45 |   16 |
|Xe4-1-3-0-grtmiabr4.priv.red.telefonica-wholesale.net -    0 |   98 |   98 |   29 |   42 |  133 |   39 |
|Xe7-1-4-0-grtdaleq2.red.telefonica-wholesale.net -    0 |   98 |   98 |   63 |   76 |  143 |   63 |
|              xe-1-1-1.nyc24.ip4.gtt.net -    0 |   98 |   98 |   64 |   72 |  102 |   68 |
|              xe-5-0-0.nyc38.ip4.gtt.net -    0 |   98 |   98 |   72 |   83 |  110 |   83 |
|            ae0-150.cr2.nyc3.ip4.gtt.net -    0 |   98 |   98 |   69 |   82 |   99 |   72 |
|  as20473.ae7.ar2.nyc3.us.as4436.gtt.net -    2 |   95 |   94 |   68 |   82 |  105 |   77 |
|        vl351-c9-20-b2-1.pnj1.choopa.net -    0 |   98 |   98 |   63 |   78 |  129 |   82 |
|        vl351-c9-20-b2-1.pnj1.choopa.net -    0 |   98 |   98 |   65 |   83 |  176 |   90 |
|                     websiteforgeeks.com -    0 |   98 |   98 |   67 |   83 |  106 |   78 |
|________________________________________________|______|______|______|______|______|______|
 
 

splitice

Just a little bit crazy...
Verified Provider
Are you using SPDY and a Windows client? There was a bug fixed in nginx that caused an extra round trip... often causing a 200ms delay. Something to do with SSL record alignment or something, I cant remember exactly (we never ran that version as a result). Also 1.7.8 fixes tcp nodelay - https://josephscott.org/archives/2014/12/nginx-1-7-8-fixes-200ms-delay-with-spdy/

Other than that look at it from a developer console and get a network / resource graph and see exactly what is delaying your load.
 
Top
amuck-landowner