🔍 What This Article Covers
If your site audit is taking significantly longer than usual — for example, an hour when it normally completes in five minutes — this is called a performance regression. This is different from an audit that has always been slow. A sudden, dramatic increase in duration usually has a specific cause that can be identified and resolved. This article walks you through how to diagnose it.
⚠️ First: Confirm It Is a Regression, Not a One-Off
Before investigating, confirm the pattern is real and not an isolated incident.
- Check when the slow audit occurred and whether it has happened more than once recently.
- Compare the current audit duration with your last three to five completed audits to establish a clear baseline.
- Note whether any changes were made to your site or audit settings around the time the slowdown began.
If the duration has increased consistently and significantly (more than three times your normal baseline), proceed with the steps below.
📋 Step 1: Check Whether Your Site Has Grown
The most common reason for a legitimate audit slowdown is that your site now has substantially more pages to crawl than before.
- Open Site Metrics → Site Explorer (Site Explorer) from the left sidebar.
- Locate your domain and review the total indexed or crawled page count from your most recent audit report.
- Compare this with historical audit reports to see whether the page count has increased significantly.
A site that has grown from 200 pages to 2,000 pages will naturally take longer to audit. If this is the case, the increased duration is expected and no action is required beyond adjusting your expectations.
🛠️ Step 2: Review Your Crawl Settings
Misconfigured crawl settings can cause the crawler to work much harder than necessary, dramatically increasing audit time.
- Navigate to your site audit project settings.
- Check the crawl limit — if it has been increased recently, the audit will take longer.
- Check whether subdomains or external links have been enabled for crawling, as these expand the scope significantly.
- Verify that URL patterns you do not need audited (such as pagination, filtered URLs, or staging paths) are excluded using the URL exclusion settings.
Reset any settings that were changed unintentionally and re-run the audit to see whether duration returns to normal.
🌐 Step 3: Check for Site-Side Issues
If your crawl settings are unchanged and your page count is the same, the slowdown may be caused by your website responding more slowly than usual to the crawler's requests.
- Server response time: If your server is under heavy load or experiencing issues, every page request takes longer, multiplying across hundreds or thousands of pages.
- Redirects: A sudden increase in redirect chains (for example, after a site migration or plugin update) forces the crawler to follow multiple hops per URL.
- JavaScript rendering: If JavaScript rendering has been enabled in your audit settings and your site recently added heavy JavaScript pages, crawl time increases substantially.
- New redirect loops: Even a small number of pages caught in redirect loops can stall the crawler and inflate total audit time.
To check for these issues, run an independent speed test on your site (such as Google PageSpeed Insights or a server uptime monitor) and review your site's recent change log or deployment history for anything that may have affected response times or URL structure.
🔄 Step 4: Cancel the Stuck Audit and Re-Run
If the audit has been running for an unusually long time with no sign of completing, it may have stalled rather than simply being slow. In this case:
- Cancel the current audit run from within your site audit project.
- Wait two to three minutes before starting a new run.
- Monitor the new run for the first few minutes to confirm pages are being processed at a normal rate.
A stalled audit is different from a slow one — stalled audits show little or no progress in page count over a long period. Re-running typically resolves this.
📊 Step 5: Compare Audit Reports for Clues
Your completed audit reports contain information that can help identify what changed.
- Open your most recent completed audit report and note the total URLs crawled, total issues found, and any high volumes of specific issue types such as redirect chains or server errors.
- Compare these figures with a report from before the slowdown began.
- A spike in 3xx redirects, 5xx server errors, or total URL count between reports is a strong indicator of what is causing the increased duration.
✅ Quick Reference: Common Causes and Fixes
- Page count increased: Expected — audit takes longer as your site grows.
- Crawl limit raised in settings: Lower it back to your previous value.
- Subdomains or external links enabled: Disable if not needed.
- Server slowdown or high load: Investigate with your hosting provider and re-run when resolved.
- Recent site migration or URL restructure: Review and fix redirect chains.
- Audit stalled rather than slow: Cancel and re-run the audit.
💬 Still Seeing Unusually Long Audit Times?
If you have worked through all the steps above and your audit is still taking much longer than your normal baseline, our team can investigate whether there is a system-level issue affecting your project. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.