Ang panganib ng isang pasadyang 404-pahina

One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. Ngunit ang paggamit ng CPU at load ay napakataas, nang walang maliwanag na dahilan (ang bilang ng mga bisita ay makatwiran). Gayunpaman: bawat isa 404 nag-trigger ng malaking pagkonsumo ng CPU at bandwidth! Isang pagsubok ang isinagawa at ang 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!

Sa madaling salita: do not do it, even if it looks pretty to the eyes.