Free · instant · one homepage read
What is this website built on?
Enter any address and you get the platform it runs on, what its homepage ships, and an honest verdict: stay where you are, modernize what sits in front of the CMS, or move. Every reason on the card comes from that one read of your page.
How the check works.
You get a card, not a score. It names the platform, lists what the homepage shipped, and says which way the evidence points. When your platform is a fair fit for the page it serves, the card says stay; that answer is as useful as any other.
- 01
Enter the address
Any public homepage. No login, no code installed, no email.
- 02
One read
The homepage is fetched once and its markup and headers are inspected. Nothing is stored.
- 03
A reasoned card
The platform, the evidence, and a verdict: stay, modernize or move, with the paths that fit.
Then read the guide for your platform.
Each guide covers why teams leave, the support and export facts with their dates, every alternative in one list, and the case for staying.
- 01Sitecore alternativesSupport dates, licensing and the paths off XP.
- 02Drupal alternativesUpgrade, decouple or move, judged by your pages.
- 03AEM alternativesWhat to run when you use a fraction of the suite.
- 04WordPress alternativesStay, go headless or move: judged by your pages.
- 05Wix alternativesWhat exports, what does not, and where to go.
- 06Squarespace alternativesWhat exports, what you lose, where to go next.
- 07Webflow alternativesWhere the limits bite and what replaces it.
- 08Shopify alternativesBy store size, with the keep-the-checkout option.
- 09Joomla alternativesUpgrade, move to a builder, or a modern stack.
- 10TYPO3 alternativesEnterprise CMS or modern stack, without the agency tie.
Questions, answered.
01How does the check know what a site runs on?
It reads the generator tag when a CMS leaves one, then falls back to fingerprints in the markup and headers: asset paths, data attributes, media handlers and hosting signatures. A fingerprint is evidence of the platform, not proof of how every page is served, and the card says so.
02What else does it read?
The number of script tags on the homepage, the weight of the HTML, the time to first response from our scanner, five common security headers, and whether any JSON-LD structured data is present. Those signals drive the verdict and every reason on the card.
03Is this the same as the full assessment?
No. This is one page and no score. The full assessment reads your homepage and up to eight more pages, scores eight weighted pillars out of 100 with the evidence behind each, and sends the report link to a work email once.
04Does it store my site or my details?
No. Nothing about the site or the request is kept, and no email is asked for. Twenty checks an hour are available from one connection so a script cannot run it in a loop.
Talk it through