Fast WordPress pages, built before anyone asks
Staatic builds your WordPress pages when you publish. Visitors get the finished pages without waiting for WordPress or its database.
Our homepage: 42 ms to first byte instead of 221 ms.
WordPress took 5.3 times as long to send the first byte. We made 51 requests to each of these four pages on both versions, from a location in Amsterdam on 21 November 2026. The figures below are medians.
WordPress had no page cache in this test. A good cache can be fast too. See how caching compares.
In this test, even Staatic’s slowest response started sooner than WordPress’s fastest: 148 ms against 198 ms. Each dot below is one request.
- WordPress, no page cache
- Staatic
- Median
/
WordPress / Staatic: 5.3×
/pricing/
WordPress / Staatic: 10.8×
/security/
WordPress / Staatic: 5.2×
/documentation/setup/
WordPress / Staatic: 5.5×
Staatic cuts the wait for WordPress. Your theme sets the rest.
WordPress has already built the page before your visitor arrives. Staatic sends the finished copy, so the browser can get started sooner.
A large image or a heavy script can still slow things down. Your theme and the visitor’s device affect how quickly the rest of the page loads.
When you publish
WordPress builds the page
Staatic saves the finished HTML.
Still loaded by the browser
- Images
- Fonts
- Scripts
The browser still has to render the page and run its scripts.
A good page cache is fast too. The difference is the miss.
A cached WordPress page can respond quickly, as Cloudflare’s tests show. On a miss, your host may try another cache or ask WordPress to build the page. Staatic retrieves the file you published, whether WordPress is running or not.
A popular page, already cached
Staatic
Served without PHP: Published file, already cached
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: Built by PHP every time
- With a page cache on the server
- Works, with a catch: Cached copy from your one server
- Host with an edge cache
- Served without PHP: Cached copy from an edge location
A post from two years ago
Staatic
Served without PHP: Published file from cache or storage. No PHP.
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: Built by PHP
- With a page cache on the server
- PHP runs, or the page fails: Built by PHP once the copy expires (WP Engine: 10 minutes)
- Host with an edge cache
- Works, with a catch: Fetched from the origin once the edge copy expires (Kinsta: 24 hours)
Right after you publish or purge
Staatic
Served without PHP: Finished before going live. A first request comes from storage, not PHP.
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: Built by PHP
- With a page cache on the server
- PHP runs, or the page fails: “Slower for a period of time” until pages are cached again. WP Engine
- Host with an edge cache
- Works, with a catch: Fetches a fresh copy from your server when a visitor asks for it
Bots and odd URLs, many at once
Staatic
Served without PHP: Misses reach storage, not WordPress
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: All reach PHP and the database
- With a page cache on the server
- PHP runs, or the page fails: Misses reach PHP
- Host with an edge cache
- Works, with a catch: Uncached requests reach your origin
WordPress or its database is down
Staatic
Served without PHP: Every published page
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: Site down
- With a page cache on the server
- Works, with a catch: Cached pages, while your server can still serve them
- Host with an edge cache
- Works, with a catch: Cached pages, if your host keeps serving them during an outage. Always Online may help if your server can’t be reached.
Logged in, cart or checkout
Staatic
PHP runs, or the page fails: Runs elsewhere, such as a shop on a subdomain or Snipcart. See what works on static
Other setups
- WordPress, no page cache
- PHP runs, or the page fails: Built by PHP
- With a page cache on the server
- PHP runs, or the page fails: Skips the cache
- Host with an edge cache
- PHP runs, or the page fails: Skips the cache
This table describes how pages are served, not a speed test of each host. How long cached pages last, and whether they stay available during an outage, depends on your host and settings.
Fast on an ordinary day. Still up on a bad one.
Visitors get the files you published, not pages from WordPress, so those pages keep loading whatever happens to WordPress afterwards.
On a WordPress site without a separate cache, these two lines are the same line. A scheduled publication that runs while WordPress is broken publishes the broken state.
The public site also keeps serving while you change the PHP version, restore a backup or import a site, and while WordPress is paused after 15 idle minutes without the always-on add-on. Visitors get the version you last published until you publish again. Only a path you forward to WordPress with origin rules depends on it.
Not a backup copy of popular pages
Cache features sold as “always online” serve only what they kept, and only when your server can’t be reached. Cloudflare’s Always Online doesn’t step in when WordPress answers with an error. On Staatic the published files are the site, a two-year-old post included.
What the public site does depend on
Amazon Web Services (CloudFront and S3), your domain’s DNS, and Staatic’s form and search services if you use them. A forwarded path depends on where it goes. Your WordPress, its plugins and its database are not on the list.
Check it from where you are
Response headers say where a page came from. Here are both answers for our homepage, explained.
HTTP/2 200x-powered-by: PHPPHP ran to build this answer.cf-cache-status: DYNAMICNot cached by Cloudflare: WordPress built it for this request.server: cloudflare
HTTP/2 200server: staaticA finished file. No PHP ran.x-cache: Hit from cloudfrontCloudFront already had the page and sent it straight away.x-amz-cf-pop: AMS58-P6The CloudFront location that answered: Amsterdam.
Shortened to the lines that matter, PHP version left out.
In your browser
Open your browser’s developer tools, choose Network and reload. Timing shows how long the server took before it answered.
/
WordPress, no page cache
status 200
document
waiting for the first byte: 221 ms
/
Published by Staatic
status 200
document
waiting for the first byte: 42 ms
Run it yourself
Paste these into a terminal: the first shows the headers, the second times one request. Your CloudFront location and times will differ from ours.
$ curl -sI --compressed \ https://staatic.com/ HTTP/2 200 server: staatic x-cache: Hit from cloudfront x-amz-cf-pop: AMS58-P6 (other headers left out) $ curl -so /dev/null --compressed \ -w '%{time_starttransfer}\n' \ https://staatic.com/ 0.041897 # one run; the median of 51 was 0.042
What Staatic doesn’t change
- A heavy theme
- Large images, fonts and scripts can still slow a page down. Staatic saves the wait for WordPress to build the page; your theme still needs to be kept lean.
- Changes go live when you publish
- Saving in WordPress doesn’t change the public site; publishing does. Quick and scheduled publications (Staatic Premium and Staatic Cloud) keep the delay short.
Staatic Cloud serves your site from 250+ locations (400+ on Enterprise). Our measurements were answered by one of them, in Amsterdam; yours will use the nearest. Self-hosting the plugin? Then speed depends on where you publish.
Publish once.
Every page is ready.
See the difference on your own site. Import a copy into a free 14-day Staatic Cloud trial. Your live site stays as it is until you’re ready to switch.
- No payment details needed
- The trial ends automatically
- You keep editing in WordPress
How we measured
Show how we measured Hide how we measured
We measured on 21 November 2026 from a location in Amsterdam, between 06:30 and 06:39 CET. WordPress was awake, with no page cache. After one warm-up request per page on each side, we ran 51 rounds. Each round requested every page once from WordPress and once from Staatic, in a shuffled order, to reduce the effect of changing network conditions. Each request used a fresh connection. Every first-byte figure is the median of all 51 requests; no round was picked. Every Staatic request was a CloudFront cache hit.
We used curl’s time_starttransfer, which includes DNS lookup, connection setup, TLS and the wait for the response. It does not measure PHP execution alone, full-page load time or real visitors’ Core Web Vitals. These results come from one location, not a global average. Availability statements follow the Staatic Cloud documentation.
WordPress: Responses included cf-cache-status: DYNAMIC: Cloudflare passed every request on to our WordPress. Staatic: Answers carried x-cache: Hit from cloudfront and the same 24,631 bytes every time, over HTTP/2.