AccelerateWP in cPanel explained

AccelerateWP is a performance solution from CloudLinux for WordPress websites. At CURIAWEB, AccelerateWP is integrated into the hosting environment and can be managed directly via cPanel for supported WordPress installations.

AccelerateWP is designed to deliver WordPress faster and more efficiently. To achieve this, various optimizations at the hosting and WordPress levels are combined.

In this guide, we will show you how to find AccelerateWP in the CURIAWEB cPanel, select a WordPress installation, activate AccelerateWP, and then check whether your website is working correctly.

Important: AccelerateWP should not simply be activated in addition to several already existing cache and performance solutions. First, check which optimizations your WordPress website is already using. Multiple systems with the same task can interfere with each other.

What is AccelerateWP? #

AccelerateWP was specifically developed for WordPress hosting and is part of the CloudLinux ecosystem.

The solution combines server-side capabilities of the hosting environment with a WordPress integration. This allows performance optimizations to be implemented without you having to piece together all the measures yourself via various plugins and server settings.

Simplified:

CURIAWEB Hosting
        ↓
CloudLinux
        ↓
AccelerateWP
        ↓
WordPress Integration
        ↓
Website Performance Optimization

Which concrete features are available depends on the AccelerateWP version used on the server, the range of functions, and the respective WordPress installation.

AccelerateWP is not a feature of WordPress itself #

AccelerateWP is not part of the WordPress core.

It is an additional hosting and performance solution that works with WordPress.

This is important because a problem with AccelerateWP is not automatically a WordPress core problem – and vice versa.

AccelerateWP is not a cPanel-developed feature either #

That AccelerateWP in CURIAWEB-cPanel under Software appears, does not mean that the technology comes from cPanel itself.

AccelerateWP is powered by CloudLinux provided and integrated into the hosting environment.

What does AccelerateWP optimize? #

Depending on the available feature set, AccelerateWP can provide or coordinate various measures for WordPress performance.

This may include, for example:

• Caching
• Optimization of WordPress delivery
• Optimization of static resources
• CSS and JavaScript optimizations
• Image optimization
• additional performance features

Important: What options you actually see in your AccelerateWP area is what matters. Do not enable a setting just based on someone else's guide if that function is named differently in your CURIAWEB environment or is not present.

What AccelerateWP cannot fix #

Performance optimization can make a technically functioning website faster. However, it does not automatically fix fundamental errors within a WordPress installation.

For example, AccelerWP does not automatically fix:

• faulty plugins
• defective custom PHP code
• incorrect DNS configuration
• external services with long response times
• an overloaded application due to problematic processes
• Error in a theme
• a damaged database

If a website already has technical errors, these should be investigated first.

Before activation: Check existing performance solutions #

First, open the WordPress administration area and check the installed plugins.

Pay special attention to plugins whose task is caching or performance optimization.

Typical functions of such plugins can be:

Page Cache
CSS Minification
JavaScript Minification
Lazy Loading
Image Optimization
Database Optimization

If multiple systems take on the same task simultaneously, the configuration can become unnecessarily complex.

CURIAWEB recommendation: Do not use multiple full caching and performance systems in parallel without knowing exactly which functions are active in each case.

Why multiple cache systems can be problematic #

In simple terms, caching means that content that has already been generated is stored temporarily so that it can be delivered faster on subsequent requests.

When multiple systems cache independently of each other, the following chain can occur, for example:

WordPress
   ↓
Cache System A
   ↓
Cache System B
   ↓
Browser

In the event of changes, it can then be difficult to trace which tier is still serving an older version of the page.

This can manifest, for example, in changes being saved in the WordPress editor but not yet appearing on the publicly visible website.

1. Log in to cPanel #

Log in to your CURIAWEB cPanel.

Then open:

Software → AccelerateWP

This takes you to the management of the WordPress installations detected or supported by AccelerateWP.

2. Select WordPress installation #

If multiple WordPress websites are present in your hosting account, multiple installations may be displayed.

Select the domain or WordPress installation that you want to optimize.

For example:

