Initial Server Response on a simple "Hello World" PHP file behaving erratically.

Additionally, if the website is based on a CMS or other script (i.e WordPress with a lot of or various plugins), then some thing in the script may be trying to phone home or otherwise trying to make an outbound connection some where. And for whatever reason, the server you are on is either unable to contact that server or is communicating with that remote server very slowly.

The script gets caught waiting for a response from that remote server before it will continue with execution of the script.

Hard to really diagnose this issue.
 
I wanted you to know for the current time I wont be able to help. I wanted to post this here. So others might help out.
@Richard G is a good help so maybe he can help some. I just didn't want to string you along.
 
At this stage we are looking at Prestashop as it seems that there isn't much else we can do to optimize DA. We have made changes to MySql and PHP already. Implemented opcache as well as changed some Apache settings. The TTFB is now between 1.1-1.2s

Not great but let's hope changing more Prestashop settings will improve it further, otherwise we will have to settle for this slow TTFB
 
ikkeben said:
Did you try simple other domain or subdomain with a simple very short index.html few bytes, and yes ssl on ofcourse.

So to check it is server / network / settings for those and not presta
Click to expand...
Thanks for the suggestion but I did try that as stated in the title of this thread and the original post. :-)

That's actually how I got my baseline.
 
bluesteam said:
Thanks for the suggestion but I did try that as stated in the title of this thread and the original post. :)

That's actually how I got my baseline.
Click to expand...
With webpagetest.org and different test server locations there

Should be under 0,5 seconds better under 0,3

but see this on this moment ofcourse timezone and traffice times counts also.

WebPageTest

View this on WebPageTest.org...
www.webpagetest.org www.webpagetest.org

IS:
From: Cape Town, South Africa - EC2 - Chrome - Cable
15.7.2021, 10:06:09


Take care there. ;)
 
ikkeben said:
With webpagetest.org and different test server locations there

Should be under 0,5 seconds better under 0,3

but see this on this moment ofcourse timezone and traffice times counts also.

WebPageTest

View this on WebPageTest.org...
www.webpagetest.org www.webpagetest.org

IS:
From: Cape Town, South Africa - EC2 - Chrome - Cable
15.7.2021, 10:06:09


Take care there. ;)
Click to expand...
This is very helpful thank you but the problem is that Google will use their own test locations and their own test software to perform the tests to get the baseline.

Using this info that Google has captured from their side, they will then determine the page score. Websites with higher page scores will of course be ranked higher. So if Google's tests are saying the TTFB is high, then the ranking will drop regardless of what WebPageTest by Catchpoint says.

Sadl,y the nature of the beast
 
bluesteam said:
This is very helpful thank you but the problem is that Google will use their own test locations and their own test software to perform the tests to get the baseline.

Using this info that Google has captured from their side, they will then determine the page score. Websites with higher page scores will of course be ranked higher. So if Google's tests are saying the TTFB is high, then the ranking will drop regardless of what WebPageTest by Catchpoint says.

Sadl,y the nature of the beast
Click to expand...
YUP we should get all of Google itself on 403 ;)
So way to much control for them, better people are going to use duckduckgo and co , i tell everyone try that first only if you can't find with then try, because the power and privacy probs for past en wors very very future is :(

But again to have your server / webasite checked you need to check on your own zone , on several times, then yoy know it is your server / network, that is partly under yoyr control then or the hoster / datacentre for that.

Other things are only to switch to other datacentre where google has better connections... :( But website vistors they expect a fast ... so take care to have it in your zone..
 
yh
ikkeben said:
YUP we should get all of Google itself on 403 ;)
So way to much control for them, better people are going to use duckduckgo and co , i tell everyone try that first only if you can't find with then try, because the power and privacy probs for past en wors very very future is :(

But again to have your server / webasite checked you need to check on your own zone , on several times, then yoy know it is your server / network, that is partly under yoyr control then or the hoster / datacentre for that.

Other things are only to switch to other datacentre where google has better connections... :( But website vistors they expect a fast ... so take care to have it in your zone..
Click to expand...
yh, running the webpagetester from catchpoint shows a 0.5s TTFB which is much better than 1.1s

running the same test on a simple "Hello World" shows a 0.2s which feels a little long for a simple "Hello World"
 
bluesteam said:
yh

yh, running the webpagetester from catchpoint shows a 0.5s TTFB which is much better than 1.1s

running the same test on a simple "Hello World" shows a 0.2s which feels a little long for a simple "Hello World"
Click to expand...
No is not long network traffic and dns nameserver and maybe https redirect.

We have that between 0,1 and 0,6 depending on location and times for tests and servers / vps
 
ikkeben said:
No is not long network traffic and dns nameserver and maybe https redirect.

We have that between 0,1 and 0,6 depending on location and times for tests and servers / vps
Click to expand...
Yes of course ??

Thank you so much! You have all been so wonderfully helpful. I appreciate everyone's time they put in to solving this for me.
 
Please guys, try to not quote full posts all the time.. it gives a very unclear impression when you have to read it to help. ;)
 
You can find something out by trying this: open the hello world in your browser or maybe some other tool that can measure the time. If that is faster than when Google tries it: big chance it's because the server handling the hello world script, is doing it right after serving ALL the other files requested by Google. Google will, just like a browser, request all the files of a website at once. Your server has to handle all the requests as well. Then your server is busy handling all the other requests, before it can handle the hello world script. So that could definitely be the issue, it's not the hello world script itself, but actually when the server has time to handle that file.

Tips to speed everything up are actually useful then, because as soon as everything else is done, the simple ones like hello world can also be handled faster. Especially when resources are limited. You could also look at how many open connections or php threads at the same time are allowed. Maybe your server can handle more, but it's limited by settings.
 
You must log in or register to reply here.
Back
Top