20 blocking script resources and 8 blocking CSS resources. Until you get these whittled down to as few as possible (ideally none), all of the site’s key, user-experience-centered performance metrics will suffer.
Also on lines 43-48 you have a number of external fonts. These can block text rendering. Are all these scripts needed for the home page render? Think about which scripts are unnecessary as AJ points out. For example, some of the scripts such as jqueryform.js printfriendly.js are probably unnecessary for first render.
I think it is quite good already. I managed to reduce .js scripts from 20 down to 12, but could not reduce number of .css as visual problems emerge. I also set up asynchronous loading for queryform.js, printfriendly.js…
Still there are time gaps appearing. Could it be because of slow CDN content loading (it appears quite high loading time in both links)? At the time gap the file “…/wp-includes/js/wp-emoji-release.min.js” appears which could maybe also be problematic?
Any further comment and advices very much appreciated. Thank you kindly!
The poor grades for TTFB are due to the WPT itself, assigning a ridiculously low target based on use of a CDN. Patrick acknowledges this and says he will be addressing it. Here’s yours:
[quote]First Byte Time (back-end processing): 67/100
414 ms First Byte Time 90 ms Target First Byte Time
[/quote]
That target is just a silly number. Therefore it is safe for you to ignore the D and F grades for TTFB.
And just, dump cloudflare. Get off its nameservers. It doesn’t improve performance.
I will dump it as suggested. Thank you very much all for your comments!