“Allowed Memory Size Exhausted” appears when a WordPress request needs more PHP memory than the configured limit. It may be caused by a heavy plugin, theme, import task, faulty script or a low memory limit.
What the error means
The PHP process stops because it exhausted its memory allowance. The site may show a blank page, a fatal error or fail only during a specific task such as an update, import or page-builder action.
Find the cause first
Review the error log for the file or plugin consuming memory.
Temporarily disable the most recently installed plugin or theme.
Check whether the error happens only during an import, backup or another heavy operation.
Make sure the site runs on a supported and current PHP version.
Increase the WordPress memory limit
You can define a higher WP_MEMORY_LIMIT in wp-config.php if the hosting environment allows more PHP memory. A WordPress setting cannot exceed the server-level maximum.
Server PHP memory limit
If the WordPress limit is already correct, check PHP memory_limit in the hosting panel or ask support to change it. Do not keep increasing the limit without identifying the script that consumes the memory.
Verify after the change
Purge cache and repeat the task that failed.
Monitor the error log for another fatal error.
Check for unusual RAM or CPU usage.
If the issue returns, profile the request or test plugins one by one.
Helpful note
Increasing memory fixes the symptom only when the workload legitimately needs it. A memory leak or faulty code still requires correction of the real cause.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
Semi Dedicated Hosting sits between shared hosting and a fully independent server. It provides more resources and a more controlled environment without requiring the customer to handle all administration of an unmanaged server.
When it makes sense
When the website has higher traffic or needs more resources.
When you need more isolation than a standard shared plan.
When you want provider-managed infrastructure without taking on full server administration.
When you host multiple demanding sites or reseller workloads.
What technical support covers
Core support covers the infrastructure, the hosting environment and service-related issues. Development work, application debugging, plugin changes or malware cleanup may be handled as a separate service.
How migration is organized
A migration requires access to the current hosting or a usable backup from Plesk, cPanel, ISPmanager or another supported panel. The team reviews the backup, moves files and databases and performs checks before DNS records are changed.
Before changing DNS
Preview the new site and verify it loads correctly.
Test forms, email sending, database functions and cron jobs.
Lower TTL where appropriate.
Keep the old hosting available until the transition is complete.
Helpful note
Current resources, migration terms and any development charges are defined by the active plan and technical assessment, not by old commercial descriptions.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
With Managed service, easy performs the agreed administration tasks. With an Unmanaged VPS, the customer is responsible for the OS, updates, security and applications.
Root access
Root access provides full control and full responsibility. Restrict SSH, use keys and apply updates.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
If you want faster delivery of static WordPress assets, a CDN can help a lot. In the legacy material, the suggested flow was based on the W3 Total Cache plugin with a Generic Mirror style setup.
When a CDN is useful
A CDN is useful when your site serves many static files such as images, CSS and JavaScript and you want to reduce latency for visitors coming from different regions.
Installing the plugin
From the WordPress admin area, go to Plugins, add or activate W3 Total Cache and then open its settings.
Enabling the CDN
Inside the plugin settings, enable CDN and choose the appropriate connection type. In the legacy example, Generic Mirror is used so you can define the accelerated URL of your CDN endpoint.
Final checks
Confirm that static assets are loading from the CDN domain.
Purge cache from the plugin and your browser.
Test the site on desktop and mobile.
Watch for mixed content or broken asset URLs.
Helpful note
If styles break or images do not load after the setup, first review the CDN base URL and cache rules before making deeper changes.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
Joomla FTP Layer is a mechanism used in older hosting scenarios to help write files when web server permissions were not properly configured. You do not always need it, but in some environments it can solve practical problems.
When it is used
It is used when Joomla cannot write or modify files directly with the web server permissions. In that case the application relies on FTP credentials to complete tasks such as installations or updates.
What to pay attention to
Use the correct FTP credentials.
Confirm that the FTP path points to the correct installation directory.
Check whether the issue can be solved more cleanly through proper permissions or the correct PHP handler setup.
Helpful note
In modern hosting environments Joomla FTP Layer is often unnecessary. If you still need it, that usually means the overall ownership and permission setup should also be reviewed.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
The right hosting choice is based on the application’s real requirements, not only storage capacity or the lowest price.
Start with the application
List the CMS, PHP version, database, required extensions, expected traffic and functions such as cron, cache or staging. Verify compatibility before migration.
Linux or Windows
Linux is the common choice for WordPress, PHP and MySQL/MariaDB. Windows hosting is mainly required for applications based on Microsoft technologies such as ASP.NET or specific Windows services.
Do not compare storage alone
CPU, RAM, I/O, concurrent processes, inode limits, database workload and email usage can affect performance more than total capacity.
Review security and backups
Look for isolation, malware protection, WAF, maintained software versions, backup frequency and a clear restore process.
Plan for growth
Choose a service that can be upgraded without a complex migration. A suitable entry plan should cover current use and provide a clear next level.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
Publishing a website does not guarantee immediate appearance in search results. Google must first be able to crawl and index it.
Make sure the site is publicly accessible
Confirm that the domain works, SSL is valid and no maintenance mode, password protection or access rule blocks search bots.
Use Google Search Console
Add and verify the domain property, submit the sitemap and review coverage or crawling issues. Submission supports discovery but does not guarantee a specific ranking.
Check robots.txt and noindex
An incorrect robots.txt Disallow rule or a noindex directive can exclude important pages. Also check whether the CMS has a search-engine visibility restriction enabled.
Publish genuinely useful content
Clear titles, unique content, strong internal linking and a fast mobile experience help search engines understand the site.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.