The Brief
Smart Deelz came to us with a straightforward pitch: they had a product catalog, a supplier network, and zero online presence. The ask was simple — build something that sells.
What made this interesting wasn't the tech stack. WooCommerce is WooCommerce. What made it interesting was the constraint: the majority of their target audience browses on mobile, on slower connections, and abandons carts the moment a page takes longer than two seconds to load.
That constraint shaped every decision we made.
What We Built
The core stack was WordPress + WooCommerce, but we stripped it down to what the store actually needed:
- A custom child theme built from scratch (no page builders)
- Product filtering by category, price, and availability — all handled via AJAX to avoid full-page reloads
- A streamlined 2-step checkout (billing → review → done)
- Lazy-loaded product images with LQIP placeholders
- A WhatsApp order fallback for users who preferred messaging over checkout
The Performance Problem
Out of the box, WooCommerce installs heavy. jQuery, WooCommerce's own scripts, theme scripts — on a budget shared host, you're starting at 4–6 seconds load time before you've done anything wrong.
Our approach:
- Defer everything non-critical. Product images, reviews, upsells — none of it blocks the initial render.
- Separate CSS per template. The category page doesn't load checkout CSS. The checkout page doesn't load the gallery lightbox.
- Object caching. Product queries are expensive. We used WordPress transients to cache category results for 15 minutes.
The result: median first contentful paint dropped from 4.8s to 1.1s on a mid-range Android device over 4G.
What We'd Do Differently
The WhatsApp fallback was an afterthought. It became the store's highest-converting channel. We'd build it as a first-class feature from day one next time — a proper "order via WhatsApp" flow with pre-filled message templates, not just a floating button.
Outcome
Smart Deelz launched in March 2025. It's been running clean since.
