Choose the right investigation scope
Understand the package boundaries and the information that helps us investigate your store.
Start with evidence that fits your problem
See what an investigation report contains, then explore the technical symptoms relevant to your store.
Explore the performance evidence
Describe the affected workflow
A public-page score cannot explain every operational delay. Our guides to slow Admin tasks and search performance problems help define a focused brief for internal investigation and separately scoped improvements.
Start with a Magento Performance Investigation
Get evidence of what is slowing your store down, a clear report and prioritised next steps. Compare Snapshot, Full Investigation and Peak Readiness to choose the scope you need. Optimisation and implementation are quoted separately.
Specialist performance work for Magento stores
We work on Magento Open Source and Adobe Commerce implementations, including stores with custom modules, large catalogues and connected business systems. Our review follows the actual behaviour of your installation, with the edition, release and hosting arrangement taken into account.
The scope can cover slow category or product pages, delayed search, an unresponsive Admin area or a checkout that takes too long to complete. We establish which journeys matter most and collect evidence about where time is spent. That allows us to recommend specific application or infrastructure work and explain why it deserves priority. You receive a technical plan that relates to your store, rather than a generic list of optimisation settings.
Magento code and extension optimisation
We investigate custom code and extension behaviour that contributes to slow requests. The work can involve repeated data loading, unnecessary processing, costly database activity or external requests made during a customer journey. We trace the relevant behaviour and develop a targeted correction.
Our Magento development service supports the implementation, including changes to modules and theme components. We assess the function the code provides before altering it, so the performance work preserves the business requirement. Relevant journeys are tested after the change, and we document the correction for future maintenance. This gives your business a route from a measured bottleneck to a maintainable code-level improvement.
Caching that works with your catalogue and customers
We review the store's caching behaviour and the parts of the implementation that affect it. Our work can cover page caching, application caches, invalidation patterns and the configuration of the supported cache services. We check the requirements of the exact Magento release before changing the environment.
The review includes correctness as well as speed. Customer-specific prices, account information and basket state must continue to behave as intended. We test the relevant logged-in and guest journeys and investigate customisations that prevent useful caching or cause excessive invalidation. The deliverable is a defined change with evidence of its effect, together with any operational guidance needed when catalogue data or configuration is updated.
Catalogue, database and search performance
We optimise the processes that support browsing and maintaining a Magento catalogue. This can include reviewing slow database queries, indexing behaviour, search configuration and the way custom features request product information. We connect the technical findings with the pages or staff tasks affected by them.
For search-related work, we assess the service and configuration used by the installation, including supported OpenSearch arrangements where applicable. We also review how imports and catalogue updates interact with indexing and customer requests. Changes may involve code, scheduling, configuration or capacity. We explain the recommendation and check that the resulting catalogue and search behaviour remains useful for both customers and the people maintaining products.
Frontend performance and Core Web Vitals
We improve the way Magento pages load and respond in the browser. Our frontend work can address images, fonts, JavaScript, styles and third-party features, with attention to the actual page templates and interactions your customers use. The objective is a more usable storefront, supported by relevant measurements.
We consider loading, responsiveness and layout stability, using controlled tests and available real-user data for their appropriate purposes. A product page and a category page may need different changes, and a good homepage result does not establish the behaviour of checkout. We select representative journeys and compare the result after implementation. Our wider performance service covers this frontend work alongside the server and application investigation.
Checkout and integration delays
We investigate performance problems in checkout and the services it depends on. A slow payment or delivery response, custom calculation or unnecessary synchronous process can affect the time a customer waits. We follow the request through the relevant parts of the implementation and identify what can be improved.
The work preserves the transaction and business rules that checkout needs to enforce. We use appropriate provider test facilities and check the resulting order and payment behaviour, not just the time taken to display a page. Where the issue involves an external system or the processing around it, our checkout support and integration expertise provide the development capability to complete the correction.
Server resources and background work
We assess the relationship between the Magento workload and its hosting resources. Customer requests, scheduled jobs, imports and other background processes may compete for CPU, memory, storage or database capacity. We review that behaviour before proposing configuration changes or additional resources.
Our server management service can deliver the agreed infrastructure work. We can also coordinate with your existing hosting provider where it owns the relevant controls. The scope makes those responsibilities clear and accounts for the application requirements. This helps distinguish a genuine capacity need from an inefficient process that would continue consuming resources after a hosting upgrade.
Know what needs fixing before commissioning changes
If the cause is still uncertain, our Magento Performance Investigation provides a defined assessment and prioritised report. Implementation is scoped separately, so the proposed work can follow the evidence.
Already have a checkout-specific problem? Our slow Magento checkout guide explains how to describe the affected stage and gather a useful brief. Agree the journey, conditions and success checks before changing code or infrastructure.
Bring a more useful performance brief
Our guides to high Magento TTFB and full-page cache problems explain the evidence worth collecting before implementation. They help distinguish an initial response delay from cache eligibility, invalidation and application work.
Evidence, priorities and verification
We begin with an agreed set of journeys and a baseline that can be used to assess the work. The findings identify the bottlenecks, proposed corrections and relevant dependencies. You can then choose a defined implementation scope, with the purpose of each change explained.
After implementation, we repeat suitable checks under comparable conditions and review the affected functionality. We report what improved, what remained unchanged and where further work may be justified. The result is a usable account of the performance work and the evidence collected. Where traffic or third-party behaviour limits a comparison, we state that limitation rather than presenting an isolated score as a complete measure of the store.
Why Midoriweb for Magento optimisation?
We can implement changes across the application and infrastructure involved in the request. That makes it possible to follow a performance finding into the code, database, cache or connected service and carry out the relevant work. Your business has a technical partner capable of addressing the underlying implementation.
We also understand the commercial functions the store must preserve. Pricing, stock, delivery rules and order handling remain part of the acceptance criteria. The service is designed to improve performance while maintaining a usable trading platform. Ongoing Magento support can keep performance findings connected with maintenance and future development priorities.
FAQs
Can you work on a live store without a rebuild?
Yes. We assess the existing implementation and scope targeted improvements. A separate test environment is used where the proposed changes require it, and the release approach is agreed before implementation.
Do you promise a particular PageSpeed score?
We agree goals around the actual site and measure the work performed. A score depends on test conditions and other factors, so we report relevant evidence and functional checks rather than guaranteeing a universal number.
What information should we provide?
Share the affected pages or operations, when the delay is most noticeable and any existing monitoring information. Our Magento performance guide can help you prepare, but a technical diagnosis is not required.
How do we engage Midoriweb?
Book a consultation or tell us about your store's performance. We will recommend a focused review or implementation scope and explain the next step.
