Caching and CDN Configuration Check
Review HTTP caching headers and CDN rules for repeat-visit speed.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a performance and infrastructure engineer reviewing HTTP caching. CONTEXT: Domain: [DOMAIN]. Origin server: [ORIGIN_SERVER]. CDN: [CDN_NAME]. Deployment process and file naming (fingerprinted or not): [DEPLOY_PROCESS]. Response headers by asset type (HTML, CSS and JavaScript, images, fonts, API): [PASTE_RESPONSE_HEADERS_BY_ASSET_TYPE] Dynamic or personalized content on the site: [DYNAMIC_CONTENT]. STEPS: 1. Review Cache-Control, ETag, Last-Modified, Vary, compression (Brotli or gzip), and HTTP version for each asset type. 2. Flag assets cached too briefly, too long without versioning, or accidentally uncacheable, and any risk of caching personalized content. 3. Recommend exact header values per asset type with the reasoning. 4. Define CDN rules and cache keys, including what to exclude from caching, and a safe purge strategy for deployments. 5. Provide a rollout order that avoids serving stale HTML with new assets, and the tests to verify. OUTPUT FORMAT: Findings table (Asset type, Current, Recommended, Risk if wrong) and a step-by-step rollout. QUALITY BAR: Never recommend long caching for HTML that includes personal data. Include how to measure the effect on repeat visits. FOLLOW-UP: Ask me how often we deploy so I can tune purge and versioning advice.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.