Slopdar Turns Website Suspicion Into a Score

A website can look finished while still feeling oddly interchangeable. The layout is familiar, the copy contains filler, and every component seems to come from the same small set of defaults. That leaves visitors with a suspicion but not much evidence: was the site carefully built, assembled from a template, or produced quickly with an AI tool?

Slopdar is a free web tool aimed at that uncertainty. Paste a website link into it, and the service scans the page for signs associated with AI tools, templates, or rushed builders. It returns a Slop Score from 0 to 100, along with the evidence behind the result and a roast that can be screenshotted.

The basic problem it addresses is not website building. It is judging the visible character of a finished site when you have no access to its source code, process, or developer.

It looks for patterns, not authorship

Slopdar says it checks a page for fingerprints such as default components, common stack choices, familiar layout tropes, and leftover filler text. These are clues in the page itself. They are not a record of who made it.

That distinction matters. A website assembled with an AI tool might not contain every pattern Slopdar expects. A human developer might use a common stack or a familiar component library for sensible reasons. A template can also be customised heavily, while a hand-coded site can still look generic. The score therefore works best as a prompt for inspection rather than a verdict on the developer.

The product's useful contribution is making those clues more explicit. Instead of saying that a site feels generic, a reader can see which kinds of signals the scan noticed. The receipts are intended to connect the score to visible or detectable details, even if the interpretation of those details remains open to debate.

The score gives the suspicion a shape

The 0 to 100 Slop Score is the tool's central output. Its purpose is to turn a loose judgement about a site's originality or care into something easy to communicate. That makes the tool suitable for a quick review, a discussion about a landing page, or a screenshot shared with the site's owner.

The accompanying roast is part of the same idea. It gives the result a more entertaining format than a plain diagnostic report. That tone may make the output easier to share, but it also means the roast should not be confused with a technical audit. The receipts are the more useful part for anyone trying to understand the result.

There is a practical limit here: a single score compresses several different questions into one number. A site may be visually repetitive but technically sound. Another may look distinctive while containing filler text or default elements. Slopdar can point out patterns, but it cannot establish whether the site's code is maintainable, secure, accessible, or fast. Those are outside the problem it describes.

Other ways to use the result

Slopdar also includes a live leaderboard, guide pages, and an embeddable badge. The leaderboard gives the scores a public, ongoing context. It turns individual scans into a collection of sites that can be viewed against one another, although the score still represents the signals Slopdar checks rather than a universal measure of quality.

The guide pages appear to support the explanatory side of the product. They are relevant for readers who want more context around the patterns being identified, rather than only a number. The badge works in the opposite direction. Sites that score well can display it, while sites that score poorly can choose to wear that result publicly.

That last option captures the product's character. Slopdar is not presented as a private compliance check. It is a public-facing way to make a judgement about web design more visible, with enough evidence to make the judgement discussable.

Who Slopdar is for

Slopdar is aimed at people who encounter websites and want a fast way to investigate the feeling that one was assembled from defaults or generated in a hurry. It may be useful to developers reviewing examples, designers discussing patterns, or curious visitors who want more than an instinctive reaction. It is also a fit for site owners who are comfortable displaying a score or using the result as a prompt to revisit their pages.

It is not a good fit for anyone looking for proof of authorship or a full technical review. The service runs on the web, so its input is a page link, and its output is based on page-level fingerprints and related signals. It cannot settle the question of whether a real developer worked on a site, nor can it replace an inspection of the underlying code and behaviour.

That is the honest boundary of the product. Slopdar turns a vague suspicion into a score with receipts, but the score is a starting point for judgement, not the judgement itself.