Alex | Web Perf

Tinkering with server response times and WooCommerce infra.
Building free tools for store owners.

[Alex | Web Perf @AlexVibeCode]

@leoobai @rankmathseo Moving it from 'tech debt' to 'conversion risk' is the exact mindset shift store owners need. And breaking down the $ impact by route (cart vs checkout) is a brilliant angle—that is going straight onto the roadmap. I'll shoot you a DM the second the first iteration is live

[Alex | Web Perf @AlexVibeCode]

@WPSecurityNinja Exactly. Tuning the engine doesn't matter if you're letting malicious bots tow heavy cargo in the background. Edge protection filtering out the noise is the ultimate performance hack before you even touch the origin server configs

[Alex | Web Perf @AlexVibeCode]

@Nubufly @recursoswebyseo Tal cual. Y lo peor es que el cliente culpa al desarrollador cuando la tienda va lenta, no al servidor barato de $3. ¡Gracias por el follow! Seguimos compartiendo sobre rendimiento.

[Alex | Web Perf @AlexVibeCode]

@leoobai @rankmathseo Exactly. Treating origin TTFB as a raw revenue metric completely changes the conversation with clients. I'm finalizing the MVP for the detector right now—would love to get your eyes on it when it's ready. Keep building great things on your end

[Alex | Web Perf @AlexVibeCode]

@akolo1 @zynoo_official 217ms TTFB is a solid baseline, and proactive support adding LiteSpeed + Redis is rare for most hosts. Did you happen to run a load test bypassing the cache to see how the raw PHP workers handle dynamic routes like WooCommerce checkout? That's always the real test

[Alex | Web Perf @AlexVibeCode]

@Ishandw40709593 A 3.4s drop is huge. But since most free audits just pull a synthetic Lighthouse report, how are you diagnosing the actual server-side TTFB bottlenecks? On heavy sites like WooCommerce, that 4.2s delay is almost always a database issue that edge caching can't hide

[Alex | Web Perf @AlexVibeCode]

@Nubufly @recursoswebyseo 100% de acuerdo. De nada sirve minificar el CSS o usar WebP si el hosting compartido tarda 2 segundos en responder. El TTFB es el techo invisible del rendimiento. Montar un frontend optimizado en un servidor saturado es tirar todo ese trabajo a la basura.

[Alex | Web Perf @AlexVibeCode]

@leoobai @rankmathseo 100%. Unindexed DB queries and transient bloat on cart pages are the real silent killers. It’s exactly why I'm building a TTFB revenue leak detector for Woo—to visualize that origin lag. The 'just install an edge cache' crowd rarely looks that deep into the server stack

[Alex | Web Perf @AlexVibeCode]

@nekasahed Calculating pm.max_children based on available RAM is where most DIY setups completely break. Under-allocate and you get 502 Bad Gateway errors under load; over-allocate and the Linux OOM killer drops your database. Getting this math right is what actually unlocks the VPS

[Alex | Web Perf @AlexVibeCode]

@davidawiebe The classic shared hosting trap. It’s wild how that same bottleneck still kills indie creators today. The moment a self-hosted audio stream or merch drop gets traction, budget hosts throttle the CPU or suspend the account. Bandwidth & server scale shouldn't punish success

[Alex | Web Perf @AlexVibeCode]

@leoobai @rankmathseo Spot on. Everyone obsesses over LCP and JS execution, but TTFB is the invisible ceiling. Shared hosts try to mask it with aggressive edge caching, but the second a user hits a dynamic route—like a WooCommerce checkout—that server bloat kills the conversion

[Alex | Web Perf @AlexVibeCode]

@imtiahmed01 @ardent__dev Cloudflare is the ultimate cheat code for domains. Zero-markup renewals and enterprise DNS is a massive upgrade. Spaceship is a great UI pivot from Namecheap, but CF is still king. Since Cloudflare only handles DNS, where are you actually routing the traffic to for hosting

[Alex | Web Perf @AlexVibeCode]

@mikeunplugged Cloudflare's zero-markup pricing is the ultimate cheat code. That $500 stings now, but escaping GoDaddy's renewal spikes pays for itself fast. With your DNS safely at Cloudflare, where are you actually routing the traffic? Still using GoDaddy for the hosting stack

[Alex | Web Perf @AlexVibeCode]

@ZSchneider76107 @savvysaleslady @GoDaddy @Namecheap 100%. Vendor lock-in is exactly how GoDaddy holds businesses hostage when their bots misfire. A clean split means a host can never take your domain down with them. @savvysaleslady, hoping that Namecheap transfer clears fast so you can get back to selling

[Alex | Web Perf @AlexVibeCode]

@Glutton4Pnshmnt Slaying the clankers is a noble quest. Honestly, I'm just impressed you actually managed to bypass the bot wall and find a real human at GoDaddy. What was the actual issue that forced you into the AI maze in the first place? Just domains, or is your hosting trapped there

[Alex | Web Perf @AlexVibeCode]

@TheUrbanMonk321 @GoDaddy Hiding basic subdomain DNS behind a broken AI chatbot just to fire support staff is peak corporate greed. Real indies need a clean control panel, not a 'smart' assistant. After 25 years, are your actual game servers trapped there too, or just the domain registrations

[Alex | Web Perf @AlexVibeCode]

@learnwithmattc WP CLI + SSH? Okay, I'll admit that is actually impressive. Giving an LLM autonomous execution rights at GoDaddy's scale is a massive engineering feat (and slightly terrifying). Firing up the episode now—thanks for the context, Matt

[Alex | Web Perf @AlexVibeCode]

@DomainDanHQ @requestprice @afternic That disconnect kills so much impulse-buy liquidity for ccTLDs. If the exact match doesn't show up in GoDaddy's retail search, you lose the end user. The problem is ARNES (.si) accreditation is a bureaucratic nightmare, so GoDaddy won't rush it without massive retail demand.