Server-side timing checks after a content import
A practical performance note from the AS57110 WordPress demo, written to exercise a realistic content archive.
Operational context
This article is part of the larger AS57110 showcase archive. It gives the site a realistic mix of posts, media, comments, categories, tags, and internal links so cache testing covers more than one static homepage.
Cache path
Repeat visitors should be served from LiteSpeed page cache after the first generated response.
Content weight
Featured images, excerpts, comments, and archives give the install enough size to behave like a real site.
Testing note
Measure both the initial uncached response and a warmed repeat request before drawing conclusions.
Checklist
- Confirm the route returns a normal 200 response.
- Inspect
x-litespeed-cacheheaders. - Repeat the same URL to verify warm-cache delivery.
- Compare post, page, archive, and media-heavy routes.
The difference between cold and warm requests is very clear on this stack.
This is the kind of detail that makes a hosting demo easier to inspect.