Skip to content
Proactive security updates

Performance & shop operations

Speed is not a one-off project: it erodes as assortments grow, extensions accumulate and media are uploaded unchecked. This category treats performance as part of maintenance — regular field and lab measurements, watching response times under load, caching for category, search and detail pages, database indexes and slow queries, image sizes and formats, and clearing out extensions nobody uses any more. Added to this are further operational topics that decide reliability in daily business: the deliverability of order and shipping emails, the division of tasks in the team and documented procedures. Every measure described comes with measurement, so regressions are noticed early. We additionally show how to keep measurements comparable over months so that changes do not stem from differing test conditions.

Third-party outage: the shop keeps taking ordersInventory to blast radius to degraded mode: absorb an external failure instead of losing the order1. Dependency inventoryPayment providerCheckout step 4criticalShipping rate APIPrice in the cartcriticalDNS and CDNDelivery of every pagecriticalReview widgetProduct page, lower partcosmeticFont hostRendering, externalcosmeticCriticality decides the blast radius2. Blast radius in the funnelProduct pageOK 210 msCartOK 340 msShipping ratesTimeout after 800 msPayment choiceFallback method liveOrder completionOrder capturedResult: orders possible, partial functionFlat shipping fallback instead of a lost sale3. Degraded mode activeFallback paymentInvoice and prepayment openShipping cost fallbackFlat rate per zoneWidget hiddenReviews load laterNotice in checkoutCustomer sees the partial outageAlert to the on-call teamStatus feed and error rate per endpointResponse time per maintenance contract2/3of outagesthird parties (Uptime Institute)54 %of operators: latest severeoutage above 100,000 US dollars(Uptime Institute)90 %of mid-size and large firms:over 300,000 USD per hour down(ITIC)77 %of reported incidents in the EUwere DDoS attacks(ENISA)

Third-Party Outages: Keep the Shop Able to Take Orders

When a payment provider, shipping API or CDN fails, the shop must keep taking orders: inventory, blast radius, degraded mode and alerts for external services.

13 min read
Maintenance Window: Update Without Revenue LossLow-traffic slot as maintenance window03-05hDeploy in the revenue trough = minimal lossCorrect maintenance mode503SEO-safe, ranking preserved200Soft 404, ranking dropsRetry-After: 600 signals the return503 max. 1-2 days (Google Search Central)Sequence inside the window1Plan windowLow-traffic 03-05h2Enable 503Retry-After: 6003Update + migrationComposer, plugins4Smoke testVerify checkout5Cache warmupPrewarm sitemap6503 off, liveReady to sellRollback plan: back in minutesGit tag before deployDB dump before migrationRollback in minutes

Maintenance Windows: Shop Updates Without Downtime

Shop updates without revenue loss: a low-traffic maintenance window, an SEO-safe HTTP 503 mode, cache warmup and a rollback plan with Git tag and DB dump.

13 min read
DMARC 2026: Reliable Email Delivery for ShopsFrom monitoring to enforcement - so transactional mail reaches the inboxThree building blocks in DNSSPFauthorized sending servers (DNS TXT record)DKIMcryptographic signature per messageDMARCties SPF and DKIM together via alignment (DMARC.org)The DMARC rollout pathAggregate reports (rua) reveal every sending sourcep=nonemonitorp=quarantinespam folderp=rejectblockWithout clean authenticationSPF, DKIM or DMARC fail - messages getrejected or sorted into the spam folderOrder and shipping mails are lostWith SPF + DKIM + DMARCAuthentication passes and alignment matches -transactional mail reaches the inboxDeliverability stays stable5,000 per daybulk-sender threshold (Google)0.30%max. spam rate at Gmail (Google)Feb 2024Gmail/Yahoo enforcement (Google)May 2025Outlook enforcement (Microsoft)

DMARC 2026: Reliable Email Delivery for Online Shops

Bulk-sender rules from Google, Yahoo and Microsoft: SPF, DKIM and DMARC decide the delivery of shop mails - and how to raise DMARC safely to p=reject.

13 min read
Load Testing for Peak Traffic: Scale Before Sales DaysResponse time under rising loadResponse timeBufferNormal loadExpected peakBreaking pointHeadroom above the peak3xCapacity for3x normal loadtested aheadScaling planPrewarm cache layerAutoscaling thresholdsKnow the breaking pointLoad-test plan: 6 to 8 weeks before the event-8 wkPlan capacity-6 wkRun load test-4 wkFix + retest-1 wkDress rehearsalEventHold the peakAfter the peak: scale downScale back downNormalize costUpdate baseline

Load Testing for Peak Traffic: Scale Before Sales Days

Black Friday and sales peaks bring a multiple of normal load. Plan load testing 6 to 8 weeks ahead: realistic scenarios with buffer, breaking point and scaling.

12 min read