My website judbd.com with kirby 2.2 was blazing fast. Tonight I updated it to 2.3 and I’ve time to first byte in the 500-3000 ms range, or 3 seconds to display something on the page (server in php 7). Same thing on my local machine (php 5.5), server, and another faster server (php 5.6) (on this server, TTFB is average 300-500ms)
I have tested 2 others 2.3 kirby website on my server, and TTFB are very reasonable, like 40-100ms (sometimes randomly 1000+ms, don’t know why)
Did you know how can I test further to find the issue ? Is this kirby 2.3 ? Is this a combination of kirby 2.3 + my templates/blueprints/whatever (as otherswebsite seem fast) ?
I just changed my blueprints from php to yml in top of 2.3 update but I dont thing it change anything.
My portfolio make a heavy use of the ->thumb() method, maybe the new version have problem with it even once generated and cached ?
A friend of mine tested it a little bit and says that kirby->launch is the longer to load but I don’t know what to do with this information.
If you have any idea of how I can test and speed up the TTFB ? Is anyone experience this ?
Maybe I can try to reinstall it from scratch instead of just update kirby and panel folder ?
That’s strange, I haven’t seen that before. If other sites work on your server, it’s probably a plugin or template that’s causing the issue. Blueprints are only loaded by the Panel, so they shouldn’t be able to cause this.
I’ve had the same issue twice now and just have no clue what went wrong… What fixed it for me was to copy a fresh site folder and then piece by piece put my blueprints templates etc in until I found the origin of the problem. I haven’t found that origin buy the websites are fast again.
I was on my way to rollback to 2.2 and upload it aside the problematic 2.3 + upload a 2.3 version to text it but I think I’m just going to test the fresh install.
Maybe the thumbs cache is problematic ? Except that I can’t see any difference between my different websites.
I feel that too at the beggining but now it seems more random, though the 2.3 seems to have serious slow bumps sometimes (more than the 2.2 version). I will try with 2.3 fresh install soon.
Background images are random, also I think that the weight of files are not in question here as the problem seems to be on the GET or Time To First Byte.
I use a lot of ->shuffle() method, maybe the new kirby struggle with it ?
For the hero image on home I don’t use thumb: <section id="banner" style="background-image:url('<?php echo page('randomitems')->images()->shuffle()->first()->url();?>')">
For project images I use thumbs but I’ve pre-generated them before giving you the links. Some thumbs of random projects have to be generated but some pages with same content (like about, publication, portfolio, side project page) are slow too.
I know that generating thumbs halt the loading, but I don’t think it is since thumbs are already generated for principal pages.
I’m not entirely sure with that, but didn’t the thumbnail names change with Kirby 2.3? Maybe that was an issue and the thumbnails were created again every time the page loaded?
Indeed the thumbnail names changed with 2.3, so purging the thumb folder definitely is a good step to get a better picture. It looks like in your last test the versions are pretty equally fast. So I’m quite sure it was a thumbnail issue.
Purge of thumbnails change nothing, I made a fresh install (kirby 2.3.0 in folder, then copy of my /site /assets and /content) on my production serveur and it seems to work better, as @Thiousi suggested. Not sure if it was kirby or my hoster.
I made a fresh install on my test server and githug confirms files are the same than before, so I don’t know how a “fresh” install could change anything
I’ll let you know if I encouter others speed issues.
Note : I’m going to erase the tests domains to avoid duplicate content.
Yeah the mistery remains here too. The speed issue had transfered to the panel too with the page saving taking virtually forever on the progress bar in the panel but the saving actually happening as fast as usual. I could refresh the front-end and see changes when the pannel was still spinning for minutes…
I really tried to find a replicable issue but haven’t posted here yet as I’m just dumfounded as to how it came about and how I fixed it.
…weird, issue - though!