When a shop’s search or filters take seconds, people notice. This page collects the outside studies that look at speed and shop search, in plain words, each with who ran it, who paid for it and what it cannot tell you.
We list them so you can judge for yourself. None of them is about our product.
Eight studies
What was found, and the caveat next to it.
Findings are paraphrased. Every source link opens in a new tab and was checked on 4 October 2026.
Agencies 55 and Deloitte · 2020 (2019 data)
A tenth of a second on mobile
Across 37 brand sites, a 0.1 second improvement in four mobile speed measures went together with 8.4% higher conversion on retail sites.
Method
Over 30 million sessions on 37 European and American brand sites, watched for about a month.
Funded by
Commissioned by Google.
Caveat
Observational, mobile only, and each of the four speed measures improved on every page of the journey. It is about page loading, not search.
When Google added 100 to 400 milliseconds to its search results in a controlled test, people searched a little less (0.2% to 0.6% fewer searches per user), and some of the drop stayed after the delay was removed.
Method
Controlled experiment with a control group, delays added on the server side.
Funded by
Run by Google on its own search engine.
Caveat
Google web search in 2009, not a shop. It measures how many searches people made, not sales.
Baymard rated the search of 170+ e-commerce sites and apps and found 56% do not adequately support what shoppers try to search for. In a separate benchmark of 344 sites, 68% show a no-results page that is a dead end.
Method
Expert and usability benchmark: 10,000+ ratings on 170+ sites for search, and 344 sites for the no-results page.
Funded by
Baymard sells research and audits.
Caveat
A user-experience quality score of leading sites, not lost sales, and not WooCommerce shops in particular. The two figures come from different benchmark rounds.
Constructor, as reported by IT Brief · 2024 (October to December)
Shoppers who search carry a lot of revenue
In an analysis of 609 million searches on 113 retail sites, shoppers who used search were 24% of traffic and 44% of revenue.
Method
Search and revenue data from 113 retail sites, about $9.8 billion in revenue.
Funded by
Constructor sells e-commerce search.
Caveat
Correlation: people who search already know what they want. It does not show that fixing search raises sales. We link press coverage; the vendor report itself was not opened.
In 2024, 34% of WooCommerce sites had a good mobile Largest Contentful Paint, below Shopify, OpenCart and Shopware.
Method
Field data from real Chrome users across the web, grouped by detected platform.
Funded by
Community project with no vendor stake.
Caveat
Covers all WooCommerce sites and is about how fast the first big element appears, which is mostly front-end weight. We do not fix that. It says nothing about search or filters.
In Baymard’s tests on small direct-to-consumer sites, every tester began by browsing the menu and only 15% even looked for search. The study says search grows in importance as the catalog grows, from roughly 20 products up.
Method
Usability testing on niche direct-to-consumer sites and a benchmark of 26 sites.
Funded by
Baymard sells research and audits.
Caveat
Qualitative testing with small samples. Its point is that tiny shops rarely need search, which is why we write for shops with many products.
None of these studies tested Searchmaker or any local-index search plugin, and no Searchmaker store has a conversion measurement yet.
That page-speed results carry over to search latency.
Most studies here measure how fast a page loads. Google’s 2009 test is about delays in Google’s own search results. Neither is the time a shop’s live search takes to answer.
That “56%” means lost sales in WooCommerce shops.
Baymard’s 56% is a user-experience quality score of 170+ leading sites and apps. It is not a measure of sales, and it is not about WooCommerce.
That shoppers who search buy more because they search.
People who use search already know what they want. Constructor’s numbers are a correlation, not proof that improving search lifts sales.
That we fix your loading speed.
WooCommerce’s weak mobile Largest Contentful Paint is mostly front-end weight: themes, images, scripts. Searchmaker works on search, filters and feeds. It does not fix LCP.
What we measured ourselves
Our own numbers, with their scope.
These come from our benchmarks. They are different layers, so we never compare one with another.
One real store, about 6,500 products
The theme’s live search took about 1.4 s per search, round trip. Searchmaker’s engine answered in single-digit milliseconds. Different layers, so no ratio. One store, our test.
Engine level, synthetic 100,000 products
Filtered queries in well under a millisecond of engine time, with no web server and no WordPress. Not a page-load time.
Engine level, synthetic 100,000 products
Full index build in about 6 s, and a Google Merchant feed of 240,000 per-variation items in about 6 s. Not measured on a real WooCommerce database or a slow host.