Use this guide when:

  • The Performance menu does not appear in WordPress
  • Plugin settings do not save
  • Image optimization does not work as expected
  • CSS or JavaScript optimization breaks a page
  • Background processes appear delayed or stuck
  • The plugin cannot connect to EDGE
  • Cache purging does not update content as expected
  • You need to gather details before contacting Support

Start with these checks

Before changing settings, check the basics:

  1. Confirm the plugin is active under Plugins > Installed Plugins.
  2. Go to Performance from the WordPress admin sidebar.
  3. Check the plugin version.
  4. Review the most recent setting you changed.
  5. Open Performance > Background Processes and check for queued or running tasks.
  6. Open Performance > Logs and check for related entries.
  7. Test the affected page in a private browser window.

If the issue started after enabling an optimization, disable the most recent setting first and test again.

The Performance menu does not appear

The plugin is installed, but the Performance menu is missing from the WordPress admin sidebar.

Likely causes

  • The plugin is installed but not activated
  • Your WordPress user does not have administrator permissions
  • The WordPress admin dashboard needs to be refreshed
  • Another plugin is interfering with the admin menu

Resolution steps

  1. Go to Plugins > Installed Plugins.
  2. Confirm that Pressidium Performance is active.
  3. Refresh the WordPress admin dashboard.
  4. Confirm your user account has administrator permissions.
  5. Temporarily disable recently added admin-interface plugins if the menu is still missing.

Plugin settings do not save

You change plugin settings, but the changes are not saved.

Likely causes

  • Your user account does not have permission to update plugin settings
  • A security plugin is blocking the save request
  • A browser extension or cached admin session is interfering
  • Another plugin conflict affects the settings page

Resolution steps

  1. Confirm you are logged in as a WordPress administrator.
  2. Save the setting again and check for any visible error message.
  3. Refresh the page and confirm whether the setting changed.
  4. Try again in a private browser window.
  5. Temporarily disable recently added security or admin plugins if the issue started after a plugin change.

Settings save but do not affect the site

A setting appears saved, but the site does not show the expected optimization behavior.

Likely causes

  • The affected files have not been processed yet
  • Background processes are still queued or running
  • Another cache layer is serving older output
  • The file is excluded from optimization
  • The file is already minified or not eligible for optimization

Resolution steps

  1. Open Performance > Background Processes.
  2. Check whether tasks are queued, running, paused, or completed.
  3. Review the relevant exclusion list.
  4. Clear any active WordPress, plugin, origin, browser, or EDGE cache.
  5. Test the affected page again in a private browser window.

A page looks broken after enabling optimization

A page layout changes, styling is missing, or interactive elements stop working after enabling an optimization.

Likely causes

  • CSS minification affected a stylesheet
  • JavaScript minification affected a script
  • Concatenation changed the loading order of assets
  • A page builder, slider, form, popup, map, or checkout script needs to be excluded

Resolution steps

  1. Disable the most recent optimization you enabled.
  2. Test the affected page again.
  3. If the page works, re-enable the setting.
  4. Add exclusions for the affected CSS or JavaScript files.
  5. Test the page again after saving exclusions.

Important: Concatenation is a beta feature. If layout or script issues continue, keep concatenation disabled or use exclusions for affected files.

A script stops working after minification or concatenation

Menus, forms, sliders, popups, maps, checkout steps, or custom JavaScript behavior stop working.

Likely causes

  • A script does not work correctly after minification
  • Concatenation changes the script loading order
  • A third-party script should not be optimized
  • A dependency is loaded later than expected

Resolution steps

  1. Disable JavaScript minification and test the page.
  2. If the issue remains, disable JavaScript concatenation and test again.
  3. Identify the affected script.
  4. Add the script URL to the relevant exclusion list.
  5. Re-enable the optimization and test again.

A layout changes after CSS optimization

Styling changes, spacing is wrong, fonts are missing, or a page appears partially unstyled.

Likely causes

  • A stylesheet does not work correctly after minification
  • CSS concatenation changes the expected loading order
  • A page builder or theme stylesheet should be excluded
  • A third-party stylesheet should not be optimized

Resolution steps

  1. Disable CSS minification and test the page.
  2. If the issue remains, disable CSS concatenation and test again.
  3. Identify the affected stylesheet.
  4. Add the stylesheet URL to the relevant exclusion list.
  5. Re-enable the optimization and test again.

Images are not optimizing

Images remain in their original format or file size after enabling image optimization.

Likely causes

  • Image optimization is not enabled
  • Background processing has not completed
  • The image type is not selected for optimization
  • The image is excluded from optimization
  • The image was already optimized
  • The server image editor does not support the requested output format

Resolution steps

  1. Go to Performance > Image Optimization.
  2. Confirm image optimization is enabled.
  3. Confirm the image type is selected.
  4. Check whether the image is excluded.
  5. Open Performance > Background Processes and check task status.
  6. Review Performance > Logs for related entries.
  7. Confirm the selected image editor and output format are supported by the server.

Verification

The image is optimized or a modern format version is generated, depending on your settings.

Optimized images do not look correct

An optimized image looks blurry, distorted, or lower quality than expected.

Likely causes

  • The quality setting is too low
  • The source image is already heavily compressed
  • The selected output format does not suit the image
  • The original file was deleted and cannot be compared

