Understanding Server Limits on Free Hosting
ProFreeHost uses strict resource limits to ensure that a single website doesn’t dominate all resources on the server, thereby slowing down thousands of other sites which share resources. These limits are the primary reason a site might suddenly feel slow, show a 508 Resource Limit Reached error, or face an automated suspension.
1. CPU and Script Execution Time
Every time a visitor loads a page, your PHP scripts (WordPress, themes, and plugins) use the server’s “brain” (CPU) to process data.
-
The Limit: You are typically given a tiny percentage of the total CPU or a maximum “execution time” per script (often only 30–60 seconds).
-
Triggers: Heavy page builders (Elementor/Divi), “nulled” themes, or backup/security plugins that scan thousands of files at once.
-
Result: If a script takes too long, the server kills the process, resulting in a 504 Gateway Timeout or a blank page.
2. Concurrent Requests (Entry Processes)
This limits how many people can “knock on your door” at the exact same millisecond.
-
The Limit: Free hosts often cap this at 20–50 processes. Note that this isn’t total visitors, but active tasks. If one user opens 10 tabs at once, they consume 10 entry processes.
-
Result: Once the limit is hit, the next visitor gets a 508 Resource Limit Reached error until a current process finishes.
3. Hits vs. Bandwidth
While “Bandwidth” refers to the total volume of data (GBs) transferred, “Hits” refers to the number of individual requests.
-
Daily Hit Limit: ProFreeHost limits you to around 50,000 hits per day.
-
The Trap: A single page load can consist of 50+ “hits” (1 for the HTML, 30 for images, 10 for CSS/JS, etc.). A small spike in traffic or a single search engine bot crawling your site can exhaust this daily limit in minutes.
4. File Count (Inodes)
On free hosting, the number of files you have is often more important than the size of those files.
-
The Limit: This is called an Inode limit. A common cap is 30,000 to 50,000 inodes.
-
The Trap: Every single image, email, and plugin file counts as 1 inode. WordPress generates multiple “thumbnail” sizes for every image you upload, which can eat through your inode limit surprisingly fast.
-
Result: Once you hit the limit, you cannot upload new files or even receive emails, even if you still have GBs of “disk space” left.
5. Database and Email Restrictions
-
Concurrent MySQL Connections: Usually capped at 20–30. If your site has too many database-heavy plugins (like WooCommerce or forums), the database will “refuse” new connections.
-
Email Sending: To prevent spam, free hosts often block the mail() function entirely or limit you to 5–10 emails per hour. Contact forms often fail on free hosting for this reason.
How to Stay Within the Limits
To keep your site running smoothly without being suspended:
-
Offload Your Media: Host your videos on YouTube and your large images on a service like Imgur or a CDN.
-
Stop the Scans: Never run “High Performance” security scans or scheduled backups on a free host; these are the #1 cause of CPU suspensions.
-
Clean Your Inodes: Delete unused themes, plugins, and old “trashed” posts. Use a plugin to stop WordPress from generating unnecessary image sizes.
-
Use Cloudflare: A custom domain with Cloudflare can block “bad” bots from eating up your hits and bandwidth before they even reach your server.