Processwire and "Time to first byte"

[Torsten Baldes]

Hi,

i noticed on my sites and also on other processwire sites, that the time to the first byte is quite long (> 500ms).

Is there a way to speed up this waiting time, without using plugins like ProCache?

i benchmarked some sites from the showcase and from Processwire weekly and nearly all of them perform bad at First Byte Time.

is this related to Processwire or just standard behaviour for php/cms sites?

Here are the tests:

First Byte Time - Grade F

URL: http://c-logistic.de/

Test: http://www.webpagetest.org/result/150601_J7_3992e9491b6acf72f73f10441880e6a2/

URL: http://von-bergh.de/

Test: http://www.webpagetest.org/result/150601_8S_cc7abdaa6519aae4904ea067ca5adf3c/

 

URL: http://www.canton.de/

Test: http://www.webpagetest.org/result/150601_7S_a8d3c3cf3d4f8ad2c3d3048a31864c81/

 

URL: https://www.maletschek.at/

Test: http://www.webpagetest.org/result/150601_42_8379a987c81ee2b8aa11f50b7a74694c/

 

URL: http://www.deichtorhallen25.de/

Test: http://www.webpagetest.org/result/150601_SS_90b428db03a86a5a309bd80aec294706/

URL: http://www.orkork.de/

Test: http://www.webpagetest.org/result/150601_VJ_63b76ec1ab9f37a93b9776320059a0a6/

 

URL: http://www.dojofuckingyeah.de/

Test: http://www.webpagetest.org/result/150601_J5_db3c199ddb74cfae513bbbe775b947c8/

 

URL: http://www.schloss-marienburg.de/

Test: http://www.webpagetest.org/result/150601_KY_01db3003b66dfad3b91aa40cbfda8f82/

 

 

First Byte Time - Grade C

 

URL: http://www.grupoolmos.com/

Test: http://www.webpagetest.org/result/150601_ZH_8b9a2af518a9ac0cb30130e2aa3d3f2d/

 

URL: http://www.pipistrello.ch/

Test: http://www.webpagetest.org/result/150601_RK_5cf4d97c7fe1d4db3a145c565a84069f/

 

URL: http://transformationswerk.de/

Test: http://www.webpagetest.org/result/150601_9D_f16e00a262ec9d30b19ff67a290216ca/

 

URL: http://transformationswerk.de/

Test: http://www.webpagetest.org/result/150601_9D_f16e00a262ec9d30b19ff67a290216ca/

 

 

First Byte Time - Grade B

 

URL: http://brakhax2.com/

Test: http://www.webpagetest.org/result/150601_JE_6552783547f8f7b73945a4698af8f231/

 

 

First Byte Time - Grade A

 

URL: http://www.1815.ch/

Test: http://www.webpagetest.org/result/150601_Z5_f97b31533f61453aaeefc6cafef20e83/

 

URL: http://new.korona-licht.de/

Test: http://www.webpagetest.org/result/150601_RD_37ece6079e30ff5858c95db932f91e30/

 

URL: http://processwire.com

Test: http://www.webpagetest.org/result/150601_V0_c812f846f6555e506fbd2b8ba9efe2e6/

 

 

Thanks!

[LostKobrakai]

The answer is quite simple.

flush();
ob_flush();

Use these as soon as you have parts of "final" markup, that you can send to the user. Sadly this needs to be in order, so most of the time it's more like:

"header" - flush - "content" - flush - "footer" - end

This speeds up every request.

Other options are caching and faster servers (and/or cdn). It doesn't necessarily need ProCache for fast caching. TemplateCache and MarkupCache are quite powerful, too, but they do require php to run (fast servers *hint*).

[matjazp]

Sites with A (and B) grade are almost certainly using ProCache. In real life it is really hard to get A grade without ProCache. And yes, some CMS/CMF are faster. The best results are achieved with SSD (for data and for mysql data), tested myself, almost double the speed...

[tsdtsdtsd]

  On 6/1/2015 at 12:23 PM, Torsten Baldes said:

URL: http://www.orkork.de/

Test: http://www.webpagetest.org/result/150601_VJ_63b76ec1ab9f37a93b9776320059a0a6/

The site is currently hosted on an utterly lazy shared webspace. Guess that alone makes a huge difference

Also, caching is currently completely deactivated - and I have no senseful reason for that, mark it as "testing" I'll activate it in the near future