Which WordPress pages should be cached?
A fast public homepage and a correct customer session need different cache rules. On managed WordPress, the starter homepage can be served from an origin cache for five minutes.
Public pages
The cache is isolated by site and URL. Eligible published pages can reuse a saved response for anonymous visitors. Changing content invalidates the cached version so visitors can see the edit.
Personal and interactive pages
Signed-in requests, forms, shopping carts and checkout need a fresh response. The hosting service keeps their responses out of shared caches. WordPress administration and password setup also use private responses.
Compare before and after
Measure the same public URL and use the same location when comparing hosting speed. Record the baseline before migration, then measure again after DNS and HTTPS are working. A faster cached response measures delivery speed, not search position.