example.com

Attention: Always check the domain when dealing with multiple websites. You should not accidentally make changes to performance and cache settings on another live WordPress installation.

WordPress is not displayed in AccelerateWP #

If an existing WordPress website is not displaying or is not being recognized, you should not immediately reinstall WordPress.

Check first:

• whether WordPress is installed under the expected domain path
• whether the installation works in principle
• whether the domain is set up correctly
• whether WordPress or the installation is detected by the hosting environment

An additional check may be required in the event of a manually relocated or unusually structured installation.

3. Check AccelerateWP status #

Open the relevant WordPress installation and first check the current AccelerateWP status.

Check whether AccelerateWP is already activated or if the optimization for this website still needs to be set up.

Do not immediately change any further settings before you know the initial state.

Practical Tip: Note the existing settings on an already configured website or take a screenshot before making any changes.

4. Enable AccelerateWP for WordPress #

If AccelerateWP is not yet active for the selected WordPress installation, you can initiate activation using the provided function.

The exact labeling of the button may depend on the version used.

Wait until the activation is complete or the corresponding status is confirmed.

5. Check WordPress integration #

AccelerateWP does not operate exclusively outside of WordPress. Appropriate AccelerateWP components or a plugin can be used within the WordPress installation for integration.

Log in to WordPress after activation and check if the AccelerateWP integration is present and not reporting any errors.

Important: Do not remove a WordPress component required by AccelerateWP just because you did not install it yourself. It may be part of the hosting integration.

6. Test website before further optimizations #

After activation, first open the website normally in your browser.

Check in particular:

• Home
• important subpages
• Navigation
• Forms
• WordPress administration area
• Login functions
• dynamic areas of the website

For a WooCommerce shop, you should also check shop functions like the shopping cart and checkout.

Why dynamic pages require special attention #

Not every WordPress site is suitable for the same type of caching.

A normal content page can be identical for many visitors. Other pages, however, contain user- or session-dependent content.

In an online shop, this includes, for example:

Cart
Checkout
Customer Account

Such areas must be handled correctly by a performance solution.

Practical Tip: When testing WooCommerce, do not just test the shop homepage. Add a product to the cart, open the cart, and proceed to checkout without completing an order.

7. Check available optimizations #

Then open the AccelerateWP settings for the website in question.

Which options are available there depends on the range of features provided by your hosting.

Check each option individually and do not change all settings at once.

Why optimizations should be enabled gradually #

If you enable multiple optimizations at once and a display or functional error subsequently occurs, it is harder to determine which setting is responsible for it.

A better approach is:

Test initial state
→ change one optimization
→ test website
→ change next optimization
→ test again

This makes it much faster to assign a problem to a specific setting.

Caching #

A key performance measure is caching.

Without caching, WordPress typically has to execute various PHP and database processes on a page request before the finished page is delivered to the visitor.

Simplified:

Visitor
   ↓
WordPress
   ↓
PHP
   ↓
Database
   ↓
Generate page
   ↓
Response

With appropriate caching, previously generated results can be partially reused.

As a result, WordPress does not have to perform certain work again on every identical request.

Take cache into account after changes #

If you change a page in WordPress and subsequently still see the old content, a cache may be involved.

Before changing any further settings, you should therefore check whether existing cache contents need to be updated or cleared.

Don't constantly clear the cache without reason #

A cache is precisely intended to prevent content from having to be recalculated constantly.

Clearing is useful if cached content is actually causing problems after a change or needs to be updated specifically.

On the other hand, permanent manual deletion on every normal page view is not the purpose of a cache system.

CSS optimization #

Depending on the feature set, AccelerateWP can provide optimizations for CSS.

CSS controls large parts of a website's presentation.

Optimizations can, for example, aim to reduce the amount of data to be transmitted or to make delivery more efficient.

Visually check CSS optimization after activation #

After making a change to CSS-related performance features, you should check several page types.

Pay special attention to:

• Layout
• Fonts
• Spacers
• Navigation
• Buttons
• Mobile view

