Hello,

Thank you for reaching out to us.

I apologize for the inconvenience. We’ve recently implemented rate-limiting features — the current limit is 100 requests per 10 seconds. If you’re not logged in, please avoid attempting multiple sign-ins at once or clicking the “Sign In” button repeatedly.

Kindly try clearing your browser cache and let me know if the issue persists.

Tip for the future: Use Opera browser and built-in VPN - and using it visit our site.

Best regards,

Hello,

Thank you for your response. I understand the rate limiting you have in place. However, I would like to point out a specific case: https://www.joomshaper.com/page-builder/blocks.

This page loads a significant number of resources (images, scripts, CSS, fonts), and with the current limit of 100 requests per 10 seconds, it is too restrictive. Even during normal manual browsing, the page can exceed this threshold, resulting in Error 1015 on some browsers like Chrome.

Observations:

• Edge or a 4G connection do not trigger the error, likely due to slightly slower resource loading.
• Modern browsers (Chrome, Firefox) often preload resources, increasing the number of simultaneous requests.

Suggested solutions:

1. Increase the rate limit (for example, 200–250 requests per 10 seconds) to better support resource-heavy pages.
2. Exclude certain public/documentation pages from this rate limiting rule.
3. Enable “burst tolerance” to allow minor traffic spikes without triggering blocks.

These adjustments would allow normal users and developers to browse your resource-heavy pages without encountering blocks, while still maintaining effective protection against bots.

Thank you in advance for your consideration and feedback.

Best regards,