خطر 404 صفحه سفارشی

One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. اما CPU و مصرف بار بسیار زیاد بود, بدون هیچ دلیل مشخصی (تعداد بازدیدکنندگان معقول بود). با این حال: هر 404 باعث مصرف عظیم CPU و پهنای باند شد! آزمایشی انجام شد و 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!

به عبارت دیگر: do not do it, even if it looks pretty to the eyes.