If the website suddenly appears unformatted or misaligned after an optimization, first disable the most recently changed option and test again.

JavaScript Optimization #

JavaScript is used by WordPress websites for numerous interactive features.

This may include, for example:

• Menus
• Slider
• Forms
• Pop-ups
• Shop features
• Tracking
• interactive page elements

JavaScript optimizations can improve delivery, but when combined inappropriately, they can also expose functional issues.

Not just visual testing of JavaScript #

A website can look visually correct after JavaScript optimization while a background function no longer works.

Test this, for example:

Open menu
Submit form
Operate slider
Trigger popup
Update shopping cart
Go to checkout

Important: When optimizing JavaScript, it is not enough to just look at the home page. Interactive features must actually be used and tested.

Image optimization #

Depending on the available AccelerateWP feature set, image optimizations may also be offered.

Images are among the largest files transferred on many websites and therefore have a significant impact on loading time.

However, performance optimization does not replace sensible image selection.

An image should already fit the website in terms of dimensions and intended use.

Lazy Loading #

In simple terms, lazy loading means that certain content is only loaded when it is actually needed or brought close to the visible area.

This can reduce the amount of data to be initially transferred, especially on image-heavy pages.

If WordPress, a theme, another plugin, and AccelerateWP offer similar lazy-loading features, you should not automatically activate all variants at the same time.

Avoid duplicate optimizations #

A common mistake in WordPress performance is not too little, but too much optimization.

For example, the following can be present simultaneously:

Theme optimization
+
Cache plugin
+
Image optimization plugin
+
JavaScript optimization plugin
+
AccelerateWP

This can work if the tasks are clearly separated. However, if the same functions are executed multiple times, troubleshooting becomes significantly more difficult.

CURIAWEB recommendation: Deliberately decide for each core performance task which system should be responsible for it. Avoid multiple comprehensive solutions working in parallel.

AccelerateWP and existing cache plugin #

If a cache plugin is already installed, you should check its features before fully activating AccelerateWP.

The crucial factor is not just the name of the plugin, but which functions are actually enabled.

For example, one plugin can handle just a single specific task, while another represents a complete caching system.

Do not simply delete multiple plugins #

When optimizing an existing WordPress website, you should not delete performance plugins indiscriminately.

Check first:

• what function the plugin performs
• whether AccelerateWP is supposed to replace this feature
• whether the plugin has additional features
• whether the website continues to function correctly after deactivation

Disable before deleting #

If you no longer need an existing performance plugin, it makes sense for a live website to first deactivate it and test the website.

Only when it is clear that no required function is missing can you decide on final removal.

Compare performance before and after activation #

If you want to know whether an optimization is actually helping, you should not judge solely by feel.

Try to create a baseline before making major changes.

Then compare the same pages under comparable conditions.

Not just evaluating a single test run #

Performance measurements can fluctuate.

For example, a single test can be affected by network conditions, cache state, or external services.

Several comparable measurements therefore yield a more reliable picture than a single value.

Consider cache warmup #

A page may respond more slowly on the first visit after clearing a cache than on subsequent visits because certain content must be regenerated first.

Therefore, do not uncritically compare a completely uncached call with an already cached call.

Logged-in administrators can see other results #

Caching systems sometimes treat logged-in WordPress users differently than normal visitors.

Testing the website exclusively during an active WordPress administrator session may therefore cause the result to differ from the behavior of a regular visitor.

Practical Tip: Additionally, check important changes in a private browser window or without an active WordPress login.

AccelerateWP activated, but website does not seem faster #

If no clear improvement is noticeable after activation, it does not automatically mean that AccelerateWP is not working.

The actual loading time of a website depends on many factors.

This includes, for example:

• Theme
• Plugins
• PHP processing
• Database queries
• Pictures
• Fonts
• external scripts
• Tracking services
• external APIs
• Number and size of the resources

External resources cannot be completely resolved by hosting caching #

If a website waits for external services while loading, their response time is not entirely under the control of your own web hosting.

This may include, for example, external fonts, analytics services, videos, maps, advertising networks, or APIs.

