Antihost WordPress hosting plans use defined resources and limits.
These limits are not random restrictions. They help keep each WordPress environment stable, measurable, and predictable. Instead of relying on vague “unlimited” claims, Antihost defines the resources your site can use.
Good to know
Defined limits help protect hosting stability. They make resource usage visible and prevent one site from affecting other environments.
What resources mean
CPU
CPU is the processing power used by your WordPress site.
Your site uses CPU when it:
- loads pages;
- runs PHP code;
- processes plugin logic;
- handles WordPress admin actions;
- runs WooCommerce operations;
- processes forms, searches, or dynamic requests.
If CPU usage is too high, the site may become slower during active traffic or heavy background operations.
Simple explanation
CPU handles “work”. The more dynamic work your WordPress site performs, the more CPU it needs.
RAM
RAM is the memory available to your WordPress environment while it is running.
Your site uses RAM for:
- WordPress processes;
- PHP execution;
- plugins;
- admin dashboard actions;
- caching systems;
- database-related operations;
- background tasks.
If RAM is too limited for your workload, the site may become unstable, slow, or unable to process some requests correctly.
Simple explanation
RAM is the active working space your site uses while processing requests.
Storage
Storage is the disk space used by your WordPress site.
Storage may include:
- WordPress files;
- theme files;
- plugin files;
- uploaded media;
- images;
- videos;
- backups, if stored within your plan limits;
- cache files;
- logs;
- temporary files.
If storage is full, you may not be able to upload new files, update plugins, create backups, or save changes correctly.
Important
Large media libraries, backups, cache files, and logs can increase storage usage over time.
I/O
I/O means input/output operations between your site and storage.
Your site uses I/O when it reads or writes files.
This can happen when:
- WordPress loads files;
- images are uploaded;
- plugins write logs;
- cache files are created;
- backups are generated;
- updates are installed;
- media is processed.
High I/O usage can affect how quickly the site reads and writes data.
Simple explanation
I/O is how actively your site reads from and writes to disk. Heavy file activity requires more I/O capacity.
Bandwidth
Bandwidth is the amount of data transferred between your website and visitors.
Your site uses bandwidth when visitors load:
- pages;
- images;
- CSS and JavaScript files;
- videos;
- downloads;
- media files;
- admin assets.
The more visitors and media-heavy pages you have, the more bandwidth your site uses.
Simple explanation
Bandwidth is traffic volume. It grows when more people visit your site or when pages contain large files.
Why Antihost uses limits
Limits protect stability
Resource limits define how much CPU, RAM, storage, I/O, and bandwidth your site can use under your plan.
This helps prevent uncontrolled resource usage and keeps hosting behavior predictable.
Important
Limits are part of stability. Without limits, one overloaded site or process can consume more resources than expected and affect performance.
Limits make usage visible
Defined limits make it easier to understand whether your current plan fits your site.
Instead of guessing, you can compare your site’s resource usage with the plan’s available capacity.
This helps you decide when optimization or upgrade is needed.
Limits make plans easier to compare
Different plans provide different resource levels.
A higher plan may include more CPU, RAM, storage, I/O, bandwidth, backup capacity, or support options.
Good to know
Plan limits are not only about size. They define the operational baseline your WordPress site can rely on.
How to know if your site needs more resources
Pages load slower under normal traffic
If pages become slower even when traffic is normal, the site may be hitting resource pressure.
This can happen because of:
- heavy plugins;
- inefficient theme logic;
- large database queries;
- too many dynamic requests;
- insufficient CPU or RAM;
- high I/O usage;
- lack of caching.
The site slows down during traffic peaks
If your site works normally most of the time but slows down during campaigns, launches, or traffic spikes, your current plan may not provide enough capacity for peak load.
Example
A site may work well with regular traffic but become slow during paid campaigns, product launches, or seasonal demand.
WordPress admin becomes slow
WordPress admin can also show resource pressure.
Signs include:
- slow dashboard loading;
- slow plugin updates;
- slow media uploads;
- errors when saving settings;
- timeout errors;
- slow WooCommerce admin pages;
- slow page builder editing.
Updates or backups fail
If plugin updates, theme updates, or backups fail, the site may be hitting storage, memory, or process limits.
This does not always mean the plan is too small, but it is a signal to check resource usage.
Good to know
Failed updates or backups can also happen because of plugin conflicts, file permissions, or other WordPress-level issues. Resource usage is one possible cause, not the only one.
You see resource warnings in the panel
If Antihost shows resource usage or warnings in the panel, check whether your site regularly approaches or exceeds plan limits.
Occasional spikes may be normal. Repeated high usage is a stronger signal.
Important
Repeated resource pressure is different from a one-time spike. Repeated pressure usually means the site needs optimization, more resources, or a different plan.
When to upgrade your plan
Upgrade when high usage becomes regular
Consider upgrading if your site regularly uses most of its available CPU, RAM, I/O, storage, or bandwidth.
This is especially important if high usage affects loading speed, admin stability, or business-critical flows.
Upgrade before planned traffic growth
Upgrade before planned campaigns or launches if you expect significantly more traffic.
This can include:
- paid ad campaigns;
- product launches;
- seasonal sales;
- email campaigns;
- PR mentions;
- high-traffic landing pages;
- WooCommerce promotions.
Recommended
Upgrade before the traffic arrives, not after the site becomes slow.
Upgrade when the site becomes business-critical
If your WordPress site directly supports revenue, leads, bookings, or customer onboarding, resource stability matters more.
Upgrade may be needed when downtime or slow performance starts to create business risk.
Examples:
- WooCommerce store;
- lead generation website;
- booking platform;
- membership website;
- LMS platform;
- high-traffic business site;
- paid traffic landing pages.
Upgrade when optimization is no longer enough
Sometimes optimization can reduce resource usage.
But if the site has naturally grown, more resources may be the correct solution.
This can happen when you add:
- more products;
- more traffic;
- more media;
- more plugins;
- more logged-in users;
- more dynamic pages;
- more integrations.
Simple rule
Optimize obvious waste first. Upgrade when the workload itself has grown beyond the current plan.
What limits are normal for stability
CPU and RAM limits
CPU and RAM limits help keep your WordPress environment predictable.
They prevent one site process from using uncontrolled resources.
This is especially important for WordPress because plugins, themes, page builders, and WooCommerce can create heavy dynamic workloads.
Storage limits
Storage limits keep disk usage controlled.
Without storage limits, old backups, media files, cache files, and logs can grow without control.
Good practice
Regularly remove unused media, old exports, unnecessary backups, and plugins you no longer use.
I/O limits
I/O limits help keep disk activity stable.
This matters during:
- backups;
- updates;
- cache generation;
- bulk media operations;
- plugin processes;
- imports and exports.
High I/O activity can affect the site if too many read/write operations happen at once.
Bandwidth limits
Bandwidth limits define how much traffic your plan supports.
If your site has large media files, many visitors, or download-heavy pages, bandwidth usage may grow quickly.
Important
“Unlimited” bandwidth often still has technical or policy limits. Defined bandwidth is clearer because you can see what your plan is built to handle.
What happens if limits are exceeded
The site may slow down
If your site reaches CPU, RAM, or I/O limits, requests may become slower.
Visitors may experience:
- slower page loading;
- delayed responses;
- timeouts;
- admin delays;
- unstable plugin behavior.
Some operations may fail
If resource usage is too high, some operations may fail.
This can include:
- plugin updates;
- theme updates;
- uploads;
- backups;
- imports;
- exports;
- page builder saves;
- WooCommerce background tasks.
Storage-related actions may stop working
If storage is full, WordPress may be unable to write new files.
This can affect:
- media uploads;
- plugin updates;
- theme updates;
- cache files;
- backups;
- logs;
- temporary files.
Important
A full storage limit can cause practical site issues even if CPU and RAM usage are normal.
Bandwidth overuse may require action
If bandwidth limits are exceeded, the next steps may depend on your plan and Antihost policy.
Possible outcomes may include:
- warning in the panel;
- recommendation to upgrade;
- temporary limitation;
- need for manual review;
- additional bandwidth option, if available.
Plan policy applies
Exact behavior after exceeding limits depends on your active hosting plan and Antihost service rules.
What to do before upgrading
Check whether the issue is resource-related
Before upgrading, check whether the site is actually limited by resources.
A slow site may also be caused by:
- heavy plugins;
- poor theme performance;
- large images;
- missing caching;
- external scripts;
- slow third-party APIs;
- database bloat;
- broken plugin behavior.
Good to know
More resources can help with real workload growth, but they may not fix inefficient code, broken plugins, or external service delays.
Review recent changes
Check whether the issue started after:
- installing a new plugin;
- updating a plugin;
- changing a theme;
- adding tracking scripts;
- importing many products;
- adding large images or videos;
- launching a campaign;
- enabling a new integration.
If the problem started after a specific change, optimization or rollback may be better than upgrading immediately.
Contact support if unsure
If you are not sure whether you need more resources, contact Antihost support.
Support can help identify whether the issue is likely related to:
- hosting resources;
- WordPress configuration;
- plugins;
- theme behavior;
- traffic growth;
- DNS/SSL;
- external services.
When to contact support
Contact support if resource usage affects the site
Contact Antihost support if:
- the site is slow and you see high resource usage;
- WordPress admin becomes unstable;
- backups or updates fail;
- storage is full and you are not sure what to remove;
- traffic increased and the site cannot handle it;
- you see resource warnings in the panel;
- you need help choosing a higher plan;
- you are not sure whether the issue is resource-related.
What to include in your support request
When contacting support, include:
- your domain name;
- your WordPress hosting plan;
- what issue you see;
- when the issue started;
- whether traffic recently increased;
- whether you changed plugins or themes;
- whether the issue affects live or staging;
- screenshots of resource usage, if available;
- any error messages shown in WordPress or the panel.
Why this matters
Resource issues can come from real traffic growth, inefficient plugins, storage pressure, background tasks, or plan limits. Context helps support separate a hosting limit from a WordPress-level issue.
Summary
Resources define what your WordPress site can reliably use
Antihost uses defined resources and limits to make WordPress hosting more predictable.
CPU, RAM, storage, I/O, and bandwidth each describe a different part of your site’s workload.
If your site regularly approaches or exceeds limits, you may need optimization, a higher plan, or a custom setup.