Speed up public pages without breaking wp-admin, logins, carts, or personalized content
Goal
You should be able to demonstrate the result described in the lesson and explain why each step was necessary.
You should be able to demonstrate the result described in the lesson and explain why each step was necessary.
Step-by-step
01
Start with static assets
Images, CSS, and JS are the easiest content to cache aggressively.
02
Exclude administration
Do not cache wp-admin and authenticated dashboard responses.
03
Be careful with HTML
Full-page caching can be powerful, but it must bypass logged-in and personalized sessions.
04
Purge after major changes
Theme deployments and CSS changes can look broken if old edge cache survives.
05
Measure cache status
Inspect response headers so you know whether Cloudflare is actually serving a cached object.
Verify before moving on
You should be able to demonstrate the result described in the lesson and explain why each step was necessary.
You should be able to demonstrate the result described in the lesson and explain why each step was necessary.
Troubleshooting
If a command or screen differs from the lesson, stop and verify the version you are using before forcing a change.
What you learned
You now understand the purpose of this part of the system and have a concrete result you can verify before continuing to the next lesson.