I kept seeing AI text detectors.
But I couldn't find a tool that analyzes an entire website.
So I built Slopdar.
Paste any URL and it:
π― Gives a Slop Score (0-100)
π§Ύ Shows the receipts behind the score
π Roasts the website for fun
It's completely free and doesn't require signup.
It started as a weekend experiment.
A few days later:
π Launched on Product Hunt
π Hundreds of websites scanned
π¬ Lots of feedback (and bug reports π )
One of my favorite moments was when someone pointed out a false positive.
I fixed it the same day, and they came back offering to help improve the heuristics.
That's exactly why I love building in public.
If you want to roast your own website (or your friend's π), I'd love your feedback.
π https://slopdar.com
This is fun and interesting, the reasoning is cool and genuinely useful. I'm not sure about the scoring though - is it just for fun or do you want it to be good?
Thanks! I definitely want the score to be useful, not just a fun number. It's still early, so I'm tweaking it as more people try it and share feedback. That's also why I show the reasoning. I'd rather people understand why a site got a score than blindly trust the number.
So I tried my two sites and the I got a lower score on the vibe coded one than on my old webflow one. Anyone once again cool work!
Pretty cool work! Think this can be very useful for basic fraud detection. Like - let's see who's not professional... Just one thing to note. I slapped in my fully lovable made prototype (check my profile, for Rogue Headlines, you'll see it immediately). It gave it a 56 score even though I'd have expected it to be considered maximum sloppiness (I don't know how to code and didn't code anything...) haha. Other than that, think this thing could become quite useful
That's actually by design. Slopdar isn't checking whether AI was used to build a site. It's looking for AI fingerprints. A site can be built entirely with Lovable and still score low if those fingerprints have been removed. I'd love to see your prototype if you're happy to share it. It would make a great test case.
I like that you're showing the reasoning behind the score instead of just assigning one.
The interesting challenge is making sure people use the score as a starting point for investigation rather than treating it as an objective measure of quality. That distinction will probably matter more as the product grows.
I completely agree. The score is just a summary. The reasoning is what I want people to focus on. That's why every scan includes the receipts instead of asking people to trust a black box.
Interesting.
Your reply made me think less about the score itself and more about what the product quietly commits itself to once the reasoning becomes the thing users are really expected to trust.
I don't think I can explain that line of reasoning properly in a thread without oversimplifying it.
If you're interested, what's the best email to reach you on?