Use this guide to troubleshoot slow site performance when using Pressidium EDGE.

Slow performance can have several causes, including cache misses, CDN delivery issues, slow origin responses, large images, render-blocking assets, WordPress plugin conflicts, third-party scripts, or traffic spikes. This guide helps you identify the likely cause and decide which area to investigate next.

If your site used to perform well but has become slower over time or after a change, start with Performance Degradation.

When to use

Use this guide when:

  • Pages take longer than expected to load
  • Time to First Byte (TTFB) is high
  • Server response time is high
  • Static assets load slowly
  • Images slow down the page
  • Cache hit rate appears low
  • Some pages are fast but others are slow
  • The site is slow from specific locations, networks, browsers, or devices
  • External performance tools report poor results
  • You are not sure whether the issue is cache, CDN, WordPress, frontend, origin, or traffic-related

Symptoms

Common signs of slow site performance include:

  • Slow page load: Pages take several seconds to load.
  • Slow TTFB: The browser waits too long before receiving the first response.
  • Slow server response: The origin takes too long to generate dynamic responses.
  • Slow asset loading: CSS, JavaScript, fonts, images, or other assets load slowly.
  • Poor Core Web Vitals: Metrics such as LCP, CLS, FCP, TBT, or TTFB are worse than expected.
  • Inconsistent performance: The site is fast sometimes but slow at other times.
  • Location-specific slowness: The site is slow from certain regions or networks.
  • Page-specific slowness: Only specific pages, templates, or endpoints are affected.

Quick checks

Start with these checks before making changes:

  1. Check whether the issue affects all pages: Test the homepage, key landing pages, dynamic pages, and WordPress admin separately.
  2. Test as a logged-out visitor: Logged-in WordPress sessions often bypass cache by design.
  3. Check cache behavior: Confirm whether public pages are served from cache or repeatedly reaching the origin.
  4. Review Performance Analytics: Look for high response times, high-impact paths, and unusual request volume.
  5. Review Cache Analytics: Check cache hit rate, cacheable hit rate, misses, and bypasses.
  6. Review Traffic Analytics: Look for traffic spikes, top URLs, top IPs, referrers, countries, and error patterns.
  7. Run a Site Audit: Audit affected URLs to identify frontend, asset, and Core Web Vitals issues.
  8. Check recent changes: Review plugin, theme, cache, DNS, firewall, origin, image optimization, or deployment changes.

Common causes

Cache issues

Issue: Public pages are not being served from cache as expected.

Cache issues can increase origin load and make pages slower, especially for high-traffic pages.

What to check:

  • Cache hit rate
  • Cacheable hit rate
  • Repeated cache misses
  • Cache bypasses
  • Cache exclusions
  • Cookie-based exclusions
  • Query strings
  • Recently purged cache
  • WordPress plugins setting no-cache headers
  • Dynamic pages that should bypass cache

What to do:

  • Review cache status and cache analytics.
  • Test the page as a logged-out visitor.
  • Check response headers with browser Developer Tools or curl -I.
  • Review URL path and cookie-based cache exclusions.
  • Confirm whether the affected page should be cached.
  • Review Cache Not Working for detailed cache troubleshooting.

CDN or EDGE delivery issues

Issue: Traffic or assets do not appear to be served efficiently through Pressidium EDGE.

What to check:

  • Whether DNS points to EDGE
  • Whether the domain is attached to the correct site
  • Whether assets use the expected domain
  • Whether requests return from the expected route
  • Whether static assets are cached
  • Whether some locations behave differently
  • Whether the issue affects HTML, images, CSS, JavaScript, or all content

What to do:

  • Confirm the site is routed through Pressidium EDGE.
  • Inspect response headers for affected pages and assets.
  • Test from another browser, device, network, or external testing location.
  • Review traffic and cache analytics.

Slow origin or WordPress response

Issue: The origin or WordPress application takes too long to generate responses.

This is often visible as high TTFB or high server response time, especially on uncached dynamic pages.

What to check:

  • Server response time
  • High-impact paths
  • Dynamic endpoints
  • WooCommerce cart or checkout pages
  • LMS, membership, account, or logged-in pages
  • admin-ajax.php
  • REST API requests
  • Search pages
  • Form submissions
  • Slow database queries
  • Plugin or theme overhead
  • External API calls

