The architecture, and why
The obvious way to build a hardware-test site is with a backend that stores results and accounts that keep a history. That would also destroy the only genuine differentiator this site has, which is that nothing you type, say or show on camera ever leaves the tab. So there is no backend at all. Every page is prerendered at build time, the tools are client-side components that read a browser API directly, and the only state anywhere is the full-check progress list, which lives in your own browser's localStorage.
That decision has downstream consequences and they are all good. Nothing to breach, because there is nothing stored. Nothing to keep patched in the request path. No cookie banner, because there are no cookies to consent to. And a page that loads from a CDN edge instead of waiting on a server.
How the content is kept honest
The eleven tests, four categories, twelve guides, two datasets, the sitemap, the llms.txt and the API index are all generated from the same registry. That is not tidiness for its own sake: the previous llms.txt was hand-written and had drifted to listing nine tools while the site had eleven, which made two of them invisible to any AI crawler using it as an index. Anything derived from one source cannot drift.
The last-updated date on every page comes from the git history of the files that produce that page, generated into a lookup at build time. It feeds the visible date, the sitemap and the structured data at once, so those three cannot disagree and none of them is a build timestamp masquerading as freshness.
What is deliberately absent
- No analytics, of any kind. Not even a privacy-friendly one.
- No cookies, no local storage except the full-check list you control.
- No third-party scripts, no chat widget, no heatmap, no session recording.
- No advertising. The ad slots in the codebase render nothing and are switched off.
- No affiliate links, anywhere on the site, at time of writing.
- No newsletter popup, no exit intent, no interstitial.
Open by default
The reference data compiled for these tools is published under CC BY 4.0, as human pages, as JSON endpoints and as CSV. Every test is available as a free embeddable frame for any other site, on the single condition that the credit link stays visible. Every AI crawler is explicitly allowed in robots.txt, because being quoted is the point.
Who built it
MyGearCheck is built and maintained by Jamey Weber, Front-end developer and founder of FusionStudios. It is a project of FusionStudios, a web design studio in the Netherlands.
If you want something built along these lines, fast, static, privacy-first and honest about what it does and does not do, that is the kind of work FusionStudios does. The studio site is the place to start a conversation. Everything else on MyGearCheck stays free and stays out of the way of the tools.