How-To posts from the kant.au team.
A 99.9% uptime badge looks like proof nothing went wrong. It’s proof of something much narrower: that a server answered a request quickly enough, often enough. Whether the page it returned actually worked for the person waiting on it is a different question, and most uptime monitoring never asks it. What uptime monitoring actually measures […]
Read more →
A 100 on Lighthouse’s accessibility audit feels like a finished checklist. It’s closer to a first pass. The audit is automated, and automated testing can only catch what’s mechanically detectable, which is a smaller slice of real accessibility than the clean round number suggests. What Lighthouse’s accessibility score actually checks Lighthouse’s accessibility category runs on […]
Read more →
Every page a browser loads can, by default, be asked to hand a visitor’s camera, microphone, or location to any script running on it, including scripts your site didn’t write and doesn’t control. Almost nobody explicitly closes that door. What Permissions-Policy actually controls Permissions-Policy is a response header that declares which browser features and APIs […]
Read more →
Broken links don’t announce themselves. A page gets deleted, a URL structure changes, a typo makes it into a menu link, and the site keeps working for everyone who doesn’t happen to click that specific thing. Google, meanwhile, already knows exactly which links are broken, because it tried to follow them. Where broken links actually […]
Read more →
A sitemap makes a claim: these are your important pages, and here’s roughly when they last changed. Google doesn’t have to believe any of it, and increasingly, it doesn’t. When a sitemap contradicts what the site itself says, the cost isn’t abstract, it’s crawl budget spent on the wrong pages and money pages that never […]
Read more →
You changed a DNS record, and someone told you to wait 24 to 48 hours for it to propagate. That advice describes a real experience, a change that takes a while to show up everywhere, but the wrong mechanism behind it. Knowing the real one tells you exactly what to check instead of just waiting […]
Read more →
Auto-renew feels like a solved problem. You ticked a box years ago, the domain has renewed every year since, and you’ve never thought about it again. Domain expiry monitoring never actually stopped mattering, people just stopped thinking about it, which is exactly the condition under which auto-renew quietly fails and nobody notices until it’s too […]
Read more →
A client emails to say their invoices have been going to spam for two weeks. You check the domain. The SPF record looks fine on the surface, but a third-party tool was added three months ago and nobody updated the policy to include it. Every email sent from that tool has been failing authentication checks, […]
Read more →
The browser doesn’t give a warning. It gives a red screen. “Your connection is not private.” Most visitors leave immediately, and a percentage never come back. For the people managing the site, it’s always a surprise. It shouldn’t be. What SSL certificates actually do An SSL certificate encrypts the connection between a browser and a […]
Read more →
An agency gets a support call. A client’s email has been broken for three days. They dig in and find the MX records changed, quietly, a few days earlier. Not a hack, just an edit by someone at the client’s end who thought they were fixing something. Three days of missed business emails because no […]
Read more →