What to do:

  • Use Performance Analytics to identify slow paths.
  • Check whether the slow paths are cacheable.
  • Review plugins, theme code, custom queries, and external calls.
  • Reduce unnecessary dynamic requests.
  • Optimize or cache safe public content.
  • Contact Support if server response time remains high and the cause is unclear.

Image and media issues

Issue: Large, unoptimized, broken, or slowly served images increase page load time.

What to check:

  • Large image files
  • Unoptimized uploads
  • Too many images on one page
  • Images loaded above the fold
  • WebP or AVIF delivery
  • Image optimization settings
  • Lazy loading behavior
  • Missing or stale image cache
  • Image request status codes
  • Image response time

What to do:

  • Review image requests in browser Developer Tools.
  • Optimize large images.
  • Use modern formats where appropriate.
  • Check image optimization settings in the Pressidium Performance Plugin.
  • Test important pages after changing image optimization settings.
  • Review Images Not Loading if images are broken, stale, slow, or affected by optimization settings.

Frontend asset issues

Issue: CSS, JavaScript, fonts, page builders, or third-party scripts slow down rendering.

What to check:

  • Render-blocking CSS or JavaScript
  • Large JavaScript bundles
  • Unused CSS
  • Too many fonts or font weights
  • Layout shifts
  • Heavy page builder output
  • Large DOM size
  • Ads, tracking scripts, chat widgets, and embeds
  • Tag manager changes
  • Mobile vs desktop differences

What to do:

  • Run a Site Audit for the affected URL.
  • Review browser waterfall data.
  • Remove unused scripts where possible.
  • Defer or delay non-critical scripts where safe.
  • Optimize font loading.
  • Test mobile and desktop separately.

WordPress plugin or theme conflicts

Issue: A plugin or theme adds overhead, disables cache, modifies headers, loads heavy assets, or creates slow dynamic requests.

What to check:

  • Recently added plugins
  • Recently updated plugins
  • Caching plugins
  • Optimization plugins
  • Security plugins
  • Page builders
  • WooCommerce extensions
  • LMS or membership plugins
  • Form plugins
  • Plugins that set cookies for all visitors
  • Plugins that load third-party scripts globally

What to do:

  • Review changes made before the slowdown started.
  • Disable only suspected plugin features where safe.
  • Test one change at a time.
  • Avoid disabling production-critical plugins without a rollback plan.
  • Review WordPress Plugin Conflicts if a plugin may be affecting performance, cache, or asset delivery.

Traffic spikes or abnormal traffic

Issue: Traffic volume increased, or abnormal traffic is creating excessive load.

What to check:

  • Total requests
  • Top URLs
  • Top IPs
  • Top countries
  • Referrers
  • Bot-like traffic
  • Spikes during campaigns
  • Increased 404, redirect, or error responses
  • More uncached dynamic requests than usual

What to do:

  • Review Traffic Analytics.
  • Identify high-volume URLs and request sources.
  • Confirm whether the traffic is legitimate before blocking it.
  • Review cache coverage for high-traffic public pages.
  • Contact Support if traffic appears abnormal or difficult to classify.

Third-party services

Issue: External scripts, APIs, embeds, or services slow down page loading.

What to check:

  • Analytics scripts
  • Ads
  • Tracking pixels
  • Chat widgets
  • CRM forms
  • Payment gateways
  • Social embeds
  • External fonts
  • External API calls
  • Tag manager changes

What to do:

  • Review the browser waterfall.
  • Remove unused third-party scripts.
  • Load scripts only on pages that need them.
  • Defer or delay non-critical scripts where safe.
  • Add timeouts or fallbacks for slow API calls.
  • Contact the third-party provider if their service is slow or unreliable.

Diagnostic steps

Step 1: Define the scope

Start by identifying what is actually slow.

Check:

  • Whether all pages are slow or only specific pages
  • Whether the issue affects logged-out visitors, logged-in users, or both
  • Whether the issue affects desktop, mobile, or both
  • Whether the issue affects all regions or specific locations
  • Whether the issue is constant or intermittent
  • Whether the issue started after a specific change

Write down affected URLs, test times, and the user experience you are trying to improve.

Step 2: Review Performance Analytics

Open the site in the Pressidium Dashboard and go to Performance -> Performance Analytics.

