How much faster will it actually get?

You get numbers before and after, on your own system and your own data, instead of a promise of “up to three times faster”. Moving catalog search out to Elasticsearch took eight seconds to one; what your system gains depends on where its own seconds are spent.

Do we have to upgrade Odoo first?

Usually not. Most of what costs seconds - queries, indexes, page weight - is independent of the version. Where the fix really does exist only in a newer release, you hear that instead of being sold a rewrite.

Services

Odoo is slow: finding out why, with numbers

Slowness is not an opinion, it is a measurement. First we find where the seconds go, then we change what actually costs them.

What gets measured

The database first: slow queries, missing indexes, the searches that walk the whole catalog. Then the front end - what the browser downloads, parses and executes before a person can click anything.

Core Web Vitals come from real visitors, not from a lab run on a fast laptop. So do the conclusions.

What usually turns out to be true

On a large catalog the search is the first thing to stop scaling, and no index fixes it: at the worst point a search took eight seconds while the warehouse waited. Moving it out to Elasticsearch took that to one.

On the public side the answer is usually weight: a page that shows text should not ship half a megabyte of JavaScript written for a shop you do not run.

What you end up with

Numbers before and after, on your own system and your own data - not a promise of “up to three times faster”. Plus the list of what was changed and why, so the next person can read it.

And an honest line about what is not worth fixing: some of it is cheaper to live with than to rewrite.

Worth reading before you decide

Search on 110,000 products took eight seconds - the same work, written up with the measurements.
What one page of an Odoo site weighs - and what of it can be cut.

Questions that come up before the first call

Why did Odoo become slow?: Slowness is a measurement, not an opinion, and the answer is usually in one of two places. On a large catalog the search stops scaling first, and no index fixes it - at the worst point a search took eight seconds while the warehouse waited. On the public side it is weight: a page that shows text should not ship half a megabyte of JavaScript.
How do you find where the seconds go?: The database first: slow queries, missing indexes, the searches that walk the whole catalog. Then the front end - what the browser downloads, parses and executes before a person can click anything. Core Web Vitals are taken from real visitors, not from a lab run on a fast laptop.
How much faster will it actually get?: You get numbers before and after, on your own system and your own data, instead of a promise of “up to three times faster”. Moving catalog search out to Elasticsearch took eight seconds to one; what your system gains depends on where its own seconds are spent.
Do we have to upgrade Odoo first?: Usually not. Most of what costs seconds - queries, indexes, page weight - is independent of the version. Where the fix really does exist only in a newer release, you hear that instead of being sold a rewrite.

How it looked in practice

Website / online store
Internal system

Germany

Westfalia.de

German e-commerce website

Move from Plentymarkets to Odoo, catalog and warehouse
Forty storefronts on one instance, one deploy

Read the case

Where to start

Show me the page that drags. By the end of the half hour you will know where the seconds go and which of them can be taken back first.

Book half an hour All services