Helping ecom to optimise - dev costs - infrastructure performance - automate processes 20000+ hours in ecom projects. 14y in management. Owner@ https://xitter.gq/t.co/1NNMaWH12W
Dnipro
Joined January 2009
- Tweets2.5K
- Following287
- Followers525
- Likes1.5K
Pinned Tweet
Lots of ecom stores struggle with infrastructure when scaling past 7 figures
I've been consulting 8-figures stores for 14+ years on how to optimize the tech infrastructure and operations
Here are the top 5 things you need to have to run smoothly at 7-figure and beyond
What an online store can put on it today, and why the free plan won't do: wpwp.bz/spacefast-automattic…
Automattic's Spacefast is WordPress you never see.
Tell Claude "publish this" and get a live link: database, logins, uploads, email and spam checks built in. No account to start.
Matt says he'd like to host Lovable's apps for less than they pay now.
xitter.gq/photomatt/status/21028…
We had a soft launch of @SpacefastHQ yesterday before our board meeting, @batuhan (and now a team!) have been cooking what I think is the future of @WordPress and AI. You don't have to know or think WordPress, but this leverages wp.cloud to give you a Real Database, auth, uploads, email, @akismet / @automattic spam protection, and soon stats.
The architecture is amazing I'd actually love to talk to @Lovable et al see if we can host things for them for less than they spend now.
Datacenter space and components are getting pricey... So we might have to limit signups to prioritize our @WordPressVIP customers but get in while you can!
Which themes and servers are affected, and a five-minute check for your store: wpwp.bz/wordpress-7-1-2-secu…
WordPress 7.1.2 fixes a critical flaw, 9.2 out of 10: no login needed, and on some themes and servers it ends in running code on your server.
If your store has automatic updates off, and many do, it hasn't updated itself. Check Dashboard → Updates today.
xitter.gq/prashant_baldha/status…
🚨 WordPress 7.1.2 is now available as a security release.
The update addresses the security vulnerability (github.com/WordPress/wordpre…).
🔗wordpress.org/news/2026/09/w…
#WordPress #WP @WordPress #Release #Security
8/ 8–10. Update in October on staging, then freeze on 20 Nov. Rollback plan on one page. Name who is on call Fri–Mon. Full checklist, with the ten-minute version of every point: wpwp.bz/woocommerce-black-fr…
7/ 6–7. Open WooCommerce → Status → Scheduled Actions before the peak, not during it. And compare yesterday's orders with GA4 and Meta: if they don't match now, they won't match on Black Friday.
6/ 5. Checkout waits for shipping rates, tax, fraud checks, the gateway and often the ERP — inside the request the shopper is staring at. Pay for one real order on a phone, 3-D Secure included, and count the seconds.
5/ 4. Ask your host in writing: how many PHP workers, how many database connections, can you add capacity for 27–30 Nov. When every worker is busy the queue becomes timeouts, 502s and 504s.
4/ 3. Your cache stops at "add to cart". Session cookies make most page caches step aside, so the shopper who is buying gets pages built by PHP and the database. Fast for browsers, slow for buyers.
3/ 2. Don't load-test your homepage — it is cached and fast. Test category → product → add to cart → checkout on a staging copy, at 3× and 5× your peak. Watch p95 and the error rate, not averages.
2/ 1. Write down last year's peak: orders and visitors in the busiest hour. For stores that email and advertise it is usually 3–5× a normal day. A load test "at 1,000 users" means nothing if your real peak is 150.
1/ Black Friday is 27 Nov. For a WooCommerce store the deadline that matters is 16 October — fixes need two weeks to settle. The 10 checks we run on every store we get ready 🧵
