Die gevaar van 'n pasgemaakte 404-bladsy

One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. Maar die SVE en vraggebruik was so hoog, met geen duidelike redes nie (die aantal besoekers was redelik). Egter: elk 404 het 'n groot SVE en bandwydteverbruik veroorsaak! 'n Toets is gedoen en die 404 was replaced by a flat and tiny 324 bytes HTML file. The result: the instance size could be divided by two, so halving all expenses (including the bandwidth).

When using a custom 404-page: one should not forget that even a simple dead link to an image will trigger an expensive and huge HTML code being returned to the browser, resulting in sluggish speeds for the visitors as well!

In other words: do not do it, even if it looks pretty to the eyes.