CASE STUDIES

What changed after 404 Guard was installed?

We’re preparing real website comparisons. Each one will show the traffic, when protection started and what happened to performance.

404 Guard shield

REAL RESULTS COMING SOON

See how a website copes while an attack continues.

A useful comparison doesn’t need the bots to disappear. We want to show whether the website does less work while the unwanted requests continue, and whether visitors can use the site more easily.

BEFORE

Traffic Gate traffic view

The missing-page requests and the load they were putting on the website before protection started.

INSTALLATION POINT

When protection was enabled

The time 404 Guard was switched on, plus the settings and any other changes made.

AFTER

Response times and website load

Comparable Traffic Gate views and 404 Guard results, with the limits of the comparison explained.

Supplied performance examples

These examples aren’t published customer case studies. They show supplied test figures, and results will vary with hosting, settings and load.

MISSING-PAGE RESPONSE

980 ms → 300 ms

Normal conditions, before and after 404 Guard.

20 REQUESTS IN A ROW

5,000 ms → 589 ms

Response-time example during repeated missing-page requests.

MISSING FILE

80 KB → 1 KB

Response-size example for a missing image or font.

Traffic and workload are different

404 Guard can reduce the work needed to answer a request. It doesn’t make bots stop sending requests. A drop in a plugin’s logged hits can also reflect where the request was handled.

Customer experiences

We’ll publish customer comments and website results here when we have permission to share them. There are no customer testimonials published yet.

See what changes on your website.

Start with the trial and keep a before-and-after record.