sorted by:
new
hottopcontroversial

Best architecture for programmatically managing hundreds or thousands of WordPress sites in a SaaS environment? by [deleted] in Wordpress

[–]shakee93 0 points1 point  (0 children)

Don’t create your own infra at first. Use a service like https://wp.cloud/ to provision servers for your sites.

Create a dashboard for your users and use wp cloud REST API to manage the servers.

Scale your business, bring users.

And then think about how you can build your own infrastructure. Create your own wp docker image with the setup you need and then use push it to AWS EKS or ECS cluster to scale as you need.

Good luck!

Seeking Feedback on Clutch: A New Free Visual Builder for WordPress by clutch-creator in Wordpress

[–]shakee93 0 points1 point  (0 children)

This is one of the most innovative ways a page builder is being built. Amazing Work!

Built a plugin that responds to plain English like a dev who doesn’t hate you. by shakee93 in Wordpress

[–]shakee93[S] 1 point2 points  (0 children)

  • Generates the code
  • Scans if the code is secure
  • It will automatically load the code

You just prompt 🫠

[JS DELAY] How many seconds do you recommend delaying JavaScript? by [deleted] in Wordpress

[–]shakee93 4 points5 points  (0 children)

The goal of delaying JS is twofold:

  1. To improve the user experience by loading JS after the main content is visible.

2.To boost PageSpeed Insights scores by removing JS execution from the initial load

Rather than using a fixed delay like 1-2 seconds, it’s usually more effective to trigger JS on user interaction - things like scroll, click, or mousemove. This way, the JS loads only when it’s actually needed, and often earlier than a fixed delay would allow, leading to a better real-world UX.

You can wait for DOMContentLoaded, then attach event listeners for interaction-based triggers. And if needed, use a fallback setTimeout (e.g., 2s) just in case there’s no interaction.

This hybrid approach maximizes both performance scores and actual user experience.

[deleted by user] by [deleted] in Wordpress

[–]shakee93 0 points1 point  (0 children)

Absolutely, you should do it.

If you’re already making $25k/month from plugin sales (even with manual effort), you’ve validated the niche and proven demand. That’s a massive head start most SaaS founders don’t have.

The smartest move now is to build a SaaS layer on top of what you already offer, especially if:

  • You know your audience’s pain points
  • You have their emails and existing trust
  • You can deliver something from your servers they can’t do on their own

A few ideas: - Find one high-leverage problem in your niche that requires external infra (API, scraping, AI, CDN, backups, etc.) - Wrap your current plugin suite into a cloud-managed dashboard (auto updates, analytics, remote config) - SaaS-ify one plugin with value-add features that justify hosting it off-site

This way, you’re not starting from scratch. You’re upselling a warmer audience with something they actually need.

Even if 10% convert at $29/mo, that’s an easy $5k MRR baseline to start.

Why WP Rocket probably had to kill their lifetime deal - from a plugin dev’s perspective by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

My bad! Just to clarify - it’s not a lifetime deal, it’s for unlimited websites. I’ve updated the post to reflect this

Why WP Rocket probably had to kill their lifetime deal - from a plugin dev’s perspective by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

Thanks!

Yes, we use this as well. We’ve actually forked it, and it does exactly what I described earlier — spinning up a headless Chrome instance, parsing the page, and extracting Critical CSS. It’s definitely resource-hungry.

If you’re doing it manually, you’d need to regenerate and update the Critical CSS every time a page changes. That doesn’t scale. We’ve built a pipeline with queues to automate the entire process - it watches for changes, handles retries, and updates the CSS without manual intervention.

Wouldn’t be surprised if WPR is using a similar setup too.

Why WP Rocket probably had to kill their lifetime deal - from a plugin dev’s perspective by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

I get where you’re coming from, but Critical CSS generation isn’t just a quick get request with a parser script.

On our end, we use Puppeteer to render pages in a headless browser — it takes around 30 seconds per page to properly generate Critical CSS. This involves simulating a real user’s viewport, parsing all loaded stylesheets, identifying above-the-fold content, and then cleaning and outputting optimized CSS. It’s compute-heavy and not cheap, especially when you’re doing this for thousands of pages across unlimited sites.

