9 articles tagged performance.
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.
A home-screen icon, instant repeat visits and a notification when the order ships — you can have all three without two codebases and a review queue. What a PWA storefront genuinely delivers in 2026, where the service worker earns its place and where it quietly lies to your customers, the iOS caveats that decide your push reach, and the parts that still need a real native app.
Visitors who use search buy at several times the rate of visitors who browse — which makes the search box a conversion feature, not a technical checkbox. When the database you already run is enough, when typo tolerance pays for itself, and the sync problem that is the real project either way.
Next.js will happily serve your JS bundles from a CDN with one config line. We stopped doing that. Hashed chunks belong to the build that emitted them; images outlive every deploy — and treating both as 'assets' is how a rollback turns into a cache-purge incident.
Prefetch-everything wastes bandwidth, prefetch-on-hover fires too late, and neither exists on a phone. Cursor trajectory, tab distance and scroll direction are better signals — and this site already runs them.
LCP, INP and CLS are graded on real visitors at the 75th percentile, not on your MacBook with a Lighthouse tab open. What actually moves each metric on content and commerce sites, ranked by effort.
This site renders once at build time and serves from memory. SSG, ISR, and the short list of things that genuinely need a request-time server — most marketing pages aren't on it.
Before a two-developer project grows a Redis, a RabbitMQ and an Elasticsearch, look at what the database you already run can do. SKIP LOCKED queues, tsvector search, LISTEN/NOTIFY — and the measured signals that tell you when to graduate.
Your ERP answers in 800 ms and no amount of React tuning changes that. What does: not asking twice. The query-key, staleTime and invalidation patterns we use in front of Odoo.