TTFB 5.6 Sec

[slatwallshopfittings]

Hi,
Wondering if anyone can shed some light as to why my website would be a little slow.
I built it myself using Wordpress and woocommerce, i have about 200 products at the moment all with thier own images and description etc.

I also have WP Super Cache installed which seems to have helped a bit with speeds.

Is TTFB at 5.6 seconds a slow website? according to the ranking on the test it is an F, also the keep-alive enabled is rating an F

Any advice woud be greatly appreciated.
Thanks very much in advance

Darrel

[slatwallshopfittings]

Hi,
I forgot to say the website in question is https://slatwallshopfittings.co.uk

Thanks

[GreenGecko]

For an eCommerce site, it’s imperative for your site to be fast, although it could be argued that the more niche your product is, the less important it is.

Site looks good and clean and is delivered through https which is great. The only nit I would pick is that it’s not an html 5 template.

For the implementation, if possible, can you enable keep-alive? That’ll lower the overhead of the site. The TTFB is low, so there’s not much that’s going wrong server side ( well, you should also check with your FPC disabled as well as that can make a huge difference ).

So next thing to look at is delivery. If you can use http2, then that will aide in performance by re-using connections to their fullest so none of the connection overhead. If this is not possible, then you need to look at reducing the resource count. look for something that merges the css and js files… js often breaks when you do this, but you normally get away with css. In addition, using a lazy loader to only show resources on the screen will also help with the perceived speed - I’ve found BJ Lazy Load to be a no brainer for this for years.

[slatwallshopfittings]

Thanks very much for your comments, i will look in to all those options.

@GreenGecko

For an eCommerce site, it’s imperative for your site to be fast, although it could be argued that the more niche your product is, the less important it is.

Site looks good and clean and is delivered through https which is great. The only nit I would pick is that it’s not an html 5 template.

For the implementation, if possible, can you enable keep-alive? That’ll lower the overhead of the site. The TTFB is low, so there’s not much that’s going wrong server side ( well, you should also check with your FPC disabled as well as that can make a huge difference ).

So next thing to look at is delivery. If you can use http2, then that will aide in performance by re-using connections to their fullest so none of the connection overhead. If this is not possible, then you need to look at reducing the resource count. look for something that merges the css and js files… js often breaks when you do this, but you normally get away with css. In addition, using a lazy loader to only show resources on the screen will also help with the perceived speed - I’ve found BJ Lazy Load to be a no brainer for this for years.