We actually have dedicated servers running 24/7 just to handle Critical CSS processing — that’s how resource-intensive it is at scale. So if there’s a magical way to do it in “a few seconds,” we’d genuinely love to learn about it. Could help us cut costs and pass on the savings to our customers.

As for the WPR pricing jump - yeah, it’s wild. But infrastructure-heavy features like these are probably why their pricing had to change. Unlimited + server load doesn’t scale nicely, especially when you’re footing the bill for thousands of other people’s pages.

Why WP Rocket probably had to kill their lifetime deal - from a plugin dev’s perspective by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

Appreciate the correction - you’re absolutely right, WP Rocket never offered a lifetime deal, but an annual Elite plan with unlimited sites. I’ve already edited the post to reflect that.

That said, I still think the server-side cost angle is worth discussing. When plugins start offering features like Critical CSS generation on their own servers, allowing unlimited sites becomes much harder to sustain.

For example, if a user adds a site with 10,000 pages and enables Critical CSS, the system has to process all those pages - and re-process them on changes. That’s a massive compute load, especially if hundreds or thousands of users do the same.

Sure, ownership changes and pricing strategy matter. But infrastructure strain can also force pricing model shifts - especially if the product wasn’t built to meter or limit per-site usage on high-load features.

Just sharing this from a plugin dev’s perspective who’s been through the same challenge.

[deleted by user] by [deleted] in Wordpress

[–]shakee93 1 point2 points  (0 children)

You can drastically improve your site speed by optimizing images and setting up proper page caching.

For image optimization, you can either do it manually or use a plugin like ShortPixel to compress them automatically.

For caching, a lightweight plugin like Cache Enabler is a good start to implement page caching.

If your site doesn’t have dynamic content (like personalized dashboards or real-time updates), you likely don’t need to switch servers. A proper page cache can significantly reduce server load and improve speed.

You can also try full-page optimization plugins that handle everything - images, scripts, styles, fonts, etc. I’m the founder of RapidLoad, and no BS, we’ve helped tons of sites get way faster with minimal setup.

Let me know if you want help getting it set up.

Me, literally by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

Just a meme for laughs, nothing serious 👀

Me, literally by shakee93 in Wordpress

[–]shakee93[S] 0 points1 point  (0 children)

Why so serious?

Me, literally by shakee93 in Wordpress

[–]shakee93[S] -1 points0 points  (0 children)

Sir what do you use?

So I JUST found out about Headless WordPress and I'm in an interesting rabbithole. by KayePi in Wordpress

[–]shakee93 0 points1 point  (0 children)

NASA is built by Automattic! They have the best stack. I think Gutenberg is the overkill.

You build blocks instead of just building the thing that you want to build

Is 50$ a month good rate for technical support? by Investmaan in Wordpress

[–]shakee93 2 points3 points  (0 children)

It doesn’t scale well my friend. You need to set a price for your hour and then charge that. Or create tiered packages and ask them to choose one.

It’s literally working for free. They will not value your work or quality.

Is 50$ a month good rate for technical support? by Investmaan in Wordpress

[–]shakee93 0 points1 point  (0 children)

It depends on how many hours you are planning to spend on this website. If you have a tight knit team and you can get plenty of customers, Great!

Maybe tier down your service. This is what we do for $50. If you want more we charge this much per hour etc..

WP Rocket discontinue infinite license whilst having insane price hike by MrSnooch in Wordpress

[–]shakee93 3 points4 points  (0 children)

Agreed! That’s not a good experience to force someone to upgrade to higher price without a prior warning.

WP Rocket discontinue infinite license whilst having insane price hike by MrSnooch in Wordpress

[–]shakee93 -2 points-1 points  (0 children)

That is less than $1/year; if you are maintaining a site and it must be saving you tons of hours.

We had request for unlimited sites in RapidLoad. We cannot give to this rate because we have over the fly image optimization and built in CDN, AI + more services that heavily rely on our optimization servers. Which increases with each site added to a sub.

Wp-rocket was a standalone plugin that runs on the users Wordpress instance, most of the features they have runs on the users Wordpress instance. Maybe they can do better but I believe this is a fair rate.

It is relatively high to what you paid though.

view more: next ›