I help businesses speed up and scale WordPress and pass core web vitals.
Get it here 👉
Joined March 2009
- Tweets757
- Following171
- Followers1.9K
- Likes1.1K
good
WordPress’s attempt to trademark “Hosted WordPress” and “Managed WordPress” has been denied by the US Patent and Trademark Office
theregister.com/2025/02/13/w…
Hey @dannypostma, how do I contact you for the seo course issue? Sent several emails to [email protected] but never got a response.
Rahul Nagare retweeted
"That's the deal. That's open source. I give you a gift of code, you accept the terms of the license. There cannot be a second set of shadow obligations that might suddenly apply, if you strike it rich using the software. Then the license is meaningless." world.hey.com/dhh/automattic…
Rahul Nagare retweeted
I recently rewrote our marketing site from NextJS to Rails, and it’s soooo nice! Enjoy this peek behind the curtain. 😁
youtu.be/blzd9MEyzcA
It's only called founder mode if it comes from the Bay region of California. Otherwise it's just sparkling hustle.
Rahul Nagare retweeted
There are few decisions that I can look back on and say it truly changed the trajectory of Castos, but joining @tinyseedfund is definitely one of them.
Folks think: oh cool, raise some money.
But honestly, the money is nowhere near the best part.
What's really impactful is surrounding yourself with like-minded, growth-focused founders, mentors, and peers who are all trying to do the same thing as you.
The old "you are the sum of the 5 people you spend the most time with", but roided out like The Rock.
There are like 150 founders in TinySeed now, and in that Slack group there are hundreds of years of experience. Literally, no question that someone doesn't have first-hand experience navigating.
And that doesn't count @robwalling , @einarvollset , @tracymakes and the dozens of mentors in the program. All of whom are insanely talented and bring so much to the table...and are all rooting for you.
I made the decision to join TinySeed because I was serious about scaling Castos, and wanted every advantage I could get in the process. And it's paid off massively.
If you're a bootstrapped founder and want to accelerate your SaaS growth, I'd seriously consider applying. tinyseed.com/latest/applicat…
I gave up hoping that you'd fix it after 72+ Hours and recreated everything on AWS. Feel free to close my ticket, so your team can go be useless elsewhere. @linode
If no one is working on this over the weekend then why is your support saying "We've escalated this to even higher teams" every time I ask for an update? @linode
Rahul Nagare retweeted
🚨 It’s Annual Planning season.
And I’m giving away all my custom templates.
They’ve helped me:
+ Grow and sell @ampush for 8-figs
+ Build up a $1B venture studio
+ Scale scores of startups as an angel
RT + Reply with the word BOOTSTRAP…and I'll send them your way.
And Bard is shut down, soon to be replaced with a new chat service.
Most pagespeed optimization advice on the internet is garbage.
Some of it actually makes your core web vitals worse.
You get far better pagespeed score by focusing on these 3 things.
1. Javascript
2. Images
3. CSS
Once you go from a failing score to 'Needs Improvement' you can afford the luxury of minifying scripts and updating htaccess files.
I've spent over 5.4 million dollars on AWS.
But I wouldn't recommend AWS to someone looking for hosting suggestions.
Here's why:
There is a common misconception that hosting WordPress on AWS makes it scalable automatically.
Every online WordPress community I visit has a fair number of posts asking about solutions for a growing site.
10 out of 10 times, these posts have a suggestion that says, “If you need scalable infrastructure, AWS is the only option.”
Suggestions like this lead to a scenario we often see when onboarding new customers at Nestify. It goes something like this:
The site starts to grow and runs into scaling troubles. Developers suggest a CDN.
When the site still has issues, management decides to move the site to AWS.
At this point, either the IT dept., or the agency managing WordPress launches a new EC2 instance.
Since AWS recommends using Bitnami’s WordPress AMIs, most people go with that.
Using them in production doesn’t provide any of the scalability or high-availability features that AWS offers.
Afterall, all these images can do is to manage software INSIDE the instances.
Simply put, users trade their bare-metal servers and VPSs in favor of EC2 VMs and are no better off than before.
And now, they also need to have a plan for backups, security, and staging sites (Most AMIs only support one WordPress install).
Here's what I recommend instead:
Unless you have data residency or compliance requirements, pick a managed WordPress host and let them handle everything.
If that's not an option, keep your stack simple.
Let CDN cache aggressively and serve most of your traffic.
Lock down wp-admin access to specific IPs.
If possible, lock down the filesystem as well.
By adding these 3 measures you'll eliminate 90% of common WordPress threats.
Every creative/SEO/ppc agency has mindvalley logo on their site. Is it part of some default template or do they really churn through a lot of agencies?