Check:

  • Request volume
  • Total request time
  • Server response time
  • High-impact paths
  • Slow hours or traffic spikes
  • Paths with high request count and high response time
  • Whether the slowest paths are public pages, dynamic pages, APIs, admin requests, or assets

Use this step to identify where the slowdown is concentrated.

Step 3: Review Cache Analytics

Open the site in the Pressidium Dashboard and go to Performance -> Cache Analytics.

Check:

  • Cache hit rate
  • Cacheable hit rate
  • Cache hits
  • Cache misses
  • Cache bypasses
  • Top URLs by cache status
  • Whether important public pages are being cached
  • Whether dynamic pages are correctly bypassing cache

If cache hit rate is low or cacheable pages are repeatedly missing cache, continue with Cache Not Working.

Step 4: Review Traffic Analytics

Open the site in the Pressidium Dashboard and go to Traffic -> Traffic Analytics.

Check:

  • Total requests
  • Top requested URLs
  • Top countries
  • Top IPs
  • Top referrers
  • Response status breakdown
  • Cache status breakdown
  • Traffic spikes or unusual request patterns

Use this step to identify whether traffic volume or abnormal traffic is contributing to the slowdown.

Step 5: Run a Site Audit

Run a Site Audit for the affected page.

Check:

  • TTFB
  • LCP
  • FCP
  • TBT
  • CLS
  • Page weight
  • Number of requests
  • Large images
  • Render-blocking resources
  • JavaScript execution time
  • Mobile vs desktop results

Audit more than the homepage. Test important landing pages, product pages, checkout, login, LMS, membership, forms, and other business-critical URLs.

Step 6: Test with browser Developer Tools

Open the affected page in a browser and inspect the Network tab.

Check:

  • Which request is slowest
  • Whether the main HTML request has high TTFB
  • Whether images, CSS, JavaScript, or fonts are slow
  • Whether requests are blocked or redirected
  • Whether third-party scripts are slow
  • Whether assets return 404, 403, redirect, or 5xx responses
  • Whether the browser is loading resources from cache

This helps separate backend, cache, asset, and frontend rendering problems.

Step 7: Test with command-line requests

Run:

curl -I https://example.com/

Repeat the request:

curl -I https://example.com/

Compare the first and second response.

Check:

  • HTTP status code
  • Redirects
  • Response headers
  • Cache-related headers
  • Whether the response changes after repeated requests
  • Whether the page behaves like a public cacheable page or a dynamic response

Use the exact affected URL instead of testing only the homepage.

Step 8: Compare with external tools

Use external tools to understand the visitor experience.

Useful tools include:

  • PageSpeed Insights
  • WebPageTest
  • GTmetrix
  • Browser Developer Tools
  • Uptime or synthetic monitoring tools

External tools are useful for frontend and real-user style testing, but they should be compared with EDGE analytics to understand whether the bottleneck is cache, origin, asset delivery, frontend execution, or third-party services.

Solutions

Improve cache behavior

  1. Review Cache Analytics.
  2. Check whether public pages are being served from cache.
  3. Review cache exclusions.
  4. Check whether plugins are setting no-cache headers or cookies.
  5. Purge affected URLs if stale content is involved.
  6. Retest as a logged-out visitor.
  7. Review Cache Not Working if cache behavior still looks wrong.

Improve EDGE or CDN delivery

  1. Confirm the domain points to Pressidium EDGE.
  2. Check whether affected requests use the expected domain.
  3. Review response headers and cache behavior.
  4. Test from another region, network, or external testing tool.
  5. Purge stale assets if needed.

Reduce slow origin responses

  1. Identify high-impact slow paths in Performance Analytics.
  2. Check whether those paths are cacheable or dynamic.
  3. Review plugins, theme code, custom queries, and external API calls.
  4. Reduce unnecessary plugins or plugin features.
  5. Optimize slow database-heavy pages.
  6. Cache public anonymous pages where safe.
  7. Avoid caching private, transactional, account, cart, checkout, LMS, membership, or logged-in pages.
  8. Contact Support if origin response time remains high.

Optimize images and media

  1. Identify large or slow images.
  2. Check image requests in browser Developer Tools.
  3. Use the Pressidium Performance Plugin image optimization settings where appropriate.
  4. Enable or review modern image formats such as WebP or AVIF if supported and tested.
  5. Avoid uploading unnecessarily large images.
  6. Purge stale image cache if old images appear.
  7. Review Images Not Loading if image delivery or optimization appears to be the issue.

