Analytics and audits
Online shop audit
for PrestaShop
PrestaShop handles large catalogues well, but it can be sensitive to too many modules and a neglected database. We check what slows your shop down and where orders get lost.
What sets PrestaShop apart from other platforms
PrestaShop is built around a large catalogue: attributes, combinations and multi-language support are built into the system. With thousands of products this is a big advantage, but when a shop grows without order in its data, the same features start to slow it down.
The second difference is modules. Many shop features run as separate modules, and each of them can add its own database queries and scripts to the page.
Performance: database, combinations and cache
With large catalogues, the database is often the bottleneck. Combination tables grow quickly, and without the right indexes opening a category requires many heavy queries.
We also check the cache configuration, how product thumbnails are generated and in what format they reach the page.
- Table size and fragmentation, indexes, slow queries
- Number of active modules and their effect on page generation time
- Cache configuration: Smarty, CCC, server cache
- Generation and format of product thumbnails
- PHP version and server settings for PrestaShop
Purchase path and checkout
The default PrestaShop checkout often gets extended with more and more modules until it becomes hard to use. We check the number of steps, fields required for no reason, the handling of business orders with a tax ID (NIP), and whether delivery costs appear early enough.
We also test the full path on a phone, because some problems only show up on a small screen.
Versions and updates
Updating PrestaShop requires the modules and theme to support the new version. In the report we do not stop at recommending an update: we describe exactly what is blocking it, for example an incompatible module, a modified theme or a custom-built feature.
Make a copy of the files and database, restore it in a test environment and run the update there. You update the live shop only when everything works on the copy.
Order in the catalogue: attributes, features and combinations
PrestaShop distinguishes between attributes (which create combinations, e.g. size) and features (descriptive, e.g. material). Confusing the two during import multiplies combinations that mean nothing for sales, and the database grows for no reason.
In the audit we check how many combinations actually make sense and show you what can be simplified. A simpler catalogue speeds up the shop and makes life easier for the people who handle orders.
Modules: what loads on every page
We check the list of active modules and measure how much time each one adds to page generation. We also point out unused modules that are still active.
We look separately at third-party scripts: chats, review systems, advertising pixels. Each of them connects to an external server, so if it fails or runs slowly, it can slow down your shop.
- Page generation time broken down by module
- Unused modules that are still active
- External scripts and their effect on loading time
- Module compatibility with the PrestaShop and PHP version
Update, new installation or platform change
The choice of path depends on what is blocking the update. Sometimes it is cheaper to build a new shop and migrate the data, and sometimes an update and replacing a few modules is enough.
In the report we set out every sensible path with an estimate of cost and risk, calculated for your specific shop.
| Path | When it makes sense | Main risk |
|---|---|---|
| Update | Standard theme, modules have new versions | Module conflicts, need for testing |
| New installation | Heavily modified theme, a lot of dead code | Migration of data and redirects |
| Platform change | Catalogue smaller than expected at launch | Loss of PrestaShop-specific features |
SEO in PrestaShop: filters, duplicates and URLs
Filters are a common source of SEO problems in PrestaShop. Every combination of filters can generate a separate URL with almost identical content. With a dozen or so filters there are a great many such URLs, and Google spends time crawling them instead of your categories.
We check the canonical URL configuration and how pagination is handled. We also decide which filter combinations to index: usually those that match real searches (“work boots size 45”). We recommend blocking the rest from indexing.
- Canonical URLs on categories and on products with combinations
- Handling of pagination and sorting in indexing
- Duplicate descriptions across variants of the same product
- Redirects after a change in category structure
- Structured data for products and breadcrumbs
Multiple languages and currencies for selling abroad
PrestaShop supports multiple languages and currencies straight after installation, but the configuration is often incomplete. Typical gaps are missing language version tags, which make Google show the wrong version, and half-finished translations: categories in Polish, products in English.
If you sell abroad, we also check the basics of the tax configuration: VAT zones and rates. It is worth confirming the findings with your accountant.
Working together
How we work together, step by step
Access to the shop and server
Admin panel, FTP and database. We run heavier tests on a copy so as not to load the shop.
Measurements and tests
Performance, database queries, the full purchase path on several devices.
Report and repairs
A prioritised task list and, if you wish, implementation on our side.
Questions
Frequently asked questions
We audit PrestaShop shops on versions 1.6 to 9.
No. We run heavier tests on a copy of the shop, and on the live shop we only take measurements that do not load the server. Sales carry on as normal.
Yes. We provide PrestaShop shop maintenance: updates, performance and day-to-day support.
Access to the shop admin panel, the server (FTP) and the database, and information on which PrestaShop version the shop runs on.
It can, but you need to make a conscious decision about how long you will stay on this version. In the audit we give the cost and risk of each sensible path: an update, a new installation or a platform change.
Related services
What else may be useful
Your city
PrestaShop audit in your city
For each of these cities we have a separate page describing the local market and how we work with companies there.
Let's check what is slowing your shop down
Give us your shop's address and PrestaShop version. We will send back the scope and timing.