Resolution steps

  1. Review the image quality setting.
  2. Increase quality if the output is too compressed.
  3. Confirm whether the original file is still available.
  4. Exclude the affected image if it must remain unchanged.
  5. Re-test image output after adjusting settings.

Background processes seem delayed or stuck

Optimization tasks remain queued or running for longer than expected.

Likely causes

  • The site has a large Media Library
  • Many CSS or JavaScript files are being processed
  • Server resources are limited
  • WP-Cron is delayed or not running as expected
  • Another plugin or server process is interfering

Resolution steps

  1. Open Performance > Background Processes.
  2. Check whether tasks are queued, running, paused, or completed.
  3. Allow large optimization jobs to finish before making more setting changes.
  4. Review Performance > Logs for related errors.
  5. Confirm that scheduled WordPress tasks are running normally.
  6. Reduce the number of changes being processed at once if possible.

The plugin cannot connect to EDGE

The plugin is active, but the EDGE connection does not complete.

Likely causes

  • The site has not been added to your EDGE account
  • API credentials are missing or incorrect
  • The credentials were copied with extra spaces or missing characters
  • The Client Secret was re-issued and the plugin still has the old value
  • The site URL or domain does not match the EDGE site entry

Resolution steps

  1. Confirm the site has been added to your EDGE account.
  2. Confirm you are using the correct EDGE credentials.
  3. Copy the credentials again and check for extra spaces.
  4. If the Client Secret was re-issued, update the plugin with the new value.
  5. Save the connection settings.
  6. Confirm the plugin status shows as connected.

Verification

The plugin connection status shows that WordPress is connected to EDGE.

Cache does not update after a WordPress change

You update content in WordPress, but visitors still see the old version.

Likely causes

  • The plugin is not connected to EDGE
  • The change did not trigger an automatic purge
  • The content is generated by a custom workflow
  • Another cache layer is serving old content
  • The browser is showing cached content

Resolution steps

  1. Confirm the plugin is connected to EDGE.
  2. Manually purge the affected content.
  3. Clear any WordPress, plugin, origin, browser, or EDGE cache.
  4. Test the page in a private browser window.
  5. If the content is generated by a custom workflow, use developer purge hooks.

Verification

The updated content appears after refreshing the page.

Manual purge does not update the page

You manually purge cached content, but the page still shows old content.

Likely causes

  • The browser is serving cached content
  • Another cache plugin is serving old output
  • Origin cache still contains old content
  • The wrong URL or content area was purged
  • The page is generated by a custom workflow

Resolution steps

  1. Purge the affected content again.
  2. Clear browser cache or test in a private window.
  3. Clear any active WordPress or plugin cache.
  4. Clear origin cache if applicable.
  5. Confirm the correct URL was tested.
  6. Check whether custom purge logic is needed.

Verification

The page shows the latest content after cache is cleared and the page is requested again.

Custom content is not purged as expected

Standard posts update correctly, but custom content, custom post types, imported content, or page-builder content does not purge as expected.

Likely causes

  • The content update happens outside standard WordPress publishing actions
  • A custom post type needs custom purge handling
  • A page builder stores content in a non-standard way
  • An external integration updates content without triggering expected hooks

Resolution steps

  1. Confirm whether standard WordPress content purges correctly.
  2. Identify how the custom content is updated.
  3. Review whether developer purge hooks are needed.
  4. Add custom purge logic for the affected workflow.
  5. Test the update again.

Logs show errors

The Logs tab shows plugin-related errors or warnings.

Likely causes

  • A file could not be processed
  • A background task failed
  • A server requirement is missing
  • A request to the EDGE API failed
  • Another plugin or server configuration is interfering

Resolution steps

  1. Open Performance > Logs.
  2. Identify the time and feature related to the error.
  3. Check whether the issue affects images, CSS, JavaScript, background processes, or EDGE integration.
  4. Retry the affected action if safe.
  5. Contact Support if the error repeats.

Best practices

  • Enable one optimization area at a time.
  • Test important pages after each change.
  • Use staging before production when possible.
  • Keep original images until optimized output is verified.
  • Use exclusions for affected files instead of disabling an entire feature.
  • Treat concatenation as beta and test it carefully.
  • Check Background Processes after enabling bulk optimization.
  • Review Logs before contacting Support.
  • Keep a note of the last setting changed before an issue appeared.
  • Avoid using multiple plugins that optimize or cache the same assets in conflicting ways.

Need help?

If the issue persists, contact Support and include:

  • Site URL
  • WordPress version
  • Plugin version
  • EDGE site name or domain, if the issue involves EDGE
  • The setting or action that caused the issue
  • Affected page URL
  • Time the issue occurred
  • Screenshot of the issue
  • Screenshot of the plugin settings or connection status, if relevant
  • Browser console errors, if available
  • Relevant log entries from Performance > Logs
  • Any files or URLs already excluded
  • Whether the issue affects one URL or the whole site
  • Any custom post type, page builder, import job, deployment process, or external integration involved

For plugin bugs or technical feedback, you can also use the official WordPress.org support forum or GitHub Issues.

Where to go next

After you troubleshoot the Pressidium Performance Plugin, return to the relevant setup or configuration guide.