Rate Limiting

Speed limitation, API throttling, Throttling, Request limitation, Request limiting, Request limitation
Rate limiting limits the number of requests a user or system can send to your server within a certain amount of time. It protects your infrastructure from overload and abuse.

What is Rate Limiting?

Rate limiting is een techniek die het aantal verzoeken (requests) beperkt dat een gebruiker, IP-adres of API-client binnen een bepaalde periode naar je server mag sturen. Wordt de limiet overschreden, dan krijgt de afzender een foutmelding of een wachttijd. Zo voorkom je dat je server vastloopt door overbelasting, bots of kwaadwillenden.

How rate limiting works in practice

A rate limiter tracks how many requests a specific source (such as an IP address, API key, or logged-in user) makes within a time window. This time window can be a second, a minute, or an hour. Common strategies include the token bucket algorithm, in which each user is given a β€œbucket” of tokens that is slowly replenished, and the sliding window principle, which tracks a moving average. Once the limit is reached, the system temporarily blocks new requests or slows down the response. In a professional web development environment, you often configure this via the web server (such as Nginx or Apache), a CDN, or within the application code itself.

Why rate limiting became essential for modern websites

Rate limiting originated in the early years of the API economy, when services like Twitter and Google realized that uncontrolled usage could cripple their infrastructure. A single bot firing off thousands of requests per second can take down a server just as effectively as a DDoS attack. For Dutch ecommerce stores and SaaS platforms, this remains a pressing issue: credential stuffing attacks, scraping by competitors, and unintended loops in external integrations occur daily. Rate limiting is therefore not a luxury but a basic safeguard, comparable to authentication and authorization.

What rate limiting brings to your business

Voor een MKB-webshop met 5.000 bezoekers per dag voorkomt rate limiting dat een enkele bot je checkout-pagina 10.000 keer per minuut oproept en daarmee je hosting overbelast. Voor een B2B-platform met API-koppelingen naar klanten beschermt het je tegen onbedoelde loops in externe software die je server onnodig belasten. Daarnaast helpt het bij eerlijke verdeling: geen enkele gebruiker kan alle beschikbare capaciteit claimen. In de praktijk zien we bij WordPress-hostingtrajecten vaak dat rate limiting op serverniveau de uptime verbetert en de kosten verlaagt, omdat je minder overhead nodig hebt voor piekbelasting. Volgens Google Developers helpt rate limiting ook bij het beheersen van crawl budget, zodat zoekmachines efficiΓ«nter je site indexeren.

Applications of Rate Limiting

Rate limiting is not an abstract technique for large tech companies. Dutch SMEs with a website, ecommerce store or API also benefit daily from smart limiting. Below are four concrete situations where rate limiting makes the difference between a stable service and an overloaded server.

Protecting login pages from brute force attacks

A common attack is credential stuffing: criminals try thousands of username and password combinations on your login page. Without rate limiting, a bot can make millions of attempts in minutes. With rate limiting, you limit, for example, to 5 login attempts per IP address per minute. After the fifth attempt, the user gets a 15-minute temporary block. For legitimate users this is hardly noticeable, but for attackers it becomes economically unfeasible. In practice, we find with customers that this simple measure stops 99% of brute force attempts without affecting real visitors. Combine this with two-factor authentication for an extra layer of protection.

Fair distribution of API capacity for external links

Suppose you have an ecommerce store with an API that allows external systems (such as an ERP or marketing automation tool) to retrieve product data. Without rate limiting, one customer with a misconfiguration can flood your API with requests, thereby slowing down other customers. By setting a limit of, say, 1,000 requests per hour per API key, you guarantee fair distribution. This is especially relevant for B2B platforms and SaaS services. You communicate the limit upfront in your API documentation, so developers can configure their integrations accordingly. At Monkey Vision , we often configure this through API links with tools like n8n, setting rate limiting at both ends: at the source and at the destination.

Preventing scraping by competitors or bots

Ecommerce stores and comparison sites are regularly scrapped by competitors who automatically collect prices and product information. A scraper can request hundreds of pages in a short period of time, taxing your server and undermining your competitive advantage. Rate limiting based on IP address or user-agent limits this: for example, a maximum of 60 pages per minute per IP. Legitimate visitors never reach this, but a scraper is slowed down immediately. Note that limits that are too strict can also hamper Google bots. According to Google's crawler documentation, a limit of 1 request per second is safe for most sites. Combine rate limiting with a robots.txt and monitoring to find the balance.

