Our Website Passed Its Health Inspection. The Clipboard Said Otherwise.
A monthly site sweep reported zero errors and listed five violations five lines lower. What the filter was looking for, the eleven false alarms, and the one real finding that had to be fixed in order.
- → What a monthly website inspection actually checks, told like the restaurant version every New Yorker knows
- → How a report said "zero errors" at the top and listed five violations at the bottom, and why the zero was wrong
- → Why our own bouncer made the inspector write "closed," and what to do about false alarms
- → The one real finding, the order it had to be fixed in, and the ten-minute version for your own site
The Grade in the Window
Every New Yorker knows the letter in the restaurant window. Since 2010 the City has required restaurants to post a grade from their sanitary inspection: 0 to 13 points is an A, 14 to 27 is a B, 28 or more is a C, and the card has to go where people walking by can see it. It's the only test in New York where you want a low score.
Nobody reads the inspection report. They read the letter.
That's the problem with a website too. Every tool that checks a site hands you a grade, and the grade is what you remember. The report, the clipboard with the actual findings on it, is what tells you whether the grade means anything. In August we ran the first of our monthly inspections on our own site, ingeniumvector.com, and the clipboard turned out to be more interesting than the grade.
If you've watched Kitchen Nightmares, you know the scene. Gordon Ramsay doesn't look at the sign out front. He opens the walk-in fridge the owner stopped opening years ago. For one afternoon in August we were the owner, and the sweep was the walk-in.
What the Inspector Checked
The rule for the sweep is findings first, no fixing during the inspection. You don't rewire the kitchen during dinner service. You write it down, and you fix it later, in the right order.
The basics came back clean. All 68 pages in the site's map answered the door. Every page had one title, one description and one main headline, with no duplicates of any of them. Every image had a text description for screen readers. Nothing loaded over an insecure connection. Ten pages rendered in a real browser with no script errors. If that were the whole report, it'd be an A, and you could stop reading.
It wasn't the whole report.
The Clipboard Said Zero. The Clipboard Also Said Five.
Here's the one I keep thinking about.
The tool that watches for errors while a page loads works by scanning the browser's messages for words like "refused," "blocked," "failed" and "error." It ran on our contact page and reported zero errors. Clean. Next line.
Five lines lower in the same output sat five messages from our site's own security policy. Every one of them was worded "violates." Not "error." Not "failed." "Violates." The filter wasn't looking for that word, so the filter said zero, and the zero was sitting on top of five things worth reading.
Google's own documentation for the same kind of check spells out that browser messages come in levels, verbose, info, warning and error, and that an error means something on the page needs fixing. Our filter had learned a few of the words and was blind to the rest. A clipboard that says "no violations" on the top line and lists five at the bottom.
We caught it for one reason, and it wasn't cleverness. The zero disagreed with a number we'd already measured a different way, and somebody went and looked. That's the whole method, and it's the same one that caught a backup check passing on the wrong definition of success. When two instruments disagree, the interesting one is the one that says everything's fine. It's also why we checked by hand whether AI engines cite us instead of trusting a dashboard that couldn't say.
The Bouncer Wouldn't Let the Inspector In
Second finding, and this one's a false alarm with a lesson in it.
Our site has a bouncer. A firewall turns away the generic testing tools that scrape websites all day, while letting real uptime monitors and Google's own crawler through. Good policy. The side effect is that any quick check of the kind you'd run from a laptop gets turned away at the door and reports the site as down.
The site wasn't down. The inspector just couldn't get in, so he wrote "closed." If you've ever had a monitoring tool insist your site is offline while customers were happily buying things, this is one of the reasons why. Before you panic about an outage, find out whether the tool that reported it was ever allowed inside.
Eleven Reflections
The sweep flagged 11 more things before anything was called a defect, and all 11 got thrown out.
Ten were accessibility warnings about checkboxes that were, on inspection, labeled correctly. The tool was wrong. One was an artifact of the checker's own file naming, which is the inspector tripping over his own clipboard. Eleven findings, zero problems. A report is only as good as the person willing to say "that one's a reflection" eleven times in a row, and to write down why each time, so the next inspector doesn't re-find them all.
The One Real Finding, and the Order
There was one real problem. It's a security setting, and I'm not going to describe it in detail on the public internet, which is what you'd want from anyone running your site.
What I will tell you is the part that matters for your business: the fix had an order. Done the obvious way, it would've broken the contact form and the same form where it appears on two other pages, which is to say the three places a customer reaches us. The right order was to adjust the setting first, watch what it reported, and only then switch it fully on. Adjust, watch, switch.
That order is the lesson. A security fix that takes down your contact form isn't a fix, it's an outage with a good excuse. Whoever does yours should be able to tell you the order before they start, and who owns it if it breaks.
Everything else on the clipboard was low: a few titles and descriptions running long, and some internal links pointing at an address that forwards to another one. Housekeeping. It's on the list.
The Dishwasher Set Off the Alarm
One more, from five days before the sweep, and it's here because it's the same lesson in miniature.
A speed tool's "best practices" score for our site had dropped from 82 to 75. The cause turned out to be our own new analytics tool, the one we'd switched to three weeks earlier, whose server our own security policy was reporting. Our dishwasher was setting off our own alarm. A one-line change put the score back to 82, the speed number sat at 92 the whole time, and we ran the same version of the tool before and after so the comparison was real.
Nothing was broken. Two of our own systems just hadn't been introduced to each other.
The Ten-Minute Version
You don't need our tooling to do this. You need a calendar and the willingness to read past the grade.
Once a month, open your site on your phone and tap every link in the menu. Then run Google's free speed test and, instead of reading the score, scroll to the list underneath it and read the first five items. Then ask whoever runs your site one question: when the last check said "no errors," what word was it looking for?
The grade in the window is for the people walking by. The clipboard is for you.
When did anyone last read the bottom of your website's report, not just the score at the top?
Smatthew Cohen is an AI Operator and the founder of Ingenium Vector. Before that he ran a sales firm called Tortoise & Rooster for twelve years, helping boutique manufacturers who couldn't afford the agencies that were ignoring them anyway. He builds things now.