AccelerateWP therefore cannot eliminate every website delay.

Website broken after AccelerateWP activation #

If a problem occurs immediately after an AccelerateWP change, you should first determine which setting was changed last.

Proceed systematically:

1. Note the error.
2. Check which AccelerateWP function was last activated or modified.
3. Revert this setting to the previous state for testing purposes.
4. Clear the affected cache if necessary.
5. Test the same function again.

Do not change the theme, plugins, PHP version, and multiple performance settings at the same time.

Layout damaged after activation #

If the website is rendered incorrectly after a performance change, optimizations of static resources in particular may be relevant.

Check the most recently modified CSS and JavaScript settings respectively.

First, revert only this change and test again.

Menu or form no longer works #

If interactive elements stop working, you should investigate JavaScript-related optimizations in particular.

A typical error pattern can be:

Page looks correct
→ Menu does not respond
→ Form does not submit
→ Popup does not open

This is an indication that not only the visual representation may be tested.

Changes are not being displayed #

If you have edited a WordPress site, but the public website still shows the old content, a cache may be involved.

First, check whether the change was actually saved in WordPress.

Then specifically clear the relevant cache and check the page again.

Do not confuse browser cache and server cache #

Caching can take place at multiple levels.

Simplified:

WordPress / Application
        ↓
Performance / Server Cache
        ↓
Browser Cache
        ↓
Visitor

If old content appears, it must therefore first be clarified which layer is delivering it.

AccelerateWP and PHP version #

AccelerateWP optimizes a WordPress website, but it does not replace the correct PHP configuration.

At CURIAWEB, you generally manage a domain's PHP version via the MultiPHP Manager.

If WordPress or a plugin is not compatible with the PHP version being used, this issue should not be masked by performance settings.

AccelerateWP and PHP Limits #

PHP limits such as:

memory_limit
max_execution_time
upload_max_filesize

are also a separate configuration.

When an application reports a specific PHP memory error, that is not automatically an AccelerateWP issue.

We cover the most important limits under Set PHP memory limit, upload size, and execution time.

AccelerateWP and CloudLinux resources #

While AccelerateWP is part of the CloudLinux ecosystem, it is not the same as your hosting account's resource management.

CloudLinux can manage CPU, memory, or process resources at the hosting level, for example.

If an account regularly reaches a resource limit, the cause should be investigated independently of AccelerateWP.

We explain how to evaluate these values under Understanding CloudLinux Resource Usage in cPanel.

AccelerateWP and WordPress Cron #

Scheduled tasks on a WordPress website are also not the same as the page cache.

For example, if a scheduled process is not executed, the cache should not automatically be assumed to be the cause.

We handle server-side cron jobs under Create a cron job in cPanel and set the schedule correctly.

Temporarily disable AccelerateWP for troubleshooting? #

If an error has clearly only occurred after AccelerateWP activation or a specific optimization, a controlled comparison with the previous state can be useful.

Do not indiscriminately disable all performance components at the same time.

If possible, first revert only the last modified function and test again.

Why step-by-step troubleshooting is important #

Assuming you simultaneously change:

PHP version
Cache
CSS optimization
JavaScript optimization
WordPress plugin

and after that the website no longer works.

Then there are five possible starting points for troubleshooting.

If, on the other hand, you always change only one relevant area and then test, the cause can be isolated much more quickly.

Use error log for PHP errors #

If a website shows a PHP or server error after a change, the cPanel error log can provide important clues.

We explain the procedure under Read cPanel Error Log and find website errors.

AccelerateWP and 500 Internal Server Error #

One

500 Internal Server Error

can have numerous causes and is not automatically attributable to AccelerateWP.

However, if the error occurred immediately after a specific change, that change is naturally one of the first things you should check.

We cover systematic diagnosis under Fixing a 500 Internal Server Error.

Test AccelerateWP after WordPress updates #

After major changes to WordPress, your theme, or plugins, you should check important website functions.

This is especially true if components have been updated that affect frontend output, JavaScript, CSS, or dynamic functions.

