Breakdown of waiting time

The waiting time corresponds to the time spent waiting for the server (contains the time spent in Magento). QUANTA then breaks it down into two steps thanks to the profiling module that you had installed by your integrator.

• Magento Time Time taken by Magento to generate the page: This factor should be optimised in collaboration with your agency (or your developer)
• Other Processing time outside the Magento application: Optimization of this factor should be done in collaboration with your hosting provider in most cases

If most of the time is spent in "Magento time", then click again on "More details" to analyse the time spent by Magento in each feature (this is the case in this example).

Magento code analysis

Quanta details the page generation time within Magento in different stages.

• Find the source of your site's optimizations by starting with the most time-consuming steps.
• You can zoom in on two particular steps: the "Loading Magento" step and the "Rendering blocks" step. To do so, click on the "More details" buttons.
• In this example we will zoom into the Layout Rendering Time.

Focus on Magento blocks

Quanta automatically identifies the blocks of Magento code that take the longest or have the greatest variation.

Select the blocks you are interested in (preferably the blocks that took the longest to generate, i.e. at the top of the list) and click on "View block details".

Each block can be analysed/comparisoned in the form of graphs in order to see how it evolves over time (the timeline is interesting here to see the possible recurrence of a problem).