Welcome to WebmasterWorld Guest from 220.127.116.11
I think I am being click bombed
IP Ranges alone are not server CPU intensive, and done properly in htaccess cause little delay in serving pages.
With htaccess files @ sizes that most noobs would consider extreme, the delay is in milliseconds.
The server does process the htaccess directives before delivering the page to the user, but as wilderness said, it is not a significant issue unless it contains complex directives such as database redirects and other resource intense rules. If you just have simple rules and IP blocks (within a reasonable amount) the hit on server response to deliver the page to the user is not an issue. There are many more things to worry about when it comes to server response time.
With a VPS, the IP blocks are done differently and would not be an issue anyway.
IP ranges are not purely regionally specific. Example, China uses many ranges assigned to USA IP blocks. If your objective is to block non-English speaking users, IPs are not a good thermometer. You'll have to be more surgical. Besides, English is the second language for most countries nowadays.
my main interest was blocking all non-English speaking countries (so 90% of the world's countries). I was told doing so would be crazy and would slow down the page loading of my site dramatically.
Lastly, I have read in other forums that using IP ranges is not optimal to block desired countries since not all countries are restricted to certain IP ranges and you could be blocking IPs that belong to USA and UK
I've provided multiple instances for beginners on denying key Class A's as preliminary restrictions.
[edited by: Andy500 at 7:43 pm (utc) on Apr 14, 2014]
(can we allow Europe as a continent but then block Eastern Europe with further blocking rules, for example?).