2026-08-14

Website errors your customers see and you never do

Website errors do not announce themselves.

Tamás sells furniture online. In March his revenue dropped 18 percent. Traffic stayed flat. Ad costs stayed flat.

He blamed the season. Then he blamed the ads. Then he raised his budget.

Eleven days later a customer emailed him. The checkout button did nothing on her iPhone.

A plugin update had broken it. Only on Safari. Tamás uses Chrome on a laptop. His site looked perfect every single morning.

The kind of broken you never notice

There are two ways a website breaks.

The loud way. The page will not load. Your phone rings within the hour. You fix it.

The quiet way. The page loads fine. It looks fine. One button does nothing on one browser.

Nobody calls you about the quiet way. People assume the problem is on their end. They close the tab and buy from someone else.

That is why quiet breakage is more expensive. It survives for weeks.

"The first principle is that you must not fool yourself, and you are the easiest person to fool."

Richard Feynman, Caltech commencement address, 1974

Your own browser fools you every day. It has your cache, your extensions and your settings. It is the least representative device you own.

Why these errors hide so well

Four things keep the problem out of sight.

• Your browser is not their browser. Safari, Firefox and old Android versions behave differently.
• Your cache is warm. You have loaded the site a hundred times. Your first-time visitor has not.
• Updates happen without you. A plugin, a theme or a payment script updates itself overnight.
• Other people's code runs on your page. Chat widgets, cookie tools, ad scripts and review widgets can all fail. When one of them dies, it can take your button with it. The same scripts also slow your page down.

That last one surprises people. You did not change anything. Someone else did.

What StatJolt does about it

StatJolt listens for errors in the visitor's browser. Not on your server. In the browser of the real person who is trying to buy.

When something breaks it records:

• The error message.
• The page it happened on.
• How many people hit it.
• The browser, the device and the operating system.
• When it first happened and when it last happened.

So Tamás would have seen one line. Safari, iPhone, /checkout, 340 people, started 4 March.

Eleven days of guessing become one sentence.

You can mark an error as solved. If it comes back within a week, StatJolt flags it as returned and emails you. That catches the fix that did not hold.

Still with me? Good, because the reporting is only useful if you actually look.

A two minute habit that pays for itself

Put this in your calendar every Monday morning.

1. Open your error list. Sort by number of people affected.
2. Ignore anything under ten people. Most of that is browser extensions and noise you cannot fix.
3. Look at the top three. Check which pages they sit on.
4. Escalate anything on a money page. Checkout, signup, contact and pricing come first.
5. Send the top item to whoever maintains the site. Message, page, browser. That is all they need.

Two minutes. Every week. This is the same rhythm we describe in analytics in 5 minutes a week.

What to send your developer

Most fix requests waste a day because they say "the site is broken".

Send these four things instead.

• The exact error message.
• The page address.
• The browser and device.
• The date it started.

That last one is the most valuable. It tells them what changed on that day.

Your developer stops hunting and starts fixing. It also protects you from paying for hours of guesswork.

Where StatJolt fits in

Error monitoring usually lives in a separate tool with a separate bill. StatJolt puts it next to your traffic numbers, because that is where you will actually see it.

It works without cookies. That way ad blockers do not remove the very visitors most likely to hit a problem. Technical people block trackers more than anyone else.

Your form is the other silent leak. That one has its own article: form abandonment and the field that costs you signups.

If you only read one box

Websites usually break quietly, on one browser, without anyone telling you. Your own device hides the problem because your cache and settings are not typical. Watch errors from real visitors, check the list weekly and treat anything on a checkout or signup page as urgent.

Back