Smart Wines: from a slow shop to connected operations
I connected a WooCommerce redesign with performance, technical SEO, catalogue work and links to Fakturoid and day-to-day operations.
- Stage
- Implementation
- Client
- Smart Wines ↗
- Author
- Jan Chýla, AI Honza
- Updated
- 31 August 2026
What changed
This was not only a visual redesign. I reduced technical debt in WordPress, simplified the public content footprint, cleaned catalogue data and separated changes that were safe to automate from stock and payment operations that required verification.
- WordPress and WooCommerce redesign
- Performance and database cleanup
- Technical SEO and sitemap cleanup
- Catalogue, invoicing and operational links
What was getting in the way?
The shop used old, heavy templates, mobile behaviour was unreliable and filtered URLs created duplicates. The database had grown substantially and catalogue information in WooCommerce and Fakturoid could not be safely treated as one source without checking individual matches.
During the first audit, the homepage HTTP response took roughly 20–22 seconds. This is a point-in-time server response observation, not a Core Web Vitals result.
What I did
Website and journeys
I redesigned the homepage and key pages, rebuilt the mobile layout and clarified the main routes through the shop.
Performance
I reduced unnecessary plugin files, configured page and Redis object caching, and cleaned database logs and expired sessions.
Search eligibility
I corrected canonicals and noindex rules for filters, cleaned the sitemap and schema, and removed demo, duplicate and expired pages.
Catalogue and operations
I standardised SKUs, vintages, images and content, compared WooCommerce with Fakturoid without guessed matches, and documented safer operational procedures.
Verified technical results
Values below come from defined before-and-after checks. They describe technical and operational changes; they do not prove an increase in revenue, orders or organic traffic.
How to read these numbers
The database and asset counts are snapshots from the documented checks. PHP warnings were observed on 27 of 32 sampled products before the fixes and none appeared in 106 follow-up HTTP checks.
Catalogue expansion in Fakturoid does not mean live WooCommerce stock was changed automatically. Where product matching was ambiguous, I kept the case for manual review.