Somewhere along the way, the browser quietly became the operating system that matters. Email, the CRM, the HR portal, the ticketing system itself: all tabs. Which means “the website is broken” is now a load-bearing category of help desk ticket, and the good news is that browser tickets yield to a smaller toolkit than almost any other kind.
The one-minute test that splits every ticket
Start with the diagnostic that does the most work per second in all of support: open the same site in an incognito or private window. Incognito is not privacy magic; what it actually is, for a tech, is a browser with amnesia, no cache, no cookies, and most extensions switched off.
That gives you a clean split. Works in incognito: the site is fine, the network is fine, and the problem lives in the normal profile’s stored state or extensions, which you can now clear or disable with confidence instead of superstition. Broken in incognito too: stop blaming the browser, because the trail now points at the site itself, the connection, or something the network is doing. A second browser makes the same cut when incognito is unavailable, since Chrome and Edge keep entirely separate state, and one working while the other fails convicts the failing one’s profile.
One minute, no settings touched, and half the suspect list is gone. If a single habit separates techs who close browser tickets from techs who flail at them, it is this one.
Why “clear the cache” is not superstition
Every user has been told to clear their cache, and almost none have been told why, which makes it feel like IT folklore. The mechanism is real. The cache is the browser’s stash of already-downloaded page pieces, scripts, styles, images, kept so the next visit loads fast. When a site ships an update, the browser is supposed to notice which saved pieces went stale. Sometimes it does not, and the result is a chimera: new page, old scripts, and things half-work in ways that look insane, buttons that do nothing, layouts collapsed, yesterday’s data over today’s labels.
Clearing the cache deletes the stale stash and forces fresh copies of everything, which is why the dumb-sounding fix genuinely repairs the weird-looking symptom. Cookies are the stash’s sibling with different contents, sign-ins and site settings, so cookie problems wear a different costume: endless login loops, or a site that greets you with “session expired” the moment you arrive. Same cure, with the side effect that clearing cookies signs the user out of things, which you warn them about first, because surprise sign-outs generate their own tickets.
Extensions round out the stored-state suspects. Users accumulate them like fridge magnets, and a bad or broken one can slow every page, blank specific sites, or inject junk. Incognito already hinted if they are guilty; disabling them and re-enabling one at a time finds the culprit. An extension nobody remembers installing, meanwhile, changes the ticket’s species entirely: that is the malware conversation, not the cleanup conversation.
Certificate warnings, the one place to slow down
Most browser tickets are safe to speed through. The full-page “your connection is not private” warning is the exception, and it deserves a slower hand.
The warning means the browser could not verify it is really talking to the site it dialed. The benign causes are common and worth knowing: a machine whose clock has drifted badly breaks certificate math everywhere at once, so every-site-warns plus wrong-taskbar-time is a two-minute fix. Corporate networks that inspect traffic trigger warnings on machines missing the company’s own certificate, a known quirk IT recognizes on sight. But the sinister cause, something genuinely intercepting the connection, produces the identical screen, and users cannot tell the difference. So the rule they should carry is absolute: never click past it, ask IT. A tech can look at which sites, which machines, and what changed and place the cause quickly. A user clicking “proceed anyway” on a real interception has just handed over whatever they type next.
The pattern under the toolkit
Look at the shape of all of this: split the state (incognito), refresh the state (cache and cookies), isolate the variable (extensions, second browser), and know the one warning that outranks speed. It is the six-step method wearing browser clothes, and it turns a vague “the portal is broken again” into a five-minute close instead of a shrug and a reboot.
Vague is exactly how these arrive, and the translation skill, from “it’s broken” to “which layer” while someone impatient waits, is trainable. The ServiceDesk Simulator keeps a queue of exactly such tickets, broken-for-one-user sites and half-loaded pages included, so the splitting habit becomes reflex before the first real Monday needs it.