Nevarnost 404 strani po meri
One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. Vendar sta bila poraba procesorja in obremenitve tako visoka, brez očitnih razlogov (število obiskovalcev je bilo razumno). Vendar: vsak 404 sprožil veliko porabo procesorja in pasovne širine! Opravljen je bil test in 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!
Z drugimi besedami: do not do it, even if it looks pretty to the eyes.
