A hosting plan’s monthly visitor allowance does not tell you how well your website will cope when a campaign brings people in at once. Before an advert, promotion or launch, check both the allowance and the work those visitors will ask the site to do. Reading a public information page and submitting an order place different demands on the hosting.
For a WordPress business site where you want help planning capacity, Krystal’s managed WordPress hosting is worth considering. Its current guidance asks customers to discuss large campaigns beforehand and describes support for unexpected traffic spikes. Check the plan’s limits and the ongoing upgrade position as well; that policy is not a promise of unlimited traffic at a fixed price.
This guide helps you prepare a useful capacity brief. If you are still deciding who should handle updates, recovery and hosting support, start with our shared versus managed WordPress hosting comparison.
Separate the three numbers in a hosting quote
Visits describe counted traffic over a period. A provider may define and count visits differently from your analytics software. Find out the measurement period, how repeat visits are handled and whether automated traffic is excluded before comparing the allowance with your own reports.
Bandwidth or data transfer concerns data delivered, rather than how much is stored. A visitor downloading a large PDF can use more transfer than someone reading a short text page. Check whether the plan also has a separate content delivery network allowance. A CDN distributes eligible content through other servers; it does not make every limit disappear.
Processing capacity concerns the work the server can perform. CPU, memory and the handling of simultaneous requests matter when WordPress has to build a page, search a catalogue or process a form. A generous monthly visitor allowance alone cannot establish how your particular site will behave under that workload.
Disk space is another separate limit. It holds the files and database, and should be estimated using your content rather than visitor numbers. Our WordPress storage planning guide includes a worked calculation.
Describe the busy period, not just the monthly total
Consider a hypothetical campaign bringing 3,000 visits. Spread over a month, that is a very different pattern from 3,000 visits arriving during the first hour of a promotion. Even the one-hour figure hides the peak if most people arrive in the first few minutes.
You rarely know that peak precisely in advance. Give the host a range, explain where the estimate came from and say when traffic could arrive. An existing campaign report is better evidence than a hopeful sales target. If this is your first promotion, label the forecast as uncertain and agree what will be monitored.
Then describe the journey. Will people read one page and telephone, search a large product catalogue, check availability or pay? Does a booking or payment service operate elsewhere, and what does your own site still have to do before handing the visitor over? Include the exact landing page and the important next steps in the brief.
For a simple service promotion, the landing page and enquiry form may be the main concerns. For a shop launch, cart, stock and payment behaviour need attention as well. The plan should fit that journey rather than a generic promise to support a certain number of people.
Understand what caching can help with
A page cache can serve a prepared copy of a page instead of making WordPress build it again for each request. That can reduce server work for public content. A campaign landing page with stable information is a useful place to ask whether caching is working as intended.
Personalised or changing information needs more care. A customer’s cart, account and checkout must show the right information to that person. Ask the developer or host to check the relevant exclusions and behaviour. Do not switch on aggressive caching everywhere just before a launch, or install another caching plugin on top of a managed setup without checking compatibility.
Test the actual route after any change: follow the campaign link, open the offer, use the form or checkout and confirm the expected result. A page loading quickly does not demonstrate that a booking is recorded or an enquiry reaches the business.
If ordinary visits are already slow, work through our small-business website speed triage first. Increasing capacity may help a server bottleneck, but it will not remove an oversized image or a troublesome third-party script from the page.
Read the over-limit policy before the campaign
Ask the provider what happens when you reach the allowance. Useful answers distinguish an occasional spike from sustained use above the plan, and explain warnings, charges, restrictions and the upgrade process.
Krystal’s managed WordPress FAQ says an unexpected spike does not automatically trigger shutdown or an extra charge. Its Onyx terms also set out resource limits, paid increases and upgrades. If it has contacted you at least twice about excess use and you have not confirmed your preferred option, it may upgrade the resources or plan and charge accordingly. Read those provisions together and agree the expected campaign requirements in advance.
For any provider, keep a written answer to these questions:
- What exactly is counted, over which dates, and where can I see the usage?
- Which limits apply across the whole account and which apply to this site?
- Who receives an alert, and at what point?
- What happens during an unexpected spike and during repeated excess use?
- Does an upgrade happen automatically, and what would it cost?
- If extra capacity is temporary, how and when can the plan be reduced?
Make sure the account’s alert address reaches somebody who can act. An upgrade warning sitting in an old designer’s inbox is of little help to the person running the promotion.
Prepare a short campaign hosting brief
You do not need to predict every technical detail. Give the host and whoever maintains the site enough information to judge the important risks:
- Campaign: landing-page URL, launch time and time zone, duration and likely sources of visitors.
- Expected traffic: a range, the busiest likely period and the evidence behind the estimate.
- Customer actions: reading, downloading, enquiring, booking or buying, including any external services.
- Current baseline: recent provider usage, known slow steps and current plan limits.
- Preparation: who checks caching, forms, checkout, backups and any proposed capacity change.
- During the campaign: who watches errors and usage, who can contact support and who can pause advertising if the enquiry or sales path fails.
Agree any load testing with the provider before it is run. A test that creates lots of requests can affect a live service or trigger protective systems. If testing is appropriate, have the developer define a realistic journey and a way to stop it, rather than merely firing requests at the homepage.
Keep late changes limited. Publish the landing page with enough time to check it, and avoid combining the campaign with an unnecessary host move or major plugin replacement. Record what is ready and what remains uncertain so the person launching the promotion can make an informed decision.
Use the results to choose the next plan
After the campaign, compare the forecast with the provider’s usage and the actual customer journey. Note the peak period, any errors, support action and whether enquiries or orders were recorded as expected. A monthly total that stayed within the allowance is useful, but it does not explain a brief checkout failure.
If the site coped and has room for the next planned campaign, keep that evidence. If it struggled, ask which resource or application step was responsible before buying a larger plan. A targeted fix and an upgrade answer different problems, and sometimes both are needed.
For a business in Formby, Freshfield or L37 preparing a promotion, discuss the landing page and enquiry journey with Formby Web Design. Include the campaign outline and existing website address so the work can be scoped around what customers need to do.
Sources checked 18 October 2026: Krystal managed WordPress FAQ, Krystal resource allocation guidance, Krystal terms, section 7.10, and WordPress caching documentation.
