This article will assist in troubleshooting sluggish performance issues when experiencing a slow Pull Zone after integrating a website with the CDN.
There are plenty of tools available to help troubleshoot why a website is running slowly. a third-party website like Pingdom and WebPagetest can be used, or a browser extension like FireBug for Firefox. Regardless of which method is chosen, run a test on the website and look for any files that return one of the following HTTP status codes: 404, 403, 304, 502.
- HTTP 302: The file has been moved. This is typically due to a redirection specified in the server's .htaccess file. Check the file and remove the redirection.
- HTTP 403: The user do not have permission to view the requested file. Check the file and directory permissions on the origin server to ensure it is able to be viewed on the web.
- HTTP 404: The requested file is not found. Check the origin server to make sure the file exists, and check the site's source code to ensure the file is being linked properly.
- HTTP 502: Please visit the 502 troubleshooting page for more help.
Another common reason for a slow Pull Zone is when the origin server is blocking traffic from the CDN as a part of mitigating a distributed denial of service (DDoS) attack. Our technical support staff can determine if this is the case, and if so they are available to assist with whitelisting MaxCDN IP ranges.
We hope this article was helpful and as always, If there are any questions or concerns about any of the topics mentioned in this article, please feel free to reach out to support - we are available 24/7 by chat or email!