johan
37e5497923
Drop the redundant documentation/marketing/ nesting inherited from the plugin repos, so files sit at marketing/<plugin>/<page>.md. These paths become raw URLs pasted into Elementor pages and ACF fields, so they are much cheaper to change now than once sites reference them. Fixes the four cross-plugin links for their new depth, and corrects the README, which still pointed at the abandoned per-repo documentation/ folders instead of this repo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
20 lines
1.5 KiB
Markdown
Executable File
20 lines
1.5 KiB
Markdown
Executable File
# Full-Page Caching
|
|
|
|
The single biggest lever for WordPress speed, and the first thing any performance audit will tell you to fix.
|
|
|
|
## The problem it solves
|
|
|
|
Every WordPress page load runs the same expensive process from scratch: connect to the database, run dozens of queries to assemble the content, execute PHP for your theme and every active plugin, then finally send HTML to the browser. For a typical visitor, that's the difference between a server response in a few milliseconds and one that takes the better part of a second — before a single image or stylesheet has even started downloading.
|
|
|
|
## How it helps
|
|
|
|
Dotjuice Pagespeed builds a static snapshot of each page the first time it's requested, then serves that snapshot directly to every visitor after — bypassing WordPress, your database, and PHP entirely. It's the difference between a librarian re-writing a book from memory every time someone asks for it, versus just handing over a printed copy.
|
|
|
|
Mobile and desktop visitors get their own separate cached versions automatically, so responsive layouts and mobile-specific content are never mixed up.
|
|
|
|
Cached pages don't go stale, either — the moment you publish or update a post, its cached copy (and your homepage) are cleared instantly, and the plugin can even pre-warm the new cache in the background so your first visitor doesn't pay the "empty cache" cost.
|
|
|
|
## The result
|
|
|
|
Server response times measured in single-digit milliseconds instead of hundreds — the foundation every other optimisation in this plugin builds on top of.
|