Every website has flaws, but only a handful of website issues make a stranger reply to a cold email. The difference is not how serious the problem is to a designer. It is whether the owner can see it on their own phone in ten seconds, connect it to lost enquiries or lost trust, and believe the sender could fix it. Pick issues by that standard and outreach turns from opinion into observation; pick them by craft instinct and even accurate findings get archived.
That is why the choice of issue matters more than copywriting flair. Prospects rarely reply because an opener was clever. They reply because someone noticed a concrete problem on their site that feels costly, visible or overdue. What follows ranks the categories that keep earning replies across agency outreach, the ones that sound smart but stay unanswered, and how to phrase a finding so it lands as help rather than criticism.
Which website issues drive replies, and why those ones
The strongest outreach issues sit where obviousness meets consequence. If a problem is too technical, the prospect will not understand it. If it is too minor, they will not care. If it is too broad, it reads like a template that went to five hundred other companies that morning.
The three traits of a reply-worthy issue
A finding that earns a reply is easy to verify, easy to explain in one or two lines, and tied to an outcome the owner already cares about, such as enquiries, bookings, ad spend or credibility. Mobile rendering problems, slow key pages, weak or missing calls to action, confusing page hierarchy and trust gaps on decision pages pass all three tests again and again. A useful shortcut is to ask whether a non-designer would care within five seconds of seeing it. If the explanation needs UX theory, it belongs in the sales call, not the first email.
Relevance is also a trust transfer. When a prospect checks a finding and sees it is true, they start to believe the sender can solve larger problems they have not mentioned yet. When a finding is vague or wrong, the reverse happens, and every later claim is discounted. That is why accuracy outranks cleverness: a plain sentence about a real problem beats a polished paragraph about a guessed one.
See what's wrong with any website in seconds
The free analysis checks speed, mobile and SEO, then shows what to say to the owner. No signup, no card.
Mobile UX problems the owner can see on their own phone
Mobile issues are the most reliable opener because they are visible without debate. A desktop homepage can look polished and fall apart the moment it opens on an iPhone, with the hero text cut off, the menu icon sitting on top of the logo and the call to action lost below a wall of padding. When most traffic arrives on phones, that is not a design preference but a conversion problem. It also gives the prospect a small moment of proof, because they can check it immediately and see the sender was right.
Layout breaks, menus and tap targets
The strongest mobile findings are the ones a normal visitor would trip over. Headlines that wrap into five lines, cards that overflow the screen, image crops that hide the product, hamburger menus that will not open or will not close, and sticky headers that swallow a third of the viewport are all easy to describe in a sentence. Tap targets are a frequent failure too, with buttons smaller than the 48 pixel minimum Google recommends or packed so tightly that thumbs hit the wrong link. A spacing inconsistency in a footer is real but commercially weak, and it should never lead an email.
Forms that fight the thumb
If the contact form is hard to complete on a phone, the cost is direct and the owner understands it instantly. Cramped fields, a keyboard that covers the submit button, the wrong keyboard type for a phone number, dropdowns that need zooming and a submit state that never confirms anything all create friction exactly where leads are meant to convert. A form that asks for budget, timeline and company size before any trust is earned does the same damage more quietly. Test the full submission before mentioning it, because a broken form claim that turns out to be wrong ends the conversation.
A two-minute mobile review that finds the strongest angle
Load the homepage on a real phone and spend ten seconds without scrolling, asking whether it is clear what the business does and what to do next. Scroll at normal speed and watch for jumping layouts, sticky elements covering content and dense text blocks. Tap the main call to action and go through the next step, then check readability, then open one funnel page such as services, pricing or contact, because many sites keep the homepage tidy and break down deeper in. Those five checks, done in the same order on every site, surface the best angle without turning each prospect into an unpaid audit.
Speed findings that read as business problems
Speed is the most measurable issue and the easiest to get wrong in an email. A line saying a performance score is weak rarely gets traction, because prospects do not reply to numbers in isolation. A line saying the mobile service page takes 5.8 seconds before anything can be tapped, while paid traffic lands on it, gets read. The finding needs a page, a device context and a consequence, or it is filler.
Translate the metric into what visitors feel
Most owners have never heard of cumulative layout shift, but they recognise a page that jumps under the thumb and looks unstable while it loads. They will not care about render-blocking scripts, but they understand that visitors wait several seconds staring at a blank hero. Name the visible cause where possible, such as a 3,400px hero image, an autoplay video, a slider library or a stack of chat and tracking widgets. To get those findings for a specific prospect before writing, run the URL through the free website analysis, which returns the speed and mobile numbers without a signup, then describe what the numbers mean for a visitor rather than quoting them raw.
Speed is often the symptom of a bigger rebuild
A slow site rarely fails on speed alone. It usually comes with template bloat, a heavy page builder, third-party script creep and weak mobile structure, which is why a speed finding opens doors to redesign, migration and conversion work rather than just a tuning job. Be honest when it is tactical, though, because pitching a full rebuild to a strong site with one oversized image feels forced. Some slow sites also matter little commercially, so a speed issue only earns its place when the page carries demand.
Data quality matters more here than anywhere else. A prospect who opens the page, finds it loads in two seconds on office wifi and decides the claim was exaggerated will not book a call, so test on a throttled mobile connection and quote only figures that can be reproduced. Avoid treating every red score as a crisis, too, because a site can score poorly and still convert well, and a site can score decently and still feel heavy in the hand. Use the numbers to support a judgement about what a visitor experiences, never as the whole message.
Weighing up tools?
Honest comparisons with the tools agencies already use, including where they beat Swokei.
Conversion and trust flaws that cost enquiries
Plenty of sites look decent and still underperform because the path to action is muddy or the reassurance is missing at the moment of decision. These issues speak directly to commercial intent, which is why they draw replies from owners who have tolerated dated visuals for years. They work best when tied to a single page and a single moment in the visitor's journey.
Buried, crowded or vague calls to action
A call to action fails in two opposite ways. Sometimes it is hidden below the fold or labelled with soft language like "Learn more" on a page where the visitor is ready to book. Sometimes it competes with five other actions, from newsletter sign-ups to social links to live chat, until the page feels indecisive. Either way, the email can point to the specific page where the next step is unclear and ask whether enquiries from that page match the traffic it gets.
Missing proof and mismatched landing pages
Trust gaps are overlooked in cold outreach, which is exactly why they work. A service firm that claims measurable results but shows no client names, reviews, case studies or certifications near its form asks visitors to take everything on faith, and most will not. A related issue sits outside the page: an ad promising a free quote that lands on a generic homepage, or a pricing search that ends on a portfolio with no next step. Both are easy to show and easy for the owner to recognise as lost enquiries.
Neglect a visitor can see before reading a word
Some of the strongest openers are not design findings at all. An expired SSL certificate that throws a browser warning, mixed content that puts "Not Secure" in the address bar, a 404 linked from the main navigation and a copyright line five years out of date all tell visitors that nobody is minding the site. A single dead link is rarely worth an email on its own. Several visible signs of neglect across key pages, though, suggest a maintenance gap that the owner will want closed quickly, and a line pointing out the browser warning is about as easy to verify as outreach gets.
The website issues that sound smart but stay unanswered
Not every valid problem belongs in a first email, and this is where many campaigns go wrong. Accessibility detail, schema markup, code quality and advanced technical SEO can matter a great deal, but they need more context than a cold prospect will give. Broad labels like poor UX, outdated design or weak branding fail for the opposite reason, because they are subjective and every owner has heard them before. These issues usually work better once a conversation has started, not as the reason it starts.
The best issue to lead with also depends on the prospect. A law firm will shrug at a note about animation weight but respond to weak trust cues and a buried consultation path, while a software company cares more about signup friction and speed on product pages, and an online shop about mobile product discovery and checkout weight. For a broader look at spotting which websites need a redesign in the first place, segment first and pick the issue second. Relevance is not just being specific, it is being specific in the direction that buyer already worries about.
How to write the issue so the prospect replies
A reply-worthy message follows a simple order: the observation, the likely consequence and a small ask. Name the exact page and behaviour, connect it to something the owner already values, and offer to share what is causing it rather than pitching a project. Keep inferences hedged, saying a buried form may be creating drop-off rather than claiming to know their conversion rate from outside. The website critique email examples show that structure across different industries.
Restraint drives more replies than thoroughness. One strong issue is often enough, and two work only when they are tightly connected, such as a mobile layout break and a hidden call to action on the same page. Six findings and four screenshots read like a pitch deck disguised as outreach, and an accusatory tone produces silence even when every point is accurate. The difference between this and generic personalisation is covered in generic versus personalised outreach, and the wider levers sit in the guide to improving cold email reply rates.
Scale is where quality usually slips, because findings get generic and every site with a responsive bug receives the same line. Standardise which issues qualify and how each is described, then review before sending, so evidence is surfaced quickly but judgement still picks the angle. Sending tools built for volume rarely help with that part, which is why agencies comparing a lemlist alternative often weigh site analysis as heavily as deliverability. The next step is concrete: take one prospect, run it through the website analysis, choose the single issue the owner could confirm on their phone in ten seconds, and build the first email around that alone.
Run it on a real site before your next pitch
Analyse a prospect's site for free, or start free and let Swokei write the email from what it finds.