Stability of checkout and payment pages during peaks

Black Friday, a product launch or a viral social media post can suddenly send thousands of visitors to your ecommerce store. Without rate limiting, your checkout process can get stuck because too many sessions are created at once. By putting rate limiting on critical endpoints (such as creating a shopping cart or starting a payment), you prevent your infrastructure from getting overloaded. For example, you can allow 10 checkout starts per minute per session, which is more than enough for normal users but prevents bots or bugs from crippling your system. Combined with professional ecommerce store development and scalable hosting, you'll keep control even during peaks.

When rate limiting is the right choice and when it is not

Rate limiting makes sense as soon as your website, API or ecommerce store faces automated traffic, external links or a growing number of users. It is not overkill for small sites: even a simple WordPress site benefits from basic protection against login attempts. However, you do have to be careful with too strict limits on public pages: if your homepage allows only 10 requests per minute per IP, users behind a shared corporate network or VPN may block each other. Therefore, always test with realistic scenarios and monitor your logs. For sites with little dynamic interaction (for example, a simple portfolio site with no login), you can limit rate limiting to specific endpoints such as contact forms.

Want to apply this to your business? Monkey Vision helps SME entrepreneurs with web design, SEO and smart digital solutions. Schedule a no-obligation meeting and find out what's possible for you.

Schedule an introduction

Frequently Asked Questions

No, rate limiting and a firewall are complementary layers of security with different goals. A firewall blocks traffic based on origin, protocol or known threats, while rate limiting limits the frequency of requests regardless of the source. You can have a trusted IP address that gets through the firewall, but if that address makes too many requests, rate limiting intervenes. In practice, you combine both: the firewall stops malicious traffic, and rate limiting prevents legitimate but overactive users or bugs from overloading your server. So for optimal security of your website or API, you need both, complemented by authentication and monitoring.

It depends on your traffic pattern and risk profile. For an ecommerce store with mainly Dutch visitors, a limit of 100 to 200 requests per minute per IP address is often sufficient for product pages, and 5 to 10 for login and checkout pages. Do you have an API for external links? Then use per-key limits of 1,000 to 5,000 requests per hour, depending on your infrastructure. Start conservatively and monitor your access logs: see legitimate users hitting the limit? Then increase gradually. Do you see a lot of blocked bots? Lower the limit for specific endpoints. When in doubt, a professional hosting setup with built-in rate limiting and real-time monitoring will help you find the right balance without trial-and-error on your live environment.

The most common mistake is too strict limits on public pages, causing users behind a shared IP address (such as an office network or mobile provider) to block each other. A second pitfall is applying rate limiting without clear error messages: visitors get a generic 429-error with no explanation or alternative. Always indicate when the limit resets. A third mistake is setting rate limiting but never monitoring: you then don't know whether legitimate users are suffering or whether bots are still breaking through. Solve this by setting up logging and alerting, for example through your hosting provider or a tool like Google Analytics. Finally, don't forget to exclude your own systems (such as monitoring tools or backup services), otherwise you're blocking yourself. Always test with realistic scenarios before going live.

The best approach depends on your current infrastructure and risks. Are you running a WordPress site or ecommerce store and want basic security quickly? Then start with rate limiting on login pages and forms via a plugin or your hosting provider. Do you have a custom application or API? Configure rate limiting at the server level (Nginx, Apache) or within your application code. Not sure where to start or what limits are realistic? Then schedule a free 30-minute security scan with Monkey Vision. We'll walk through your current setup, identify vulnerable endpoints and immediately give you three concrete areas for improvement you can implement this week. No sales pitch, just practical advice tailored to your situation. Contact us through our web development page to schedule an appointment.

About the author

Monkey Vision

Monkey Vision is a full-service digital agency at Nijmegen, specializing in web design, SEO, and AI automation for small and medium-sized businesses. The knowledge base has been compiled by our team of online strategists and is continuously updated based on current insights.

Publication date: 26-04-2026
Last update: 26-04-2026