WordPress CDN

Make WordPress load instantly — without a plugin

Full-page caching at the edge turns a slow WordPress site fast in an afternoon. Nothing is installed, nothing conflicts with your theme, and wp-admin and your logged-in users still get a live page every time.

Start free Test your site first

The problem

WordPress rebuilds every page for every visitor

Someone requests your about page. PHP boots, the database is queried a few dozen times, twenty-three plugins fire their hooks, the theme renders — all to produce a page that has not changed since March. Then the next visitor arrives and it all happens again.

Your hosting is not necessarily slow. It is just being asked to do the same work thousands of times.

The preset

The hard part is knowing what not to cache

Caching WordPress is easy. Caching WordPress without serving a logged-in editor's admin bar to the public, or showing a stale page to someone who just commented, is where it usually goes wrong. Pick the WordPress preset and these rules are already in place.

Cached at the edge

Identical for everyone, so there is no reason to build it twice.

The homepage
Posts and pages
Category, tag and author archives
Search result pages
The RSS feed
Images, CSS and JavaScript

Always live from your origin

Personal or stateful, so it is passed straight through, uncached.

/wp-admin and wp-login.php
Anyone with a wordpress_logged_in cookie
The REST API at /wp-json
wp-cron.php and xmlrpc.php
Recent commenters, by cookie
Any path you add yourself

// what "pick the WordPress preset" actually configures for you

bypass_cookies:

wordpress_logged_in_* wordpress_sec_* wp-* comment_author_*

bypass_paths:

/wp-admin/* /wp-login.php /wp-cron.php /xmlrpc.php /wp-json/*

// everything else → cached at the edge, served in ~15 ms

You can add your own bypass rules on top — a membership plugin's endpoint, a custom login path, a form handler. The preset is a sensible starting point, not a locked box.

The result

From seconds to milliseconds

Uncached PHP

800 ms+ to first byte

Cached at edge

~15 ms

95%+

of page views served from cache on a typical content site

no plugin

nothing installed, nothing to conflict

WebP

media-library images converted and resized

stays up

cached pages keep serving if the origin falls over

The other benefit people notice second: with 95% of traffic never reaching your server, that server suddenly has plenty of capacity. Plenty of sites downgrade their hosting after switching, which pays for the CDN several times over.

What you get

Everything handled at the edge

This is the list of plugins you no longer need, phrased as features.

One-click WordPress preset

Cache and bypass rules for wp-admin, logged-in users, commenters and the REST API — configured for you, editable afterwards.

Image optimisation

Automatic WebP conversion and on-the-fly resizing for those heavy media-library photos, with no thumbnail regeneration.

Brotli and minification

CSS and JavaScript compressed and minified on the way out. No build step, no concatenation plugin.

Firewall and bot blocking

Country and IP rules, proof-of-work challenges, and automatic blocking of the endless /wp-login.php and xmlrpc.php probing.

Your domain, with SSL

Bring your own domain; the certificate is issued and renewed automatically.

Instant purge

Purge a path, a tag or the whole zone from the dashboard or the API — or let the optional plugin do it when you publish.

Waiting room

For the day a post takes off, queue the overflow instead of letting the site fall over.

Real analytics

Traffic, cache hit ratio, geography and per-request log search — without adding a tracking script to your pages.

Getting started

Four steps, none of them in WordPress

You never log in to wp-admin during this. Nothing is installed, nothing is activated, and every step before the last one is invisible to the public.

Create a Site Accelerator pointing at your site
Your existing hosting stays exactly where it is. We pull from it, the way a visitor would.
Pick the WordPress preset
Cache TTL, bypass cookies and bypass paths configured in one click. Adjust anything you want afterwards.
Test on the temporary hostname
Every zone gets a working hostname immediately. Browse the site, log in, publish a draft, check the admin bar — all before any public DNS changes.
Point your DNS at us
Move the record, let the certificate issue, and you are live. If anything looks wrong, point it back — the change is one record either way.

FAQ

Questions, answered

No, and that is the point. NordicCDN works at the edge, on the HTML your site has already produced, so there is nothing to install in WordPress. No plugin conflicts, no extra PHP running on every request, no update to break your site on a Tuesday morning.

No. The WordPress preset bypasses the cache for /wp-admin, wp-login.php, the REST API and anyone carrying a WordPress login cookie. Editors and members always get a live page; anonymous visitors get the fast cached one. Both happen automatically.

Yes. Caching happens on the finished HTML, so it is theme- and builder-agnostic. Elementor, Gutenberg, Divi, a custom theme from 2015 — the edge does not know or care which produced the page.

You can keep it or remove it. Two caches in a row work but make debugging confusing, so most people switch the plugin to a simple object cache, or turn it off entirely and let the edge do the page caching. Either way, test on the temporary hostname before you change anything public.

Content is cached for a TTL you set, and you can purge instantly from the dashboard or the API. Our optional WordPress plugin automates it — publish or update a post and the relevant pages are purged for you. The plugin is a convenience, not a requirement.

WooCommerce has its own preset which additionally bypasses cart, checkout, my-account and the add-to-cart AJAX endpoints. See our WooCommerce CDN page.

Almost always. Cached HTML removes most of the time-to-first-byte, which directly improves Largest Contentful Paint, and edge image optimisation handles the other half of the problem. Those two together are what usually moves a WordPress site from red to green.

Minutes. Create a zone pointing at your site, pick the WordPress preset, test it on the temporary hostname, then move your DNS record and let the certificate issue.

Anonymous visitors keep getting cached pages from the edge while your origin is unreachable, so the site stays up and readable. You cannot log in or publish until the origin is back, but your visitors and Google do not see an error page.

Speed up your WordPress site

Start free in two minutes — 25 GB free every month, no card required.

Start free