Vai al contenuto principale
Discuss your project
Discuss your project
Case study · Trattamix

Rebuilding Trattamix from a legacy WordPress stack to a custom high-performance platform.

A complete redesign for a physiotherapy and healthcare business, combining a large service catalogue, clearer conversion paths, technical SEO foundations and a Boost-based custom implementation.

Discuss a similar project View services
Evidence status

Measured progress, presented with the right context

Verified legacy baseline

The original live site was tested before the rebuild, providing a documented starting point for comparison.

Current staging results

The new-build figures describe the controlled pre-launch environment and are not presented as final live metrics.

Production verification next

After launch, dated public measurements and real-user data will replace the provisional staging evidence.
60 → ~90 Mobile performance: legacy to staging
67 → 100 Desktop performance: legacy to staging
75 → 98 Yellow Lab: legacy to staging
0 HTML validation errors in staging
Legacy baseline

The starting point

The previous Trattamix site had an ageing visual and technical foundation. Audits recorded PageSpeed performance scores of 60 on mobile and 67 on desktop, a Yellow Lab score of 75/100 and structural validation problems. The site also needed to present a broad and detailed range of services without making navigation or content management harder.
  • Weak mobile and desktop performance
  • Structural HTML and heading problems
  • High front-end complexity in key areas
  • A content catalogue that needed clearer organisation
Business and technical goals

The project objective

The redesign was not treated as a theme replacement. The objective was to create a faster, clearer and more maintainable platform that could support search visibility, service discovery, conversion and future functionality from one controlled foundation.
  • Explain services and treatments clearly
  • Create stronger paths towards contact and booking
  • Improve technical quality and performance
  • Reduce dependence on disconnected third-party components
Implementation

What changed in the new build

Custom theme system

The visible site is generated from a tailored BTF configuration rather than a purchased commercial theme.

Service architecture

Contenuto is structured to help visitors understand treatments, problems and the appropriate next step.

SEO foundations

Page targets, headings, internal links, metadata and technical output are planned as part of the rebuild.

Performance control

Assets, components and effects are selected with explicit loading and rendering budgets.

Validation

HTML quality and structural checks are used as release criteria rather than optional post-launch tasks.

Expandable platform

The site can accept additional Boost modules and custom functions without replacing the core architecture.
Measured progress

Staging results before public launch

The new build reached approximately 90/100 mobile performance and 100/100 desktop performance in PageSpeed testing, 98/100 in Yellow Lab Tools and zero HTML validation errors. These figures are promising but will not be presented as final live evidence until the production release is tested under the same documented conditions.
  • Same-page before and after comparisons
  • Multiple test runs rather than one favourable screenshot
  • Separate lab metrics from real-user Core Web Vitals
  • Publish final dates, URLs and tools used
Explore WordPress performance optimisation
Transparent limits

What the case study does not claim yet

The rebuild has not yet produced a long enough public data period to claim growth in traffic, rankings, enquiries or revenue. Those outcomes require analytics, Cerca Console data and time after launch. The current evidence is technical: a cleaner, faster and more controlled platform.
Project workflow

How the final case study will be completed

  1. Passaggio 1 di 4

    Go live

    Publish the new website and verify production configuration, forms, redirects and critical pages.
  2. Passaggio 2 di 4

    Repeat tests

    Run comparable PageSpeed, Yellow Lab and validation checks and use representative results.
  3. Passaggio 3 di 4

    Monitor

    Review errors, crawl behaviour, Cerca Console and early conversion data.
  4. Passaggio 4 di 4

    Add client evidence

    Include a testimonial and business outcomes only when they are available and authorised.
Project enquiry

Need to replace a legacy WordPress stack without repeating the same problems?

Describe the current website, its limitations and the business result the rebuild needs to support.
Discuss your project Explore website redesign