Sarp Efe

Dev.
Founder of

[Sarp Efe @devsarp]

The mistake most operators make:

They install 2 plugins from the SAME category (WP Rocket + WP Super Cache — both page caches), and 0 from the category their bottleneck is actually in.

Full breakdown of all 8 categories:
https://t.co/r7im6q3zwv

[Sarp Efe @devsarp]

WordPress site slow?

Cold visitor → page cache
Logged-in dash → object cache
Big image → image optimiser
60 CSS files → script manager
600 MB DB → cleanup

"Speed plugin" isn't one category. It's 8.

🧵 below

[Sarp Efe @devsarp]

WordPress site behind Cloudflare:

Homepage: 80ms ✓
Product page: 90ms ✓
Checkout: 1,920ms ❌

Cache hit rate: 94%.
The 6% that misses is where customers pay.

Edge caching solved the easy half. The other half is its own problem.

https://t.co/uzD7AJ8U7B

[Sarp Efe @devsarp]

Built a WordPress plugin that picks which plugins run on which pages No caching layer

Tested on a vanilla install with Elementor + WC + Bookly + MailPoet + Jetpack all active. Wizard defaults only.

PSI mobile 5 runs median
LCP -31%
TBT 90 -> 0ms
SI -54%

https://t.co/orNmz0esFs

[Sarp Efe @devsarp]

@brucebiz2 @webjuice_ie WordPress needs more resources to be better, but it's simple to use.
Astro can be hosted at very low costs, it's powerful, but you need to know what you're doing.

In short, who wins depends on who you are and what you're going to use it for.

[Sarp Efe @devsarp]

@brucebiz2 @webjuice_ie If you want performance, choose Astro.
If you're not a developer and ease of use is what you're looking for, choose WordPress.
If you want to feel secure and do it without plugins, choose Astro.

[Sarp Efe @devsarp]

@noa_blog_ai By reading the logs, you can pinpoint exactly where the problem originated. Instead of building an additional system, it makes more sense to have your existing AI agent read the logs and identify the source of the problem.

[Sarp Efe @devsarp]

@camilovilla @webjuice_ie Because performance directly affects SEO score. NextJS + Nodejs has much more to offer than PHP in this regard.

[Sarp Efe @devsarp]

Ever Googled something random and landed on a US pharmacy site full of casino keywords?

That's not a glitch. That's the Cloaking Hack — and it's been running on thousands of legit websites for years.

Free 10-step defense guide

#WordPress #SEO

https://t.co/do33cl23me

[Sarp Efe @devsarp]

On a real multilingual store this week: 720 ms → 280 ms homepage
TTFB.

Five footguns the snippet fans never mention — cart-fragments
AJAX, block themes, translated checkout slugs, REST API, the 4am
cron — in the post:

https://t.co/3MRPNkKqcq

[Sarp Efe @devsarp]

Every WooCommerce performance post tells you to wp_dequeue_script
WC's CSS and JS on non-shop pages. Done.

It saves 50 KB and zero ms of TTFB. WC was booted before that
hook fired. And your cart-count badge silently breaks because you
just dequeued the script that fed it.

[Sarp Efe @devsarp]

Three different costs — boot, run, asset — and most blog posts
conflate them.

What actually works: skip WC entirely on cold pages, prune
subsystems on warm pages, dequeue assets last. In that order, the
wins compound. Reverse order, you ship a broken cart count.

[Sarp Efe @devsarp]

I hired a new developer today to help me.
#dev #saas #hiring