Test Your Product on a Crappy Laptop

The Case for Testing on Hardware That Hurts

The devices we build websites on and the devices real people use to browse them have drifted so far apart that the gap is now a chasm. Meanwhile, the average page weight keeps climbing. The most direct corrective measure available to any team? Buy a craptop and use your own product on it.

These low-end machines are cheap because they ship with weak internals and, more often than not, a pile of resource-hungry third-party software that vendors preinstall to offset the price. Virus scanners alone can eat a surprising share of a weak CPU's cycles, and they're notoriously difficult to fully remove. These machines are everywhere and they aren't disappearing.

Work through your site on one of these machines and note three things: what loads slowly, what loads so slowly it becomes unusable, and what doesn't load at all. Then make a plan to address those pain points.

Your Analytics Are Lying to You

If your analytics are representative, most of your visitors arrive on modern, powerful hardware with up-to-date operating systems, generous RAM, and fast connections. That's great for your vanity metrics, but it introduces a serious blind spot when it comes to performance decisions.

Consider the survivor bias problem, famously illustrated by WWI's Brodie helmet. When British field hospitals saw a spike in soldiers with severe head injuries after the steel helmet's deployment, command nearly scrapped the design. A statistician had to point out the obvious: soldiers were surviving injuries that had previously been fatal. The data looked like a problem when it was actually evidence of progress.

The same logic applies to web performance. People who can't load your site never appear in your analytics at all. But there's a second, sneakier group: users whose devices load just enough of your page to register a hit before they give up and bounce because the experience is fundamentally broken. Does your reporting account for those people? Standard analytics almost certainly does not.

Who to Blame (and What to Do About It)

It's easy to buy a cheap laptop, load your site, and feel helpless as the page crawls. The problems typically trace back to two forces:

1. Third-party scripts. The very analytics, CRM, and marketing tags you use to understand your audience are often the heaviest things on your page. You have little control over the code they inject, and properly blocking their own resource loading is technically difficult.
2. The people requesting them. Business stakeholders who ask for these tags usually don't know the performance cost—or don't care, because their performance metrics don't include page speed.

The fix is to connect those abstract business requests to concrete, human consequences. One approach: establish a regular cadence of moderated usability testing on low-power hardware. Some teams institutionalize this as "Testing Tuesdays," but any recurring slot works—slow sites aren't usable, so performance testing belongs in your usability program. Make sure the sessions use real-world devices, not just whatever the average device in your analytics suggests. And be sure the sessions are visible. Showing a manager a real person failing to complete a task because of choices the organization made is a far more effective persuader than a performance report.

You can also institute craptop duty. Take roughly 260 working days in a year and give someone from development, design, marketing, or leadership a rotation on the slow machine. Most dev tooling can run through a Windows subsystem for Linux; nearly everything else has either a Windows installer or runs fine in a browser. If that's not true for your stack, or the pace is intolerably slow, well—that's the point you need to feel.

Hardware Isn't a Proxy for Income

One final thing worth stating plainly: a low-power machine does not indicate an economically disadvantaged user. Powerful devices slow down for all kinds of reasons—age, malware, network conditions, software bloat—and wealthy people absolutely use low-end technology. The deeper principle is that nobody deserves a degraded experience regardless of their circumstances. A performant, intuitive, accessible web should serve everyone, no matter what device they happen to be on.