Reduce time to first byte and speed up Magento

[Goivvy.com]

Magento might be slow. We published the tutorial on how to speed up magento by reducing time to first byte TTFB.

summary:

• Enable builtin magento Profiler
• Disable not used magento extensions or observers
• Go over every .phtml file to optimize php code
• Upgrade magento to the latest version

Go check it out http://www.goivvy.com/blog/magento-o...irst-byte-ttfb for the detailed instructions on how to get low TTFB for magento store.

View more threads in the same category:

• 9 Reasons to Make your Magento Site a PWA
• What is the use of Domain Name System?
• How to Defining Whether Your E-commerce Website Is Successful or not?
• Boosting E-commerce Conversion Rate With Exit PopUps
• What to Expect From a Professional Magento Developer?
• Magento Vs. Shopify: Which is a Better Ecommerce Platform?
• Additional Facilities That Help People To Shift Easily Without Burden
• How to change once order completed in magento admin panel?
• How to track the shippment?
• How to speed up Magento 2 website ?

[funkywizard]

Thanks for the reference, should help a lot of people. I just want to add that it would also be useful to remove any external scripts that are not strictly required. They can really slow things down.

[Goivvy.com]

Thanks for the reference, should help a lot of people. I just want to add that it would also be useful to remove any external scripts that are not strictly required. They can really slow things down.

most modern scripts support async loading

what you should also do is to remove blocking Javascript aka defer parsing of Javascript

[clapcreative]

There are only 3 areas you need to look at when optimizing the performance of your store - hosting, time for the first request to complete, and the number of requests per page. You may be interested to read our blog post, and also use our performance profiler, but to summaries:

Hosting - this is of course the foundation of your entire site and performance can only be as good as the hardware your site is running on allows. You do need to have acceptable page load times on uncased pages, and this is purely so that you maintain performance on pages which should not be cached such as the cart and checkout.

If the site suddenly becomes very slow when you go to checkout, you are likely to lose customers, so the right hosting properly configured is a must as a starting point (who you host with doesn't matter). Important rules though - always steer clear of shared hosting when it comes to Magento, and host on a server geographically close to you and your main target audience.

Time for first request to complete - by this I mean the time it takes for the server to generate the HTML in response to each request, excluding the time it takes for your request to reach the server, or the response to reach the browser after being sent by the server as these are connection dependent. This request is extremely important as only when this has completed will the user start to see anything render in their browser at all. It's this time which all FPC solutions (Varnish included) improve on so the user will see content start to render in their browser more quickly.

Number of request per page - while the above affects when the page will begin to render, the number of requests on the page affects how long it is before the page has loaded entirely with all assets - so images, JS and CSS. FPC will have no affect at all on this.

Every image, JS and CSS file which loads on your page is gathered via it's own request to the server. Every request takes a finite time to complete so you can therefore logically see that the more assets you use, the longer it takes for the page finish loading. Additionally the more requests you have the more requests queue and are idle as only a few requests can be sent at any one time - the makes page load times even longer.

Reducing the number of JS and CSS assets is straightforward - just turn on merging, but reducing the number of image assets is harder and requires you to review your page design and basically determine where images can be removed. You can also often reduce the number of images by combining smaller images into a very few single image 'sprites' or by leveraging more capable CSS3 styles to achieve things like rounded edges and button graphics which would historically have been done using images.

Around 60 requests per page will give decent performance, but 30 is a good target to aim for.

[StevenAntonucci]

Caching is easy with LiteSpeed:

https://www.litespeedtech.com/soluti...o-acceleration

[Bizmagestore]

Store Error Log Manager Extension is specifically meant for admin (online merchants) to track website and log errors, not found pages along with wrong login attempts. This extension helps merchants/developers to run their online store more proficiently and seamlessly by finding different types of errors and reducing it all by finding solutions to them.

Attachment 4783

SEO Data Template Manager will help you set the SEO attributes for your online store. You can optimize your online store according to the latest requirement of search engines.

You can optimize the category pages, Product pages and CMS page for a particular product or group of products with this extension. This can lead you obtain higher position in the various search engines.
Attachment 4784

[marknguyen]

Why don't we defer JavaScript loading to reduce loading time and speed up Magento sites?
It is a truth that a web page will load JavaScript and CSS resource before loading HTML and the content of page. Therefore, this thing causes Magento sites perform slower and worse, which can make customers feel annoyed and leave sites immediately.
To solve this issue, there are two ways that most people often take advantages:

1. A manual way: make code changes to defer JavaScript but it is very complicated and takes much time as well as staff to take on

2. A Magento extension: deferring JavaScript loading becomes easier than ever by installing an extension for Magento site such as Defer JavaScript extension because it helps tp automatically defer parsing of JavaScript loading till the last moment after all HTML and CSS loading. It means that this extension will put all JavaScript files to the end of page so that a web page will render HTLM and CSS before loading JavaScript. Moreover, we can exclude controller or path that are not affected by this module. As a result, Magento sites are speeded up quickly and effectively without much efforts.

In addition, for Magento 2 sites, we can also install Defer JavaScript extension for Magento 2 to make them perform better and enhance shopping experience for customers

[olivedev]

The first byte time issue is usually because of the server performance. If you are on a shared hosting, your first byte time wouldn't be as good as VPS. For example, I have experienced a 0.3s first byte time on Cloudways magento hosting, whereas 0.8s first byte time on shared server.