The only time the request needs to hit the origin is if nobody fetched the page.
The only time the request needs to hit the origin is if nobody fetched the page.
To speed it up further, you can tell Cloudflare to cache your HTML pages. Now you've eliminated that round-the-world trip (for most visitors), but you've also lost some of the dynamicness of your site. At that point, you're basically building a static site by different means.
In the confidence it caches the HTML, and the plugin triggers a CDN purge when the HTML changes
Coupled with Cloudflare's standards support (TLS 1.2, H2, H3), and their image optimisation services it's really great for performance.
Just got to remember to disable many of the WP 'speed optimisation' plugins that may be installed as they actually can cause more speed issues.
But probably not against a static page.
Wordpress is still PHP and a Database and whatever crazy plugins, templates and front end builders are involved.
Depending on how much JAM you have in your STACK, your site/app may or may perform better than WP.
I build a ton of sites in Jekyll, which are static sites and not JAMSTACK. The two get conflated.