Understand which cache layer is serving a page before clearing or changing every performance setting.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- List the active cache layers: WordPress plugin, PHP opcode, browser, CDN or proxy, and any application-specific object cache.
- Create a backup and record current plugin settings before changing cache storage, minification or database optimisation.
- Purge the WordPress page cache first and test in a private browser window with a unique query string.
- Purge an external CDN or proxy only when it is known to cache the affected URL.
- Exclude account, basket, login and other personalised paths from full-page caching.
- Enable minification or combination one feature at a time and test forms, menus, accessibility, mobile layouts and administration pages.
- Use response headers and page source to confirm which cache served the result rather than repeatedly purging without evidence.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| WordPress shows a critical error or blank page. | A plugin, theme, PHP version or exhausted resource caused a fatal error. | Check the PHP error log, disable only the last changed component and restore a known-good copy if the administration area is unavailable. |
| The site works until cache is cleared or a plugin updates. | Generated cache, stale object data or incompatible code is masking the underlying fault. | Test with caching disabled on a staging copy, update one component at a time and confirm PHP compatibility before re-enabling cache. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Troubleshoot a blank or white page
- Resource limit errors and slow sites
- Diagnose a WordPress plugin or theme conflict
- Change PHP settings
- Configure WordPress scheduled tasks and wp-cron
Last reviewed: 2026-07-18.
