MagicWP
Sign inGet Started
Performance

WordPress performance you can actually control.

Server-level page caching, Redis object caching, and flexible PHP tuning — straight from the dashboard. Serve cached pages faster, cut repeated database work, and keep your site responsive without managing servers yourself.

Get StartedRead the Docs
Full-page cache
nginx, server-level
Redis object cache
in-memory queries
PHP version
select per site
PHP limits
memory · uploads
Cache expiration
tunable freshness
One-click flush
from the dashboard
Benchmark

Cached pages, served in milliseconds.

When a page is cached, WordPress never loads and the database is never queried. Median time-to-first-byte on an identical WordPress install.

182ms
Median TTFB on a cache HIT — identical WordPress install, US-East.
Up to 4.6× faster than typical shared hosting
182ms
510ms
840ms
MagicWP
cache HITGeneric
VPSShared
host
Why it matters

Pages that load up to 4.6× faster.

Real, measurable speed once page cache, Redis, and PHP tuning are switched on — the gains your visitors and your business actually feel.

Greener Core Web Vitals

Faster LCP and INP lift real-user scores and search ranking signals.

Faster load times

Cached pages serve in milliseconds from the server, wherever visitors are.

Higher conversions

Every second shaved off load time cuts bounce and grows revenue.

What you get

Two areas you control: caching and PHP.

A fast site should not run PHP and query the database for every visitor. Use page cache for public pages, object cache for dynamic workloads, and PHP tuning when a site needs more.

Full-page nginx cache

Rendered HTML served at the server level

Redis object cache

Database queries held in memory

Cache flushing

Clear caches from the dashboard

Cache expiration

Configurable page-cache freshness

PHP version selection

Pick the runtime per site

PHP resource limits

Memory, upload, input, execution

PHP-FPM workers

Tune worker capacity per site

Optional extensions

ionCube Loader, SOAP, and more

How it works

Caching and PHP, explained.

Full-page caching

Instant delivery, no PHP required.

MagicWP stores fully rendered HTML at the server level. When a page is cached, visitors receive the finished page without WordPress loading, PHP running, or the database being queried — the biggest win for mostly-static sites.

  • Marketing websites
  • Landing pages
  • Blogs
  • Documentation pages
  • Brochure sites
  • Slow-changing content
Where the time goesper request
Cache hitHIT41ms
nginxserved instantly
Cache missMISS486ms
PHP bootMySQL queriesrender
nginx cachePHPMySQLrender
News / hourly10 min
Blog posts6 hours
Brochure7 days
Redis object cache

For dynamic sites that can't just be static.

Not every site is static. WooCommerce stores, membership sites, LMS platforms, and plugin-heavy websites run repeated database queries. Redis holds those queries and PHP objects in memory, reducing backend work on future requests.

  • Dynamic websites
  • Database-heavy plugins
  • Logged-in experiences
  • WooCommerce & membership
  • Expensive queries
  • Backend responsiveness
Repeated queries, resolvedavg latency
Database round-trips~24ms avg
get_options22ms
wc_product31ms
user_meta18ms
Served from Redis~1ms avg
get_options1ms
wc_product1ms
user_meta1ms
Stay in control

Flush cache when content changes.

Caching should make your site faster, not confusing. Flush caches when visitors need the latest version — from the dashboard or WP-CLI, page and object cache together.

  • After a theme update
  • After plugin updates
  • After publishing content
  • After layout changes
  • After a migration
  • After search & replace
magicwp — cache
wp theme update --all
→ 3 themes updated
wp cache flush
✓ object cache flushed
✓ page cache purged · 14 regions
Success: visitors now see the latest version.
PHP tuning

Tune PHP per site, from the dashboard.

Performance is not only about caching. Give demanding plugins more memory, larger uploads, longer execution, or a newer runtime — then test your theme and plugins after every change. No server administration required.

  • PHP version & timezone
  • Memory & upload limits
  • Execution & input time
  • PHP-FPM workers
  • Max input vars
  • ionCube, SOAP & more

OPcache is on for every site on every PHP version, holding compiled bytecode in memory so WordPress, your theme and each plugin are not re-parsed on every request. There is nothing to configure: file changes are picked up within seconds, and the dashboard shows hit rate, memory and cached files with a reset for the rare case you need one.

PHP versionper site
7.48.18.28.38.4
Memory limit
512M
Upload max size
256M
Max execution
300s
PHP-FPM workers
12
OPcacheionCube LoaderSOAP
Fine-grained control

Every setting, right in the dashboard.

No support tickets, no config files. Adjust caching and PHP per site and apply instantly.

Site settings · yoursite.com
PHP 8.4
Page cachefull-page nginx
Object cacheredis · in-memory
Cache expirationpage-cache freshness1 hour
Purge on publishauto-flush changed URLs
Changes apply instantly across 14 regions.
Use cases

Built for real WordPress workloads.

A simple marketing site benefits most from page cache. A dynamic store benefits from object cache and PHP tuning. A content-heavy site needs both.

Faster public pages

Enable page cache to serve finished HTML directly from the server.

Lower database load

Enable Redis object cache to reduce repeated database queries.

Better plugin compatibility

Adjust PHP limits for builders, importers, and media-heavy workflows.

Safer performance changes

Flush cache after large updates so visitors see the current version.

FAQ

Performance questions, answered.

What is the difference between page cache and object cache?
Page cache stores the final HTML page and serves it from the server before WordPress loads. Object cache stores repeated database queries and PHP objects in Redis, so WordPress does not repeat the same backend work on every request.
Should every site enable page cache?
Most public, mostly-static WordPress sites benefit from page cache. Highly dynamic sites may need more careful configuration depending on user sessions, carts, forms, and personalized content.
Should every site enable object cache?
Object cache is especially useful for dynamic and database-heavy WordPress sites. It reduces repeated database work and improves backend efficiency.
Can I change PHP settings myself?
Yes. Manage PHP version, resource limits, PHP-FPM worker settings, and optional extensions from the dashboard.
When should I flush cache?
Flush cache after major theme changes, plugin updates, bulk edits, migrations, or whenever the public site does not show recent updates.

Make WordPress faster without managing servers.

Launch on MagicWP and tune caching, PHP, and site performance from one dashboard.

Get StartedRead the Docs