Slow Server Load time
My site is getting a slow load time of around 1.7s to 2.2s when I ping it. What should I do to speed it up?
My site is getting a slow load time of around 1.7s to 2.2s when I ping it. What should I do to speed it up?
oh crap thank you. Was just in a rush and forgot, much appreciated. I'll read over
I've contacted the advanced tech support we qualify for like 7 times and they keep saying everything looks fine. So I thought I'd try the board
It may be a good idea to check with the Managed Hosting team as well. If this is more a matter of optimization than any single thing being wrong, they could take a look and give you an estimate of the type of work that would be needed to improve things if it was something they were able to work on.
Firstly, thank you very much for responding.
Sorry, I should have posted that info. It is a dedicated server, and it started right after holiday break and nothing was changed by us since well before that. Perhaps some small file changes but nothing on server settings.
We may have more users but I doubt these numbers would be an issue:
01 Jan 2020 | 2,458 | 11,484 | 11,712 | 11.51 GB |
02 Jan 2020 | 3,193 | 16,913 | 17,484 | 32.06 GB |
03 Jan 2020 | 2,726 | 16,592 | 17,276 | 64.97 GB |
04 Jan 2020 | 2,893 | 13,463 | 13,750 | 37.78 GB |
05 Jan 2020 | 3,777 | 14,585 | 14,939 | 66.91 GB |
06 Jan 2020 | 3,088 | 36,098 | 37,703 | 141.99 GB |
07 Jan 2020 | 2,786 | 38,042 | 39,552 | 180.58 GB |
08 Jan 2020 | 2,730 | 34,518 | 35,868 | 232.03 GB |
09 Jan 2020 | 2,807 | 27,995 | 29,223 | 192.68 GB |
10 Jan 2020 | 213 | 3,107 | 3,176 | 14.59 GB |
Ping/Tracer test:
C:\Users\Matts>ping -----
Pinging --- [---] with 32 bytes of data:
Reply from ---: bytes=32 time=77ms TTL=53
Reply from ---: bytes=32 time=79ms TTL=53
Reply from ---: bytes=32 time=82ms TTL=53
Reply from ---: bytes=32 time=84ms TTL=53
Ping statistics for ---:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 84ms, Average = 80ms
C:\Users\--->tracert ---
Tracing route to --- [---]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms mynetwork [192.168.2.1]
2 25 ms 16 ms 22 ms 10.11.3.145
3 * * * Request timed out.
4 28 ms 23 ms 31 ms tcore4-toronto12_be36.net.bell.ca [64.230.52.210
]
5 28 ms 23 ms 23 ms tcore4-chicagocp_hundredgige0-4-0-0.net.bell.ca
[64.230.79.157]
6 17 ms 19 ms 19 ms bx9-chicagodt_ae1-0.net.bell.ca [64.230.79.75]
7 23 ms 19 ms 18 ms lag-101.ear7.Chicago2.Level3.net [4.15.248.93]
8 * * * Request timed out.
9 76 ms 79 ms 78 ms cr1.lax1.us.packetexchange.net [4.71.136.2]
10 82 ms 95 ms 90 ms csw3.lax1.inmotionhosting.com [198.46.92.2]
11 82 ms 78 ms 78 ms csw4.lax1.inmotionhosting.com [198.46.92.3]
12 83 ms 78 ms 77 ms csw1.lax1.inmotionhosting.com [198.46.92.26]
13 84 ms 78 ms 82 ms ded3177.inmotionhosting.com [74.124.213.13]
Trace complete.
It is essentially a landing page that pretty much just sends users to our main website - and then is used for file storage and our license management system. We wanted to have a server just for that to limit possible traffic issues. I did not see a System Health icon, but the cpanel in the link provided for that looks different than ours.
Thanks for further clarification! I removed personally identifying information from your post for your privacy.
The nature of Dedicated servers, and the custom configurations they have, mean that it's really best that you contact our Advanced Product Support team directly. They'll be able to directly connect to your server and get a clear idea of what is going on.
Having a Dedicated server means all of your support contacts automatically qualify for the APS team. Provide them with the information you provided me and they will be able to check for any issues likely causing the problem.
Firstly, thank you very much for responding.
Sorry, I should have posted that info. It is a dedicated server, and it started right after holiday break and nothing was changed by us since well before that. Perhaps some small file changes but nothing on server settings.
We may have more users but I doubt these numbers would be an issue:
01 Jan 2020 | 2,458 | 11,484 | 11,712 | 11.51 GB |
02 Jan 2020 | 3,193 | 16,913 | 17,484 | 32.06 GB |
03 Jan 2020 | 2,726 | 16,592 | 17,276 | 64.97 GB |
04 Jan 2020 | 2,893 | 13,463 | 13,750 | 37.78 GB |
05 Jan 2020 | 3,777 | 14,585 | 14,939 | 66.91 GB |
06 Jan 2020 | 3,088 | 36,098 | 37,703 | 141.99 GB |
07 Jan 2020 | 2,786 | 38,042 | 39,552 | 180.58 GB |
08 Jan 2020 | 2,730 | 34,518 | 35,868 | 232.03 GB |
09 Jan 2020 | 2,807 | 27,995 | 29,223 | 192.68 GB |
10 Jan 2020 | 213 | 3,107 | 3,176 | 14.59 GB |
Ping/Tracer test:
C:\Users\Matts>ping 1q4all.com
Pinging 1q4all.com [74.124.213.13] with 32 bytes of data:
Reply from 74.124.213.13: bytes=32 time=77ms TTL=53
Reply from 74.124.213.13: bytes=32 time=79ms TTL=53
Reply from 74.124.213.13: bytes=32 time=82ms TTL=53
Reply from 74.124.213.13: bytes=32 time=84ms TTL=53
Ping statistics for 74.124.213.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 84ms, Average = 80ms
C:\Users\Matts>tracert 1q4all.com
Tracing route to 1q4all.com [74.124.213.13]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms mynetwork [192.168.2.1]
2 25 ms 16 ms 22 ms 10.11.3.145
3 * * * Request timed out.
4 28 ms 23 ms 31 ms tcore4-toronto12_be36.net.bell.ca [64.230.52.210
]
5 28 ms 23 ms 23 ms tcore4-chicagocp_hundredgige0-4-0-0.net.bell.ca
[64.230.79.157]
6 17 ms 19 ms 19 ms bx9-chicagodt_ae1-0.net.bell.ca [64.230.79.75]
7 23 ms 19 ms 18 ms lag-101.ear7.Chicago2.Level3.net [4.15.248.93]
8 * * * Request timed out.
9 76 ms 79 ms 78 ms cr1.lax1.us.packetexchange.net [4.71.136.2]
10 82 ms 95 ms 90 ms csw3.lax1.inmotionhosting.com [198.46.92.2]
11 82 ms 78 ms 78 ms csw4.lax1.inmotionhosting.com [198.46.92.3]
12 83 ms 78 ms 77 ms csw1.lax1.inmotionhosting.com [198.46.92.26]
13 84 ms 78 ms 82 ms ded3177.inmotionhosting.com [74.124.213.13]
Trace complete.
It is essentially a landing page that pretty much just sends users to our main website - and then is used for file storage and our license management system. We wanted to have a server just for that to limit possible traffic issues. I did not see a System Health icon, but the cpanel in the link provided for that looks different than ours.
Firstly, thank you very much for responding.
Sorry, I should have posted that info. It is a dedicated server, and it started right after holiday break and nothing was changed by us since well before that. Perhaps some small file changes but nothing on server settings.
We may have more users but I doubt these numbers would be an issue:
01 Jan 2020 | 2,458 | 11,484 | 11,712 | 11.51 GB |
02 Jan 2020 | 3,193 | 16,913 | 17,484 | 32.06 GB |
03 Jan 2020 | 2,726 | 16,592 | 17,276 | 64.97 GB |
04 Jan 2020 | 2,893 | 13,463 | 13,750 | 37.78 GB |
05 Jan 2020 | 3,777 | 14,585 | 14,939 | 66.91 GB |
06 Jan 2020 | 3,088 | 36,098 | 37,703 | 141.99 GB |
07 Jan 2020 | 2,786 | 38,042 | 39,552 | 180.58 GB |
08 Jan 2020 | 2,730 | 34,518 | 35,868 | 232.03 GB |
09 Jan 2020 | 2,807 | 27,995 | 29,223 | 192.68 GB |
10 Jan 2020 | 213 | 3,107 | 3,176 | 14.59 GB |
Ping/Tracer test:
C:\Users\Matts>ping -----
Pinging --- [---] with 32 bytes of data:
Reply from ---: bytes=32 time=77ms TTL=53
Reply from ---: bytes=32 time=79ms TTL=53
Reply from ---: bytes=32 time=82ms TTL=53
Reply from ---: bytes=32 time=84ms TTL=53
Ping statistics for ---:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 84ms, Average = 80ms
C:\Users\--->tracert ---
Tracing route to --- [---]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms mynetwork [192.168.2.1]
2 25 ms 16 ms 22 ms 10.11.3.145
3 * * * Request timed out.
4 28 ms 23 ms 31 ms tcore4-toronto12_be36.net.bell.ca [64.230.52.210
]
5 28 ms 23 ms 23 ms tcore4-chicagocp_hundredgige0-4-0-0.net.bell.ca
[64.230.79.157]
6 17 ms 19 ms 19 ms bx9-chicagodt_ae1-0.net.bell.ca [64.230.79.75]
7 23 ms 19 ms 18 ms lag-101.ear7.Chicago2.Level3.net [4.15.248.93]
8 * * * Request timed out.
9 76 ms 79 ms 78 ms cr1.lax1.us.packetexchange.net [4.71.136.2]
10 82 ms 95 ms 90 ms csw3.lax1.inmotionhosting.com [198.46.92.2]
11 82 ms 78 ms 78 ms csw4.lax1.inmotionhosting.com [198.46.92.3]
12 83 ms 78 ms 77 ms csw1.lax1.inmotionhosting.com [198.46.92.26]
13 84 ms 78 ms 82 ms ded3177.inmotionhosting.com [74.124.213.13]
Trace complete.
It is essentially a landing page that pretty much just sends users to our main website - and then is used for file storage and our license management system. We wanted to have a server just for that to limit possible traffic issues. I did not see a System Health icon, but the cpanel in the link provided for that looks different than ours.
It's tough to guess when you're running what sounds like a VPS or Dedicated server. There are so many custom configurations that go into that, it can be hard to narrow down the exact issue.
Do you have significantly more users/visitors in recent weeks compared to the last six years? It could be that you're just hitting the limits of your bandwidth for the first time and will need to either optimize or upgrade to add more.
If that does not sound likely based on your current user statistics, I would check your currently running processes. Something may be behaving unexpectedly. Lastly, try running some traceroute tests. It may not be your site itself, but a node somewhere between the site and your connections.
oh crap thank you. Was just in a rush and forgot, much appreciated. I'll read over
I've contacted the advanced tech support we qualify for like 7 times and they keep saying everything looks fine. So I thought I'd try the board
It may be a good idea to check with the Managed Hosting team as well. If this is more a matter of optimization than any single thing being wrong, they could take a look and give you an estimate of the type of work that would be needed to improve things if it was something they were able to work on.