Reduce frontend overhead

  1. Run a Site Audit for affected pages.
  2. Review render-blocking CSS and JavaScript.
  3. Remove unused scripts and styles.
  4. Defer or delay non-critical scripts where safe.
  5. Review font loading.
  6. Reduce heavy page builder sections where possible.
  7. Review layout shifts from images, ads, embeds, or dynamic content.
  8. Test mobile and desktop separately.

Review plugins and themes

  1. Check recent plugin and theme changes.
  2. Review plugins that load assets on every page.
  3. Review cache, optimization, security, page builder, WooCommerce, LMS, membership, and form plugins.
  4. Disable only suspected features where safe.
  5. Test one change at a time.
  6. Clear relevant caches after changes.
  7. Keep notes on what changed and what improved.

Address traffic spikes

  1. Review Traffic Analytics.
  2. Identify top URLs, IPs, countries, and referrers.
  3. Confirm whether the traffic is legitimate, bot-like, or suspicious.
  4. Improve cache coverage for high-traffic public pages.
  5. Review firewall or bot protection settings if traffic appears abusive.
  6. Contact Support if the traffic pattern requires deeper analysis.

Address third-party bottlenecks

  1. Review the browser waterfall.
  2. Identify slow third-party scripts or APIs.
  3. Remove unused third-party scripts.
  4. Load scripts only on pages that need them.
  5. Defer or delay non-critical scripts where safe.
  6. Add timeouts or fallbacks for slow API calls.
  7. Test again after each change.

Best practices

  • Monitor performance regularly.
  • Review Performance Analytics after major changes.
  • Review Cache Analytics after cache or plugin changes.
  • Review Traffic Analytics after campaigns or traffic spikes.
  • Keep cache exclusions narrow and intentional.
  • Cache public anonymous pages where safe.
  • Do not cache private, user-specific, or transactional pages.
  • Optimize images before upload.
  • Test image optimization changes on important pages.
  • Avoid unnecessary third-party scripts.
  • Keep plugins and themes lean.
  • Test mobile and desktop separately.
  • Run Site Audits for more than the homepage.
  • Document performance-related changes.

Troubleshooting checklist

  • Identified the affected URLs
  • Confirmed whether the issue affects all pages or specific pages
  • Tested as a logged-out visitor
  • Tested in a private browser window
  • Tested from another browser, device, or network
  • Reviewed Performance Analytics
  • Reviewed Cache Analytics
  • Reviewed Traffic Analytics
  • Ran a Site Audit for affected pages
  • Checked cache hit rate and cacheable hit rate
  • Checked for cache misses or bypasses
  • Checked high-impact paths
  • Checked top requested URLs and traffic spikes
  • Checked browser Developer Tools
  • Checked response headers with curl -I
  • Checked image size and image delivery
  • Reviewed Pressidium Performance Plugin settings if image or optimization features are involved
  • Reviewed recent plugin, theme, deployment, cache, DNS, firewall, or origin changes
  • Reviewed third-party scripts and external services
  • Tested after each change
  • Collected diagnostic information for Support if the issue persists

When to contact Support

Contact Pressidium Support when:

  • Performance issues persist after troubleshooting
  • Server response time remains high
  • Cache behavior looks wrong and you cannot identify why
  • Traffic spikes or request patterns look abnormal
  • The site is slow for many users or regions
  • A high-impact path is slow without a clear cause
  • You need help interpreting Performance Analytics, Cache Analytics, Traffic Analytics, or Site Audit results
  • The issue affects a live production site

When contacting Support, include:

  • Site name
  • Affected domain
  • Affected URLs or paths
  • When the slowdown started
  • Whether the issue is constant or intermittent
  • Whether the issue affects all users or specific users, regions, devices, or browsers
  • Performance Analytics screenshots or exports
  • Cache Analytics screenshots or exports
  • Traffic Analytics screenshots or exports
  • Site Audit results, if available
  • Browser Developer Tools findings
  • Response headers from curl -I, if available
  • Recent plugin, theme, DNS, cache, firewall, origin, deployment, or Performance Plugin changes
  • Steps already taken

Where to go next