In case of problems, AccelerateWP should not immediately be assumed to be the cause. The decisive factor is which component or change is chronologically related to the error.

Check AccelerateWP after theme change #

A theme determines a large part of the frontend structure of a WordPress website.

After a theme change, CSS and JavaScript files can change significantly.

Therefore, check afterwards:

• Layout
• Navigation
• responsive design
• interactive elements
• Cache behavior

Test AccelerateWP with WooCommerce #

With WooCommerce, after changes to caching or frontend optimization, you should test at least one typical shopping flow.

For example:

1. Open product page.
2. Add product to cart.
3. Open cart.
4. Modify quantity, if possible.
5. Go to checkout.
6. Verify that the correct cart and customer data are displayed.

A real order is not strictly necessary for a basic functional test.

AccelerateWP for membership and login websites #

For websites with logged-in users, personalized content can play an important role.

Therefore, test both as a logged-in user and without logging in.

A cache must not cause a user's personal content to be served to another user.

Performance optimization is not a one-time process #

A WordPress website changes over time.

New plugins, themes, external services, images, or features can affect performance.

A configuration that is suitable today should therefore be reviewed again after major technical changes.

Recommended procedure for activating AccelerateWP #

1. Check the WordPress website before making the change.
2. Check existing cache and performance plugins.
3. Document important existing settings.
4. Log in to cPanel.
5. Open Software → AccelerateWP.
6. Choose the correct WordPress installation.
7. Check the current AccelerateWP status.
8. Activate AccelerateWP for the desired website.
9. Check the WordPress integration.
10. Test the website first without any further changes.
11. Check the available performance options.
12. Activate additional optimizations step by step.
13. Test the website after every relevant change.
14. Test interactive features and forms.
15. Test WooCommerce cart and checkout.
16. Additionally, check the website without an active administrator login.
17. Compare the performance under conditions that are as similar as possible.

Recommended troubleshooting for AccelerateWP issues #

1. Determine when the error first occurred.
2. Note the last modified AccelerateWP setting.
3. Check if another cache or performance system is active in parallel.
4. Test the specifically affected website function.
5. Reset the last modified optimization as a test.
6. Update or clear the relevant cache as needed.
7. Test again without active WordPress login.
8. Check the error log for PHP errors.
9. Do not change the PHP version, theme, plugins, and other performance settings all at the same time.

Basic rule: Performance optimization should be measurable and controllable. Know the initial state, activate AccelerateWP, test functions, and make further optimizations step by step.

When should you contact CURIAWEB support? #

If AccelerateWP does not recognize a WordPress installation, if activation fails, or if an issue occurs after activation that you cannot clearly attribute to a specific setting, you should document the current state.

For an analysis, the following information is particularly helpful:

• affected domain
• WordPress version
• PHP version used
• whether AccelerateWP is activated
• which AccelerateWP setting was last changed
• further active cache or performance plugins
• exact error message
• which website function is affected
• whether the problem also occurs without a WordPress login

Do not transmit any passwords or other confidential access credentials.

Summary #

AccelerateWP is a CloudLinux solution for performance optimization of WordPress websites and is integrated directly into the cPanel hosting environment at CURIAWEB.

You can find AccelerateWP under Software → AccelerateWP. Select the correct WordPress installation there, check the existing status, and enable the optimization for the desired website.

Check before activation which cache and performance solutions are already being used within WordPress. Multiple systems with the same tasks should not be run in parallel in an uncontrolled manner.

After activation, test not only the homepage, but also navigation, forms, and other interactive features. In the case of WooCommerce, the shopping cart and checkout in particular are part of the functional test.

You should make further optimizations step by step. This way, in the event of a display or functional issue, you can trace which change is responsible for it.

AccelerateWP can deliver a technically sound WordPress website more efficiently, but it does not replace the diagnosis of faulty plugins, themes, PHP issues, or exhausted hosting resources.

Therefore, the most important rule is: Do not activate as many optimizations as possible at the same time – instead, optimize strategically, test, and keep the responsibilities of the individual performance functions clearly separated.