Worked example
Separate page revalidation from immutable asset caching
Illustrative scenario and demonstration data. Not Broad Promo client results or a performance promise.
| Resource | Before update | After update | Verification |
|---|---|---|---|
| Page HTML | References style-a1.css | References style-b2.css | Revalidate the page response |
| Versioned stylesheet | style-a1.css | style-b2.css | New content has a new URL |
| Shared footer | Previous contact content | Updated contact content | Check its response cache policy |
| Service worker, if used | Previous cached version | Intended active version | Test an existing visitor as well as a new visitor |
These filenames are illustrative. A long cache lifetime is appropriate only when a changed asset receives a changed URL. Verify actual server, CDN and browser behavior rather than forcing a full cache clear on every visit.
What matters for landing page hosting
Landing page hosting keeps the campaign destination available, secure, and maintainable. The service may include deployment, certificates, backups, monitoring, and content changes, but those responsibilities vary between providers. Hosting should suit the page's actual technology and traffic. A static page can be lightweight while still depending on external forms or analytics, so availability checks should follow the full process from submitting a form to receiving the enquiry.
Agree on the hosting and support responsibilities
Check what is hosted, who controls the domain and DNS, and which external form or CRM services the page uses. Confirm HTTPS, caching, access for updates, backups, and restoration arrangements. A page can load correctly while its form fails, so test that enquiries reach the right place as well.
Put support hours, emergency contacts, included updates, and responsibility for third-party failures in writing. Before moving the page, test the new setup and keep a way to restore the old one where possible. Agree what recovery and exit support includes; hosting does not automatically cover every integration, content edit, or request outside support hours.
A practical checklist
- Confirm ownership and access for the domain, DNS, hosting account, and source files.
- Document the page technology and any external form or CRM dependencies.
- Set up HTTPS and test the final domain before campaign launch.
- Use optimized assets and cache rules that allow fresh content after updates.
- Agree on backups, restore procedures, monitoring, and support response.
- Test enquiry delivery as well as whether the page loads.
Use this checklist to see what is working and what needs attention. Start with the most important change before taking on more work. Record what you change so you can understand the results later.
How to assess the results
Review availability, server response, page loading behaviour, failed requests, and successful lead delivery. Compare real user experience on mobile networks where data is available. A hosting uptime figure does not prove that a third-party form or CRM connection is working, so include those dependencies in operational checks.
What to include in your brief
Share your domain and DNS details, page files or platform, expected traffic, and any external form or CRM services. Explain how often you need updates, what support hours you need, and who should be contacted if something fails. Agree on access, backups, recovery, and moving to another provider without disrupting your website or email.
Ask for a proposal explaining what is included, what your team needs to provide, who owns the work, and what it costs. Agree when you will review progress. Broad Promo can help you plan the services you need and explain how they fit together, with the details confirmed before work begins.