Other ways to check a site

Tells you how generic the finished page looks, across thirteen aspects, with a score and the places on the page it comes from.

Does not tell you whether the page is fast, accessible or well built underneath.

Use it before you share a link, and after every redesign.

Tells you which of 62 named patterns are in your code or on your page. It is open source, runs in your editor and in your pull requests, and suggests the fix.

Does not tell you how the whole page comes across. In its own words, a finding is a reason to look closer.

Use it while you build. slop.graphics runs its detector on every scan and shows what it finds as named tells.

Tell you how fast the page loads and whether it meets the basics of accessibility and search.

Do not tell you anything about taste. A page can score 100 and still be the template everyone else shipped.

Use them alongside. A clean page that takes eight seconds to load has a different problem.

Tells you something in seconds, about any screenshot.

Does not tell you the same thing twice, and it is polite. When one general model scored sites by itself, it gave the sites Rais rated 63 to 98% slop between 17 and 38%.

Use it for ideas, not for a verdict.

Tells you more than any tool: what is wrong, why, and what to do about it for your product and your users.

Costs a person's time.

Use slop.graphics as the quick check in between, so the review starts past the obvious.