metrix | Metrics collector written in golang

GT Metrix looks at your page on desktop without any throttling applied.

Page Speed Insights applies throttling to the network (to simulate 4G) and to the CPU (to simulate a mid-tier mobile phone with less processing power) and in a mobile viewport.

Also on Page Speed Insights the "Origin Summary" is real world data from people's devices, so that is the more reliable and important information.

See these answers I have given for more info:

• throttling applied
• difference between mobile and desktop scores

It is one of those guys who come over and you won't ask them away. It is not closable but it can be neglected. Do not monkey around with any of the two icons in the upper corner on the right. Just switch the pane for Server Timings or whatever another pane you need using the tabs at the bottom.

Just like a single event index can hold many types of events, so can a single metrics index hold many types of metrics.

If this is not the answer you seek then please clarify the question.

As commented, this should not be the way to go as it produces a lot of duplicates (looping through all the rows but only keep the first level). The function can be written as:

list.copy will return a shallow copy. For nested data structures you must use a deep copy.

Your edges function is almost correct. You just missed that with

Here is a summary function which will use the the sum of Sens + Spec as selection metric:

QGraphicsTextItem is held by QTextDocument, which can have a margin.
Setting the margin to 0 and the rectangle will be correctly drawn.

There is no magic switch to make your Magento fast. The speed can be affected by many factors, including the configuration of the infrastructure/server, configuration of the Magento itself, what extensions and/or themes you are using much more.

To answer the 2 questions you asked:

Does the server location affects the performance ?? - Yes but I don't think you should worry about it at this point (unless you are hosting the site in South Africa and your users are mostly from Sweden or you have a similar situation).

Do I have to use a Load balancer?? - I don't think so. You should use a load balancer only when you have such big traffic you want to distribute the load across multiple servers/instances.

I would suggest going through the following as a starting point:

1. Flat data is not that good at this point since Elastic Search is supported in Magento by default. I would suggest setting up that and turning flat data off. See the top description here for more information.
2. Set up Varnish. That should give you a good boost if you are not using it.
3. Set up a CDN. The simplest way to set it up is to sign up for Cloudflare and use that one. You can then tweak some speed settings there to help you achieve a better score.
4. Enable JS minification. This can be done either in Cloudflare or Magento. Check what works out best for you.
5. Ensure that the largest images on your website are sized properly. You shouldn't use a banner image that is 4k or more and is very heavy in size. You can also use a tool such as TinyPNG to reduce the size of your images.
6. As one already commented on your post - share the network tab of Chrome dev tools here. Also, Lighthouse or Measure results could come in handy. That will show more insights into what is causing that massive fully loaded time. Then find the biggest problem makers (what delays the website fully loaded time the most) and try to improve it.