Slop*Detector
Verdict for ohavah.com
SUSPICIOUSLY VIBEY — slop score 69/100
Ohavah.com reads like a template that never got a second pass. The clearest tell is structural: hero, trust strip, feature carousel, video testimonials, another logo strip, pricing, FAQ, in the exact stock SaaS sequence, padded with redundant trust messaging that repeats the same claim three different ways. Layered on top are the visual defaults nobody bothered to override, gradient washes, default lucide icons, and testimonial cards with rainbow accent borders, plus a product screenshot with suspiciously round pricing ($89.00, $62.00) that looks fabricated rather than exported from a real store. The copy backs this up with em dashes used as separators in the mock invoice data and a stacked-question drumbeat about Lightspeed integration. None of this is catastrophic on its own, but the combination of template skeleton, unedited component defaults, and placeholder-grade demo data adds up to a site assembled by a model and shipped with minimal human review, which supports the 69/100 score.“
Findings
- Pill tags — Little fully-rounded pill badges sprinkled across the page ("New", "Beta", category chips) are a default garnish of vibe-coded UI.
- Gradient backgrounds / gradient text — Large gradient washes and gradient-clipped headline text (usually blue→purple) are the default decoration of generated UI.
- Untouched shadcn/Tailwind defaults — shadcn components, lucide icons, and Inter/Geist/Space-Grotesk font stacks left at their defaults mean the model picked the design, not a person. Instrument Serif as an accent font is a separate, independently corroborated tell.
- Template skeleton — The page follows the stock SaaS section sequence almost exactly: hero, logo/trust strip, feature carousel, video testimonial, logo strip again, CTA banner, testimonial wall, video testimonials, pricing tiers, FAQ accordion.
- Redundant sections — Multiple sections repeat the same trust/testimonial message in different formats, suggesting slots filled to satisfy a template rather than a deliberate content plan.
- Colored borders on cards — Testimonial cards each carry a distinct colored top/left accent border (pink, orange, blue, green), a stock decorative pattern flagged as one of the most recognizable AI-UI tells.
- Stock CTA phrasing repeated as filler — The same CTA text ('Save 20 hours per month') and secondary CTA ('See Demo' / 'Try the interactive demo') appear multiple times across different sections rather than being tailored per-section.
- Numbered/dot carousel filler — A generic dot-indicator carousel ('What if listing products took minutes, not hours?') with left/right arrow controls sits with mostly empty whitespace beneath it, feeling like a templated slot rather than considered content.
- Mocked-up product screenshot with placeholder-like data — The 'Shopify Products' panel shows suspiciously tidy, generic placeholder-style data (round pricing, uniform SKUs) typical of a fabricated demo screenshot rather than a real captured product export.
- Generic thumbnail/logo placeholders — Several video/testimonial thumbnails are rendered as flat solid-color circles or plain gray boxes instead of real content, consistent with unfinished or auto-generated placeholder assets left in the page.
- Em dashes — Em dashes are the single most reliable punctuation tell of LLM copy. Human marketing copy almost never uses them; models reach for them constantly.
- One/two-word punch sentences — Single dramatic words dropped as their own sentence ("Done." "Gone." "Period.") are an LLM emphasis habit, not a human one.
- Stacked short-sentence drumbeat — Three or more clipped sentences in a row ("Important emails buried. Drafts that sound wrong. Labels everywhere.") is the manufactured-rhythm tell.
- AI vocabulary — Words statistically overrepresented in generated text: "seamless", "leverage", "unlock", "empower", "elevate", "robust" and friends.
- Em dash usage — The style guide bans em dashes outright, and the product screenshot mockup uses them as separators, though this is UI content rather than narrative prose, which softens the severity.
- 'X, not Y' reframe — The headline question uses the appositive/reframe contrast pattern flagged as an LLM tell, though it's a single instance in an otherwise concrete section.