In short: Measure where the delay occurs before changing settings. Test from more than one network, compare a simple static file with the application, then check logs, resource usage, database work and external dependencies.
Define the symptom
- Is the whole site slow or only one page or action?
- Is the delay before the first byte or while downloading page assets?
- Does it affect every visitor, one location or only logged-in users?
- When did it start, and what changed shortly beforehand?
Run safe comparisons
- Test the site in a private browser window and from another connection.
- Load a small static file from the same domain.
- Check browser developer tools for slow images, scripts and third-party calls.
- Review web-server and application logs at the same timestamp.
- Check SiteWorx statistics and available resource indicators.
Common application causes
- Uncached dynamic pages or an ineffective page cache.
- Large unoptimised images, fonts or scripts.
- Slow database queries or damaged tables.
- Plugins, themes or remote APIs delaying the response.
- Background jobs overlapping or consuming resources.
- Unsupported PHP or application versions.
Change one thing at a time: Record a baseline and retest after each change. Disabling every plugin or clearing every cache at once can hide the cause and introduce a second problem.
When to contact support
Provide the affected URL, time and timezone, test location, whether a static file is also slow, any recent change, and relevant log entries. Do not send passwords. Virgo Networks can check the hosting platform, but application optimisation may require the site's developer.
Useful guidance
See the InterWorx guide for viewing web-server logs.
