Page load TTFB

simon - 1 year ago

Hi, I have been taking a look at pyrocms demo and it runs pretty slow. It says in the footer "0.41 s | 12 mb v3.2.1" but if i look at the inspector tools it says:

Stalled 10.05 ms
Request sent 0.50 ms
Waiting (TTFB) 6.60 seconds!!
Content download 301.86 ms

Is it the average page load for pyrocms? Thanks!

Answer

william - 1 year ago

I think this depends on where you are, and where the server is located for one thing. Then you can always be unlucky and hit something when its very busy. I have no idea how optimized that site is either so it might lack that.

I am pretty satisfied with our site : https://pixney.com/

From where i am , it loads fully within 1.3-1.6 seconds.

timeline

william - 1 year ago

I am pretty satisfied with our site : https://pixney.com/

From where i am , it loads fully within 1.3-1.6 seconds.

timeline

william - 1 year ago

Another site we built, where we have not even implemented a lot of cache strategies, is loaded also within 1.6s.

Storsjöhus timeline https://bo.storsjohus.se/

piterden - 1 year ago

@simon it is your env issue. Wrong DB or server setup. mcmpspb.ru check it in inspector.

simon - 1 year ago

Thanks William Yes, I think the server was busy, but i dont think is a location issue. The "Waiting" item is related to how much time the server took to prepare the response.

Right now the waiting time is around 2 - 3 seconds :)

cleancookie - 1 year ago

I don't think this is related to your issue but incase this comes up in other people's google searches: Homestead has nfs disabled by default and is really slow with Pyro as a result. You can enable it by adding to your Homestead.yaml:

folders:
    - map: ~/projects
      to: /home/vagrant/Code
      type: nfs

If you're on Mac you can try Laravel/Valet which has been much quicker for me https://laravel.com/docs/5.5/valet

william - 1 year ago

Agreed Simon. For a second the 6s ttfb forced an error to slip in my comment:) Since it was such a long time i took it for load time :)

ryanthompson - 1 year ago

Pyro currently autoloads a lot - using PSR4 and a classmap so the disk IO seems to effect it steeply. While I have GoDaddy sites (yes.. godaddy) that loads much much faster than that I also always use DO / something with SSDs and get really good results that way. Inspect your disk setup most likely ^_^

Opcache and all that usually help in production as well!

william - 1 year ago

@ryanthompson not sure, but i thought he was looking at the demo site on your server? Hmm I might have been mistaken.

simon - 1 year ago

@william yes! i was looking at the demo. But thank you for the advices in order to implement

ryanthompson - 1 year ago

Oh my.. Well I missed that ^_^

Looks like there was some malarky on it - I reinstalled it just in case. Needs to be updated too..