Available for projects & agency overflow · Quick reply, from the person who does the work

WhatsApp contact@allaux.fr
FR EN TR
allaux.
Emergency Discuss my project

Performance and technical SEO

A slow site loses visitors before they even see the product, and a technically poorly structured site gets indexed less well. I look for the real source of the slowdown in the code, the database or the server configuration, rather than layering cache on top of an unresolved problem.

Describe my issue Chat on WhatsApp

What actually slows an e-commerce site down

Image weight is often the most visible cause, but rarely the only one: poorly optimised database queries on a product page with many variants, third-party scripts loaded in a way that blocks rendering, or an undersized server configuration all weigh just as much, and are harder to spot without looking at the code.

Technical SEO covers what affects how search engines index and read the site: URL structure, markup, server response time, redirect handling. It's not content SEO or link building, which I don't do.

What I look at

  • Server response time

    Server, application cache and database configuration for the most visited pages.

  • Database queries

    Finding slow or unnecessarily repeated queries on high-traffic pages.

  • Resource weight and loading

    Images, scripts and stylesheets, their order and how they load.

  • Third-party scripts

    Tracking, chat or advertising tools that slow rendering without it always being obvious at first glance.

  • Structure and indexing

    URLs, redirects, technical markup and the files that control how search engines crawl the site.

How a performance audit runs

  1. Measuring the current state

    Recording load times and blocking points on representative pages of the site.

  2. Identifying the causes

    Analysing the code, queries and server configuration to find the real source, not just the visible symptom.

  3. Prioritised fixes

    Addressing the highest-impact points first, with a clear price for each fix.

  4. Re-measuring

    Before/after comparison on the same indicators, to confirm the fix has a measurable effect.

  • 2019 e-commerce developer since
  • 3 platforms: PrestaShop, WooCommerce, Shopify
  • 3 working languages: FR, EN, TR
  • 100 % direct contact with the developer

No middleman: the person who replies is the one who works on the code.

Describe your need in one minute

A few targeted questions so I can reply with an estimate rather than another questionnaire.

symptome
plateforme
catalogue (facultatif)
mesure (facultatif)
Please provide an email or a phone number so I can get back to you.

Please provide an email or a phone number so I can get back to you.

Frequently asked questions

Do you guarantee a performance score or a Google ranking?
No. I fix identified, measurable technical problems, but a score or ranking also depends on factors outside my control, like content or competition on the target keywords.
Do you do content SEO or link building?
No, that's not my field. I work on the technical side of SEO: what touches the code, structure and speed of the site.
Is a performance audit worth it even if the site runs fine?
It can help you get ahead of a slowdown before it becomes a problem, especially before a period of high traffic you can anticipate for your business.
What tools do you use to measure performance?
Standard industry measurement tools, backed up by direct analysis of the code and queries, since automated tools don't catch everything.
Does the audit need redoing after every site update?
Not systematically, but a new module or theme update can reintroduce a problem that was already fixed. A quick check after a significant change is a reasonable precaution.