Firewalls to block unwanted traffic coming from bad IP sources or having bad patterns; HTTP traffic managers to drop, redirect or rewrite requests having bad HTTP patterns; Bandwidth management and traffic shaping, in order to smooth down peaks in network usage. Using different domain names, IP addresses and computers to serve different kinds (static and dynamic) of content; the aim is to separate big or huge files (download.*) (that domain might be replaced also by a CDN) from small and medium-sized files (static.*) and from main dynamic site (maybe where some contents are stored in a backend database) (www.*); the idea is to be able to efficiently serve big or huge (over 10 – 1000 MB) files (maybe throttling downloads) and to fully cache small and medium-sized files, without affecting performances of dynamic site under heavy load, by using different settings for each (group) of web server computers, e.g.: https://download.example.com https://static.example.com https://www.example.com Using many web servers (computers) that are grouped together behind a load balancer so that they act or are seen as one big web server. Adding more hardware resources (i.e. RAM, fast disks) to each computer. Using more efficient computer programs for web servers (see also: software efficiency). Using the most efficient to process dynamic requests (spawning one or more external programs every time a dynamic page is retrieved, kills performances). Using other programming techniques and workarounds, especially if dynamic content is involved, to speed up the HTTP responses (i.e. by avoiding dynamic calls to retrieve objects, such as style sheets, images and scripts), that never change or change very rarely, by copying that content to static files once and then keeping them synchronized with dynamic content). Using latest efficient versions of HTTP (e.g. beyond using common HTTP/1.1 also by enabling HTTP/2 and maybe HTTP/3 too, whenever available web server software has reliable support for the latter two protocols) in order to reduce a lot the number of TCP/IP connections started by each client and the size of data exchanged (because of more compact HTTP headers representation and maybe data compression). Caveats about using HTTP/2 and HTTP/3 protocols . Market share Below are the latest statistics of the market share of all sites of the top web servers on the Internet by Netcraft. NOTE: (*) percentage rounded to integer number, because its decimal values are not publicly reported by source page (only its rounded value is reported in