CMS Resource Usage is a fee based on the amount of server resources a customer's website consumes. Key factors that contribute to this charge include:
Bandwidth Usage: The amount of data transferred to and from the website. Example: A news site hosting large photo galleries, large file downloads, high traffic or streaming videos will use more bandwidth than a small community paper with mostly text-based articles.
Server utilization: Represents the total computing resources required to run and support a website’s performance, including both CPU and memory demands. CPU usage reflects the processing power needed for dynamic content or background tasks—for example, sites with real-time data updates, automated feeds, or personalized recommendations require more processing than static sites. Memory (RAM) usage captures the amount of memory needed to support site functions, which increases during high-traffic periods or when pages contain more content blocks, regions, widgets, or ads.
Content Storage: The total amount of disk space occupied by website files, such as images, videos, PDFs, backups, and archived content. Example: A site that frequently uploads high-resolution photos, video clips, or maintains long-term archives will consume more storage space.
Database Load: The intensity and frequency of queries or transactions the site performs. Example: A site with complex search features or frequent content updates (e.g., adding new articles every few minutes) places a heavier load on the database than one that updates weekly.
Concurrent Connections: The number of users accessing the site simultaneously, including both human visitors and bots. Example: During a major breaking story or election night, simultaneous user traffic spikes — along with search engine and social media bots — can significantly increase concurrent connections.
BLOX Digital monitors CMS Resource Usage and bills for monthly allocated usage and any overages. If an overage occurs, it will be reflected in the customer’s billing or in CMS usage reporting. To avoid overage fees, the customer must request and approve increased usage allocations.
What does this mean for me?
Here’s what the shift to CMS Resource Usage means for your team in practical terms:
1. Your monthly “Bandwidth” line item is now called CMS Resource Usage
This updated name more accurately reflects everything included in the hosting resources your site uses — not just the amount of data transferred, but also CPU, memory, storage, database activity, and simultaneous connections. (This is a label change only — not a change to how your site is hosted or supported.)
2. Your site’s resource needs naturally grow as your audience and content grow
High-resolution photos, videos, large archives, dynamic pages, automated feeds, and traffic spikes (like breaking news or elections) all require more server resources. Sites with richer media or heavier workloads will use more of their allocation.
3. BLOX monitors your usage and will notify you if you’re approaching or exceeding your allocation
If you ever exceed your monthly allocation, it will show up on your billing statement or usage reports as an overage. BLOX may recommend increasing your allocation if your site consistently uses more resources than your plan includes. (You’re always in control — no increase is made without your approval.)
4. You can request more CMS Resource Usage at any time to avoid future overages
If you’re planning a major project — a redesign, a large photo-heavy series, new video initiatives, or expecting a high-traffic event — letting BLOX know ahead of time helps ensure your allocation is right-sized.
5. Nothing changes about how your site performs today
Your site continues to run as normal. The updated term simply better reflects the full range of resources BLOX provides to power your site behind the scenes.
