I’ve built a bunch of Jamstack sites in the last 2 years, ranging from 3 – 500+ pages, and I agree with all points above.

Try telling your clients this:
– You now need an account & pay for at least 3 different services, one for Github, one for a headless CMS, one for Netlify
– You can not preview your site while you’re editting it. Wait, you can, if you use Gatsby Preview — but it’s another $20/month if you want 250 ‘real time edit’ per month — that’s right. I’ve probably editted 50 times writing this comment. But wait — can’t you just deploy your own Gatsby real time edit? It’s open-sourced, after all? Yep! Now you need to pay for a droplet & extra developer resource to maintain it, just so you can preview your site while you’re editting it… on a separate tab.
– Commenting is another service. You want the comment to be baked into the html? Either spend more developer resource, or you have to pick a service that allows that (not many). Either way, more developer resource.
– You want to optimize your images? Too many images will slow down your build beyond belief. Caching helps, but occasionally you’d need to clear your cache due to vague error… You know what, let’s put all our images in a bucket and put imgix in front of it. Another 2 services.
– This one is Gatsby-specific: You just want a website that you can edit, but I spend a lot of time wrestling with Gatsby’s GraphQL to bring your data to a template I wrote in React, a framework choice that is totally overkill since 90% of your site is just static HTML, but I just can’t write anything in vanilla JS/HTML anymore.

Things that make a static site fast also make a server-rendered site fast. Throw a CDN in front of a wordpress-powered site, pair it with a web worker for pre-caching stuff and it can be really fast.

At this point, I’m convinced people who uses JAMStack are either companies with strong dev teams that willing to shoulder the marketing responsibility, or hobby developers feel so great after rewriting their simple blog for the fifth time in a new technology.