<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dan Draguta</title>
    <description>The latest articles on DEV Community by Dan Draguta (@dan_draguta_d18e1735edb6c).</description>
    <link>https://dev.to/dan_draguta_d18e1735edb6c</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4160412%2Feff31f92-2158-4305-8d34-2924ea903428.jpeg</url>
      <title>DEV Community: Dan Draguta</title>
      <link>https://dev.to/dan_draguta_d18e1735edb6c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dan_draguta_d18e1735edb6c"/>
    <language>en</language>
    <item>
      <title>A landing page for startups: get the first screen right before launch</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Tue, 10 Nov 2026 23:49:44 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/a-landing-page-for-startups-get-the-first-screen-right-before-launch-2n4e</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/a-landing-page-for-startups-get-the-first-screen-right-before-launch-2n4e</guid>
      <description>&lt;p&gt;A big company's landing page can be vague, because people already know the name. A startup's can't. Nobody has heard of you, there are no reviews yet, and most visitors give you a few seconds before they close the tab.&lt;/p&gt;

&lt;p&gt;That makes the first screen, the part people see before they scroll, the most important thing you will build before launch. This guide is about that screen, and the few sections under it that matter.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Short answer: a good landing page for a startup says what the product does in one plain sentence, shows it working right away, asks for one action (sign up, download, join the waitlist), and is something the founder can edit without a developer.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why startup landing pages fail
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The headline describes the category ("AI-native platform for creators") instead of what happens when you use it.&lt;/li&gt;
&lt;li&gt;The product is hidden behind illustrations and stock photos, so visitors have to imagine it.&lt;/li&gt;
&lt;li&gt;There are three buttons: waitlist, demo, docs. Nobody knows which one is for them.&lt;/li&gt;
&lt;li&gt;It was built in a heavy page builder, so changing one line before launch needs a ticket and a day.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The first screen, part by part
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The headline: say what happens
&lt;/h3&gt;

&lt;p&gt;Write the product in one sentence a stranger could repeat. The best pattern for an early product is often "you do X, it does Y". Prosper, a self-hosted AI game builder, launched with exactly that: "Describe a game. Prosper builds it." Five words and you know what the product is.&lt;/p&gt;

&lt;h3&gt;
  
  
  The subheadline: who and how
&lt;/h3&gt;

&lt;p&gt;One or two lines that say who it is for and what is different about it. For Prosper that is "self-hosted": it tells the right visitor (people who want to run it themselves) that this one is for them.&lt;/p&gt;

&lt;h3&gt;
  
  
  One button
&lt;/h3&gt;

&lt;p&gt;Pick the one action that moves your launch forward. Before launch that is usually "Join the waitlist". After launch it is "Download", "Start free" or "Order". Put it in the first screen, and repeat the same action at the end of the page. A quieter "See how it works" link that scrolls down is fine.&lt;/p&gt;

&lt;h3&gt;
  
  
  Show the product, not a picture of an idea
&lt;/h3&gt;

&lt;p&gt;This is where startups have an edge over big brands: your product is new, so showing it is the pitch. A short screen recording, a looping clip of the real thing, or a live demo right under the headline beats any illustration. Prosper's page puts the download button next to a live demo of the game builder, then a launch film and looping clips of games it made. In the founder's words, the page "shows the product instead of just describing it".&lt;/p&gt;

&lt;h3&gt;
  
  
  Proof, even with zero customers
&lt;/h3&gt;

&lt;p&gt;No reviews yet is normal. Use what you do have: the product working on screen, real numbers from your beta (only if they are real), the founder's name and face, a public changelog or repo. Honest early proof beats fake logos every time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Under the fold: four sections, then stop
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;How it works: three steps, each with a screenshot or clip.&lt;/li&gt;
&lt;li&gt;What you get: the outcome per feature, in the buyer's words.&lt;/li&gt;
&lt;li&gt;Pricing or "free during beta", stated plainly. Hiding the price makes people assume it is high.&lt;/li&gt;
&lt;li&gt;A short FAQ that answers the doubts you hear in every demo call, then the same button again.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is enough for launch. Testimonials, comparison tables and case studies come later, when you have them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build it so the founder can change it
&lt;/h2&gt;

&lt;p&gt;Before launch your message changes every week. If editing a headline needs a developer, the page will always be one version behind your pitch. Prosper's page is plain HTML, CSS and JS with no build step, so the founder edits and deploys it himself. Whatever you build on, test this before launch: can you change the headline and publish in five minutes?&lt;/p&gt;

&lt;p&gt;And check it on a phone. Most first visits from X, LinkedIn, Product Hunt or Hacker News happen on a phone, and the clips and demo have to work there too. The Prosper founder called out that "the mobile layout holds up well".&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist before you launch
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Headline: what the product does, one sentence&lt;/li&gt;
&lt;li&gt;Subheadline: who it is for and what is different&lt;/li&gt;
&lt;li&gt;One main button, same action at the end of the page&lt;/li&gt;
&lt;li&gt;The real product visible in the first screen&lt;/li&gt;
&lt;li&gt;Honest proof: product on screen, founder, real numbers only&lt;/li&gt;
&lt;li&gt;How it works in three steps&lt;/li&gt;
&lt;li&gt;Price or "free during beta" stated&lt;/li&gt;
&lt;li&gt;FAQ with the doubts from your demo calls&lt;/li&gt;
&lt;li&gt;Works and loads fast on a phone&lt;/li&gt;
&lt;li&gt;You can edit and publish it yourself in minutes&lt;/li&gt;
&lt;li&gt;The main action is tracked&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Want to check your own first screen first? The free &lt;a href="https://wolfitway.com/hero" rel="noopener noreferrer"&gt;Hero Analyzer&lt;/a&gt; scores it in about a minute. For the full list of what makes a page convert, see the &lt;a href="https://wolfitway.com/blog/high-converting-landing-page" rel="noopener noreferrer"&gt;12-point high converting landing page checklist&lt;/a&gt;. For an AI product example, open the &lt;a href="https://wolfitway.com/showcase/ai-startup" rel="noopener noreferrer"&gt;AI startup showcase page&lt;/a&gt; on your phone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Want it built before your launch?
&lt;/h2&gt;

&lt;p&gt;That is what my &lt;a href="https://wolfitway.com/" rel="noopener noreferrer"&gt;landing page design service&lt;/a&gt; does: copy, design and build of one landing page, live in 3 days for a fixed €2,500 / $2,900, ordered online with no calls. You get the code and can edit it yourself, like Prosper does. Building software? See the &lt;a href="https://wolfitway.com/landing" rel="noopener noreferrer"&gt;SaaS landing page&lt;/a&gt; offer, or read &lt;a href="https://wolfitway.com/blog/how-much-does-a-landing-page-cost" rel="noopener noreferrer"&gt;how much a landing page costs&lt;/a&gt; if you are still comparing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/landing-page-for-startups" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>5 hero mistakes that waste your ad spend (and how to check yours in 60 seconds)</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Tue, 10 Nov 2026 23:49:30 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/5-hero-mistakes-that-waste-your-ad-spend-and-how-to-check-yours-in-60-seconds-3ljm</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/5-hero-mistakes-that-waste-your-ad-spend-and-how-to-check-yours-in-60-seconds-3ljm</guid>
      <description>&lt;p&gt;You set up a paid campaign on Meta, Google Search, or LinkedIn. You dial in your audience targeting, write crisp ad creative, configure conversion tracking, and allocate €2,000 to €10,000 for the month. Your cost per click settles somewhere between €3.50 and €11.00. The dashboard reports hundreds of clicks flooding into your site.&lt;/p&gt;

&lt;p&gt;Then you open your web analytics, and the reality hits like a brick wall: 68% to 84% of those paid visitors leave within five seconds. They do not scroll down. They do not read your feature grid. They do not click your pricing tab. They never see your customer testimonials or your carefully produced product demo video. They arrived, blinked, felt confused or uninspired, and tapped the back button.&lt;/p&gt;

&lt;p&gt;Where did your ad spend go? It did not get lost in the footer or diluted in the middle of your page. It evaporated in the top 700 pixels of the screen: the hero section. The hero is the single most expensive piece of digital real estate your company owns. Every single euro of ad spend lands above the fold first. If the first screen fails to grip the visitor immediately, the rest of your landing page might as well not exist.&lt;/p&gt;

&lt;p&gt;Consider the mathematics of bounce rate. If you spend €5,000 per month at €5.00 per click, you receive 1,000 visitors. If your hero has an 80% bounce rate, 800 people bounce immediately, leaving you with 200 engaged visitors. If your conversion rate on those engaged visitors is 5%, you get 10 customers at an acquisition cost of €500 each. Now reduce that bounce rate to 50% with an optimized, high-clarity hero section: suddenly 500 visitors engage, delivering 25 customers from the exact same ad spend, cutting your customer acquisition cost to €200. That is a 150% increase in revenue without spending a single extra euro on ads.&lt;/p&gt;

&lt;p&gt;In this breakdown, we examine exactly what happens above the fold on mobile and desktop, diagnose the five fatal hero section mistakes that silently drain marketing budgets, and walk through a 60-second diagnostic you can run on your site today.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a visitor need to see in the first 5 seconds?
&lt;/h2&gt;

&lt;p&gt;When a prospective customer clicks your ad, their brain does not read your landing page like a novel. Cognitive psychologists call this "System 1 processing"—an instinctive, energy-saving, split-second evaluation driven by pattern recognition and survival heuristics. The visitor is asking four subconscious questions simultaneously:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1. Who is this for?&lt;/strong&gt; Does this product or service solve problems for someone in my exact role, industry, or life situation? If the category is ambiguous or buried under poetic jargon, the visitor assumes they are in the wrong place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2. What concrete result will I get?&lt;/strong&gt; What tangible transformation or painful relief are you delivering? Not "what features do you have," but what quantifiable outcome will happen in my work or life after using this?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;3. Why should I believe you?&lt;/strong&gt; Anyone can make bold promises on the internet. Where is the immediate proof anchor—trusted customer logos, an unvarnished review rating, an industry certification, or hard volume numbers—that validates your claims before I invest my attention?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;4. What is the single next step?&lt;/strong&gt; Where do my eyes and fingers go right now? If the call to action is hidden, ambiguous, or requires a PhD in commitment, the path of least resistance is clicking back to social media or search results.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Eye-tracking research across tens of thousands of landing page sessions reveals that users scan screens in fast F-shaped and Z-shaped sweeps. On desktop screens, their eyes land on the top-left headline, dart across the subheadline, drop to the primary action button, and glance at nearby trust badges. On mobile devices, the scan is even narrower: a vertical flick down the center of the viewport that lasts less than 2.4 seconds.&lt;/p&gt;

&lt;p&gt;If any of these four anchors is missing or pushed outside that initial viewport, cognitive friction spikes. When friction spikes, visitors do not lean in to investigate—they bounce. Let us examine the five mistakes that cause this breakdown most frequently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 1: a headline about you, not their outcome
&lt;/h2&gt;

&lt;p&gt;The most widespread disease in modern web copy is the "ego headline." Founders and marketing committees write headlines that describe their company’s internal vision or technical architecture rather than the customer’s felt reality. They write copy that sounds impressive in board meetings but means absolutely nothing to a cold prospect clicking an ad during their morning commute.&lt;/p&gt;

&lt;p&gt;Visitors do not care about your mission statement, your patent-pending proprietary engine, or how innovative you consider your team. They care about their deadline, their shrinking budget, their messy inbox, or their missed revenue targets. When your headline leads with your identity rather than their outcome, you force the prospect to do mental translation work. Most will refuse.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;**The Golden Rule of Hero Copywriting: **Your visitor should never have to ask "So what does this actually do for me?" If your headline could be pasted onto five of your competitors’ homepages without anyone noticing, it is an ego headline.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Let us contrast real-world examples across different digital sectors to illustrate the difference between an ego headline and an outcome-driven headline:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;B2B SaaS / Workflow Automation:&lt;/strong&gt;
• Bad (Ego): "Revolutionizing enterprise operational workflows through AI-orchestrated intelligence and holistic synchronicity."
• Good (Outcome): "Turn messy client Slack threads into signed contracts in 10 minutes without touching a spreadsheet."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Digital Agency / Software Studio:&lt;/strong&gt;
• Bad (Ego): "We are a full-service multidisciplinary boutique design and digital transformation agency."
• Good (Outcome): "We build custom internal tools that save your operations team 15 hours every single week—fixed price, live in 14 days."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cybersecurity / Infrastructure:&lt;/strong&gt;
• Bad (Ego): "Next-generation endpoint zero-trust multi-cloud data sovereignty paradigm."
• Good (Outcome): "Stop customer data leaks before they trigger GDPR fines. One single script, zero cloud middleman fees."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Notice the pattern in every high-converting headline. It follows a battle-tested structure:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;[Specific Desired Outcome] + [Timeframe or Clear Mechanism] + [Without the Primary Objection or Pain]&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Your subheadline should then immediately follow as the anchor. If the headline is the hook, the subheadline is the concrete explanation: one to two sentences stating exactly who uses the product, how it integrates into their current setup, and what risk reduction exists. Keep the reading grade level between 6th and 8th grade. High conversion copy is never pretentious.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 2: the CTA is below the fold on phones
&lt;/h2&gt;

&lt;p&gt;Between 65% and 85% of traffic from Meta ads, TikTok, LinkedIn mobile, and Google Performance Max arrives on a mobile device. Yet the overwhelming majority of landing pages are still designed, reviewed, and signed off on 27-inch 4K desktop monitors or 16-inch MacBook Pros.&lt;/p&gt;

&lt;p&gt;On a large monitor, the layout looks spacious, breathable, and elegant. The designer adds 120px of top padding, a massive 64px display font, three lines of introductory body copy, and a large custom illustration. But when that identical layout renders on an iPhone 15 or Samsung Galaxy (with viewport heights restricted by browser address bars, bottom navigation tabs, and system notches), disaster strikes: the Call to Action button is pushed 250 pixels beneath the lower edge of the physical screen.&lt;/p&gt;

&lt;p&gt;User session replays reveal a brutal truth: over 35% of mobile ad visitors never perform a single swipe gesture. If the primary action button is not visible within the initial mobile viewport without scrolling, those visitors will never know it exists. They see a fragment of text, an image with no context, and they bounce.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa3fflkxs4ai5lty46i3f.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa3fflkxs4ai5lty46i3f.jpg" alt="Mobile UX Comparison: Above the Fold vs Below the Fold viewport analysis" width="800" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To ensure your mobile hero converts at peak efficiency, apply these engineering and design principles:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;**Use dynamic viewport units: **Never use standard CSS &lt;code&gt;100vh&lt;/code&gt; for full-height hero sections on mobile. On iOS Safari and Chrome Android, &lt;code&gt;100vh&lt;/code&gt; calculates height behind the browser toolbars, causing layout overflow. Use &lt;code&gt;100svh&lt;/code&gt; (small viewport height) or dynamic flex containers that respect system bars.&lt;/li&gt;
&lt;li&gt;**Enforce the 540px vertical ceiling: **On mobile screens, your eyebrow badge, primary headline, concise 2-line subheadline, and primary CTA button must all fit comfortably within the top 540 vertical pixels. Use fluid font sizing with CSS &lt;code&gt;clamp()&lt;/code&gt; (e.g., &lt;code&gt;font-size: clamp(2rem, 5vw, 3.5rem)&lt;/code&gt;) and clamp your padding.&lt;/li&gt;
&lt;li&gt;**Thumb-friendly touch targets: **Make the mobile CTA button span the full width of the container or a minimum of 48px in height with at least 16px font size to prevent iOS Safari auto-zoom bugs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Mistake 3: no proof near the button
&lt;/h2&gt;

&lt;p&gt;Clicking a button on an unfamiliar website is an act of trust. The exact moment a visitor’s cursor hovers over your CTA, or their thumb hovers over the mobile screen, their subconscious risk anxiety peaks. Their brain fires rapid objections: "Is this a scam? Will they bombard me with sales spam? Am I entering a forced 14-day recurring billing trap? Do I have to jump through 10 form fields?"&lt;/p&gt;

&lt;p&gt;Many landing pages make the mistake of isolating their social proof in a separate section 1,200 pixels down the page. They place logos under a "Trusted by" header halfway to the footer. But remember: if the visitor feels anxious at the top of the page, they never scroll down to see your testimonials in the first place.&lt;/p&gt;

&lt;p&gt;The solution is what conversion architects call the "Micro-Proof Cluster"—small, high-impact trust anchors placed immediately adjacent to, or directly beneath, the primary Call to Action button. In A/B testing across hundreds of landing pages, adding a micro-proof cluster to the hero lifts CTA click-through rates by 18% to 34%.&lt;/p&gt;

&lt;p&gt;A high-converting Micro-Proof Cluster should include at least two of the following three elements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;**1. Star Rating + Specific Volume: **Instead of a vague "loved by customers," display an exact metric: "★ 4.9/5 rating from 140+ verified founders on G2 / Trustpilot" with small customer avatar stacks.&lt;/li&gt;
&lt;li&gt;**2. Friction Eliminators: **Three concise bullet items with checkmarks addressing immediate fears: "✓ No credit card required  ✓ 60-second setup  ✓ Cancel anytime."&lt;/li&gt;
&lt;li&gt;**3. Recognizable Client Logos: **A clean, monochrome strip of 4 to 5 recognized brand logos placed immediately below the button cluster with the label "Powering engineering and revenue teams at".&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Mistake 4: two or more competing CTAs
&lt;/h2&gt;

&lt;p&gt;Psychologist Barry Schwartz coined the term "The Paradox of Choice": when humans are presented with multiple competing options of similar visual weight, their decision-making slows down dramatically, and the likelihood of choosing nothing at all increases exponentially. On a landing page, this psychological phenomenon is fatal.&lt;/p&gt;

&lt;p&gt;We routinely audit landing pages where the hero section presents a visual circus of calls to action: a bold green button saying "Book an Enterprise Demo," sitting right next to an equally saturated blue button saying "Start 14-Day Free Trial," flanked by a link saying "Watch Product Video," topped by a navigation header featuring "Sign In," "Contact Sales," and "Read Case Studies." Which one is the visitor supposed to click?&lt;/p&gt;

&lt;p&gt;When you ask a prospect to evaluate two divergent paths, you introduce cognitive friction. Should they book a demo? What if they are not ready to talk to a salesperson? Should they start a trial? What if they don’t have time right now? While they debate these choices, a Slack notification dings or their train arrives, and they close your tab forever.&lt;/p&gt;

&lt;p&gt;Every high-converting landing page hero has exactly ONE primary call to action. If you have an alternate action (such as watching a 90-second product walkthrough or previewing sample reports), it must be designed with strict visual hierarchy:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;**The Primary CTA: **A high-contrast, magnetic solid button (e.g., deep amber or vibrant emerald) with clear outcome-driven verb phrasing ("Start My Audit →" or "Get Instant Access →").&lt;/li&gt;
&lt;li&gt;**The Secondary Option (if strictly necessary): **A quiet ghost button or an inline text link with an icon ("▷ Watch 60s demo"). It must never compete in visual dominance with your primary conversion trigger.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Mistake 5: a slow hero image or video on mobile
&lt;/h2&gt;

&lt;p&gt;You can have the most persuasive copywriting in the world and an irresistible offer, but if your hero takes four seconds to load over a mobile cellular connection, more than half your ad budget is completely wasted. Let us explain Largest Contentful Paint (LCP) in plain words without engineering jargon.&lt;/p&gt;

&lt;p&gt;LCP is Google’s metric that measures the stopwatch from the moment a user taps your ad link to the exact millisecond the largest visual element in their screen—almost always your hero image, headline block, or hero video—actually renders and becomes readable. Google’s performance threshold for a "Good" LCP is 2.5 seconds or less. On mobile paid traffic, every 100 milliseconds of delay beyond that threshold reduces conversion rates by approximately 1%.&lt;/p&gt;

&lt;p&gt;What causes catastrophic mobile hero slowdowns? The usual suspects:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;**4MB uncompressed PNG graphics: **Exporting raw product screenshots from Figma without compressing them or converting them to modern AVIF or WebP formats.&lt;/li&gt;
&lt;li&gt;**Autoplay background video on mobile: **Embedding a 15MB MP4 video loop that blocks the browser main thread and drains mobile battery, delaying first paint by 3 to 6 seconds on 4G networks.&lt;/li&gt;
&lt;li&gt;**Missing fetchpriority="high": **Failing to tell the browser that the hero image is critical, causing the browser to download tracking scripts and analytic pixels before fetching the image your visitor needs to see.&lt;/li&gt;
&lt;li&gt;**Third-party tag bloat: **Loading Google Tag Manager containers containing 14 un-cached marketing scripts, Hotjar session recorders, and customer chat widgets before your hero DOM is even constructed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A high-performance hero image should be served in modern AVIF or WebP format, responsive via &lt;code&gt;srcset&lt;/code&gt;, weighed under 80 KB, and declared with &lt;code&gt;fetchpriority="high"&lt;/code&gt; and &lt;code&gt;loading="eager"&lt;/code&gt; in your HTML markup. On mobile viewports, consider replacing background video entirely with a crisp, optimized still frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I check my own hero?
&lt;/h2&gt;

&lt;p&gt;How do you know if your current hero section is leaking ad spend right now? You don’t need to hire an expensive conversion rate consultancy or spend three weeks running multivariate tests to get your first diagnostic. You can audit your first screen in 60 seconds using our free Hero Analyzer.&lt;/p&gt;

&lt;p&gt;Here is how the automated diagnostic works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;*&lt;em&gt;Step 1: Enter your URL at *&lt;/em&gt;&lt;a href="https://wolfitway.com/hero" rel="noopener noreferrer"&gt;wolfitway.com/hero&lt;/a&gt;. Paste the exact landing page or homepage URL currently receiving your paid ad traffic.&lt;/li&gt;
&lt;li&gt;**Step 2: Headless Viewport Capture: **Our headless Chromium engine loads your URL and captures exact pixel-accurate screenshots of both the desktop viewport (1440x900) and the mobile viewport (390x844 with standard browser chrome).&lt;/li&gt;
&lt;li&gt;**Step 3: 8-Point Conversion Scoring: **The diagnostic inspects your above-the-fold content against eight critical conversion criteria: headline clarity, outcome specificity, mobile CTA visibility, proof proximity, visual hierarchy, cognitive friction, load performance, and single-action focus.&lt;/li&gt;
&lt;li&gt;**Step 4: Instant Actionable Report: **In under 30 seconds, you receive a visual report showing your exact mobile fold line, highlighting whether your CTA is cut off, rating your copy clarity, and giving you specific rewrite recommendations.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5b3ix4a3ko0unnejmoan.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5b3ix4a3ko0unnejmoan.webp" alt="Sample 8-Point Hero Analyzer Diagnostic Report from wolfitway.com/hero" width="800" height="366"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Running this scan before spending another euro on ad platforms often saves founders thousands of euros in leaked traffic within their first week.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does fixing it cost?
&lt;/h2&gt;

&lt;p&gt;Once you discover that your hero section is leaking conversions, you have two choices. You can spend weeks tinkering with button colors, rewriting headlines with AI copy generators, and fighting with sluggish website builders like Webflow or WordPress—hoping that piecemeal edits will fix fundamental structural issues.&lt;/p&gt;

&lt;p&gt;Or you can have an expert conversion engineer build you a bespoke, high-converting landing page from the ground up.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;**The Wolfitway Landing Page Sprint: **Full landing page in 3 working days, €1,200 fixed investment.&lt;/p&gt;

&lt;p&gt;• Precision psychological copywriting engineered for your specific offer and ad audience.&lt;br&gt;
• Custom mobile-first responsive architecture designed to keep the CTA and proof permanently visible above the fold.&lt;br&gt;
• 100/100 Google Lighthouse performance score with sub-second LCP on cellular connections.&lt;br&gt;
• WCAG 2.2 AA accessibility compliance out of the box.&lt;br&gt;
• Zero recurring platform fees—you own 100% of the code, data, and deployment on your sovereign stack.&lt;/p&gt;

&lt;p&gt;*&lt;em&gt;Inspect the full offer and reserve your build window: *&lt;/em&gt;&lt;a href="https://wolfitway.com/landing" rel="noopener noreferrer"&gt;wolfitway.com/landing&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions about Hero Sections
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is a good conversion rate for a B2B SaaS or service landing page hero?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Across paid ad traffic (Meta, Google Search, LinkedIn), average landing page conversion rates typically range from 2.5% to 4.5% for free trials or lead magnets, and 1.0% to 2.5% for paid deposits or demo bookings. However, high-performing hero sections with clear outcome headlines, immediate proof anchors, and mobile-optimized CTAs frequently achieve conversion rates between 7.5% and 12.0%. A well-crafted hero often triples the net return on ad spend without touching ad creatives.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should I use an autoplay background video in my hero section?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In 90% of cases, no. While autoplay videos can look impressive to company founders on high-end desktop monitors, conversion audits consistently show that background video distracts from headline readability, increases cognitive friction, and wrecks mobile performance. On mobile devices, autoplay video triggers high battery consumption, stalls Largest Contentful Paint (LCP) by 2 to 4 seconds over cellular data, and is often paused automatically by low-power mode. If you have video, place an explicit play button on a lightweight thumbnail or link it as a secondary action.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How many words should my hero headline and subheadline be?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The optimal hero headline is between 6 and 11 words (under 70 characters). It must be readable in a single glance without wrapping into four lines on an iPhone screen. The subheadline should be between 18 and 32 words across no more than two sentences, explaining the exact mechanism, target audience, and primary outcome. Every extra word you add beyond this threshold reduces the percentage of visitors who complete the sentence.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/hero-section-mistakes-ad-spend" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What makes a high converting landing page? The 12-point checklist I build with</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Tue, 10 Nov 2026 23:49:08 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/what-makes-a-high-converting-landing-page-the-12-point-checklist-i-build-with-1gg</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/what-makes-a-high-converting-landing-page-the-12-point-checklist-i-build-with-1gg</guid>
      <description>&lt;p&gt;Most "high converting landing page" guides show you thirty screenshots of famous brands and leave you to guess why they work. Famous brands convert because people already know them. You don't have that, so your page has to do the work.&lt;/p&gt;

&lt;p&gt;Below is the checklist I go through on every page I build. Each point is one decision. Get all twelve right and the page does its job: a visitor understands what you sell, believes you, and knows what to do next.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Short answer: a high converting landing page says one clear outcome in the headline, proves it near the top, asks for one action, and loads fast on a phone. Everything else is detail.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The top of the page (where most visitors decide)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. A headline that names the outcome, not the product
&lt;/h3&gt;

&lt;p&gt;"AI-powered workflow platform" describes you. "Close the month in 2 days, not 10" describes what the buyer gets. Write the result your customer wants, in their words. If a stranger can't repeat what you do after five seconds, the headline is not done.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. A subheadline that says how and for whom
&lt;/h3&gt;

&lt;p&gt;One or two sentences: who it is for, how it works, and what makes it different. This is where you filter out the wrong visitors so the right ones feel at home.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. One main call to action
&lt;/h3&gt;

&lt;p&gt;One button, one verb, one next step: "Book a table", "Start free trial", "Order my page". A second, quieter link is fine ("See how it works"). Five equal buttons is a menu, not a landing page.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Proof above the fold
&lt;/h3&gt;

&lt;p&gt;A real number, a logo row, a short review with a name and photo, or a product shot that shows the thing working. Visitors decide whether to trust you before they scroll.&lt;/p&gt;

&lt;p&gt;Want to know how your own top section scores on these four? The free &lt;a href="https://wolfitway.com/hero" rel="noopener noreferrer"&gt;Hero Analyzer&lt;/a&gt; checks it in about a minute.&lt;/p&gt;

&lt;h2&gt;
  
  
  The middle (where visitors decide to believe you)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  5. Benefits before features
&lt;/h3&gt;

&lt;p&gt;Lead each section with what changes for the buyer, then show the feature that makes it happen. Features answer "how", benefits answer "why should I care".&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Show, don't describe
&lt;/h3&gt;

&lt;p&gt;Real photos, a short video, or the product itself beat stock images every time. The barbershop page in my showcase opens with a scroll-driven film walking you into the shop, because a haircut is something you want to see before you book: &lt;a href="https://wolfitway.com/showcase/barbershop" rel="noopener noreferrer"&gt;barbershop example&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Answer objections where they appear
&lt;/h3&gt;

&lt;p&gt;Price, time, risk, "will it work for me". Put the answer right next to the moment the doubt shows up, and collect the rest in a short FAQ near the end.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Make the next step specific
&lt;/h3&gt;

&lt;p&gt;Not "Contact us" but "Book your first class, Tuesday 18:00 is free". The gym and dojo pages in the showcase show the next free class right on the coach cards, so the visitor does not have to ask: &lt;a href="https://wolfitway.com/showcase/fitness" rel="noopener noreferrer"&gt;fitness example&lt;/a&gt;, &lt;a href="https://wolfitway.com/showcase/martial-arts" rel="noopener noreferrer"&gt;martial arts example&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts nobody sees (but everyone feels)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  9. Fast on a real phone
&lt;/h3&gt;

&lt;p&gt;Most visitors arrive on a phone, often on mobile data. Compress images, avoid heavy scripts, and test on a mid-range phone, not your laptop. A slow page loses people before they read the headline.&lt;/p&gt;

&lt;h3&gt;
  
  
  10. Readable and accessible
&lt;/h3&gt;

&lt;p&gt;Enough contrast, text that is at least 16 px, buttons big enough for a thumb, and a page that works with a keyboard and a screen reader. In the EU this is also the law for many consumer services since June 2025: &lt;a href="https://wolfitway.com/european-accessibility-act" rel="noopener noreferrer"&gt;what the European Accessibility Act means for your site&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  11. One page, one goal, no exits
&lt;/h3&gt;

&lt;p&gt;Remove the full site menu, footer link farms and anything that sends people away before they act. Every link that is not your call to action is a leak.&lt;/p&gt;

&lt;h3&gt;
  
  
  12. Measured, then improved
&lt;/h3&gt;

&lt;p&gt;Track the one action that matters (a booking, an order, a sign-up) and how far people scroll. Change one thing at a time. Without numbers, "improving the page" is guessing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist to copy
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Headline names the outcome&lt;/li&gt;
&lt;li&gt;Subheadline says who it is for and how&lt;/li&gt;
&lt;li&gt;One main button with a clear verb&lt;/li&gt;
&lt;li&gt;Proof visible without scrolling&lt;/li&gt;
&lt;li&gt;Benefits first, features second&lt;/li&gt;
&lt;li&gt;Real photos or the product in use&lt;/li&gt;
&lt;li&gt;Objections answered in place + short FAQ&lt;/li&gt;
&lt;li&gt;Next step is specific (time, slot, price)&lt;/li&gt;
&lt;li&gt;Loads fast on a mid-range phone&lt;/li&gt;
&lt;li&gt;Readable, keyboard and screen reader friendly&lt;/li&gt;
&lt;li&gt;No menu or links that lead away&lt;/li&gt;
&lt;li&gt;The main action is tracked&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  More examples you can open
&lt;/h2&gt;

&lt;p&gt;Every page in the &lt;a href="https://wolfitway.com/showcase" rel="noopener noreferrer"&gt;showcase&lt;/a&gt; is built on this checklist: a &lt;a href="https://wolfitway.com/showcase/alpine-lodge" rel="noopener noreferrer"&gt;mountain lodge&lt;/a&gt;, a &lt;a href="https://wolfitway.com/showcase/security-villa" rel="noopener noreferrer"&gt;home security company&lt;/a&gt;, and more. Open them on your phone; that is where your visitors will see yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  Want it built for you?
&lt;/h2&gt;

&lt;p&gt;If you would rather not go through the twelve points yourself, that is exactly what my &lt;a href="https://wolfitway.com/" rel="noopener noreferrer"&gt;landing page design service&lt;/a&gt; does: copy, design and build of one high converting landing page, live in 3 days for a fixed €2,500 / $2,900, ordered online with no calls. The code is yours. Building for software? See the &lt;a href="https://wolfitway.com/landing" rel="noopener noreferrer"&gt;SaaS landing page&lt;/a&gt; offer, and if you are still comparing budgets, read &lt;a href="https://wolfitway.com/blog/how-much-does-a-landing-page-cost" rel="noopener noreferrer"&gt;how much a landing page costs&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/high-converting-landing-page" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>We Tested 379 Company Homepages for Accessibility. 9 Passed.</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Tue, 10 Nov 2026 23:48:24 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/we-tested-379-company-homepages-for-accessibility-9-passed-3k7p</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/we-tested-379-company-homepages-for-accessibility-9-passed-3k7p</guid>
      <description>&lt;p&gt;The European Accessibility Act has applied since 28 June 2025. Online shops, banks, transport companies, e-book sellers and a few other sectors in the EU now have a legal duty to make their websites usable for people with disabilities. I wanted to know how far the average company actually is from that, so I tested homepages.&lt;/p&gt;

&lt;p&gt;Over three weeks I ran the same automated accessibility test on the homepages of 379 companies. 279 were small and mid-size companies and startups. 100 were the biggest listed companies in the world.&lt;/p&gt;

&lt;p&gt;The headline: of the 271 homepages I could actually test, &lt;strong&gt;9 passed&lt;/strong&gt;. Eight small companies and one giant (Shell).&lt;/p&gt;

&lt;p&gt;This article is mostly about how I got that number, because a number like that is only worth something if you can see how it was made. You will find who was in the sample, how many sites blocked me, what the test checks and what it can't check, how the score works, and the problems that showed up again and again. At the end there is a short list of fixes that would move most sites over the line.&lt;/p&gt;

&lt;p&gt;One disclosure first. I build websites and landing pages for a living, and the 279 smaller companies came from my own list of possible clients. That's why I had their addresses. It's also why I've kept the method strict and published every rule below: you shouldn't have to trust me, you should be able to check me.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;379 homepages tried. 271 tested. 108 couldn't be tested&lt;/strong&gt; (mostly security walls that block automated visitors). Blocked sites are left out. They don't count as fails.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smaller companies: 8 of 209 passed (3.8%).&lt;/strong&gt; Average score 61 out of 100, median 67.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The world's 100 biggest listed companies: 1 of 62 passed (1.6%).&lt;/strong&gt; Average score 53, median 56.5.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low-contrast text was the most common problem by far:&lt;/strong&gt; 86% of the smaller companies' homepages and 56 of 62 of the big ones (90%).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;45 of the smaller companies were one failing rule away from passing.&lt;/strong&gt; Most of these rules are a few lines of CSS or one missing label.&lt;/li&gt;
&lt;li&gt;This is an &lt;strong&gt;automated test of one page per company&lt;/strong&gt;. A pass is a good sign. It is not a certificate, and it doesn't make a site "compliant".&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why test homepages at all
&lt;/h2&gt;

&lt;p&gt;A homepage is the one page every company has, and the one every visitor sees first. If someone using a screen reader can't tell what a button does on the homepage, or someone with low vision can't read the main headline, they often never get to the product page.&lt;/p&gt;

&lt;p&gt;It's also the fairest thing to compare. Checkout flows, account areas and support pages differ a lot between a bank and a SaaS startup. A homepage is a homepage.&lt;/p&gt;

&lt;p&gt;The downside is obvious: one page says little about a whole website. I'll come back to that in the limits section. Keep it in mind for every number here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who was in the sample
&lt;/h2&gt;

&lt;p&gt;I kept two groups, and I report them apart. They are very different companies, and mixing them would hide that. (I made that mistake once in my own working notes, and the totals came out wrong. Since then the two groups never share a table.)&lt;/p&gt;

&lt;h3&gt;
  
  
  Group 1: 279 smaller companies and startups
&lt;/h3&gt;

&lt;p&gt;These came from public listings I use to find clients:&lt;/p&gt;

&lt;p&gt;Source&lt;/p&gt;

&lt;p&gt;Companies&lt;/p&gt;

&lt;p&gt;Wikidata (companies registered in Germany, the UK, the Netherlands and Romania)&lt;/p&gt;

&lt;p&gt;159&lt;/p&gt;

&lt;p&gt;BetaList (new startups)&lt;/p&gt;

&lt;p&gt;35&lt;/p&gt;

&lt;p&gt;Y Combinator company directory&lt;/p&gt;

&lt;p&gt;26&lt;/p&gt;

&lt;p&gt;Show HN on Hacker News&lt;/p&gt;

&lt;p&gt;22&lt;/p&gt;

&lt;p&gt;Hacker News "Who is hiring?"&lt;/p&gt;

&lt;p&gt;20&lt;/p&gt;

&lt;p&gt;Remote OK job listings&lt;/p&gt;

&lt;p&gt;12&lt;/p&gt;

&lt;p&gt;Added by hand&lt;/p&gt;

&lt;p&gt;5&lt;/p&gt;

&lt;p&gt;My full list had 498 companies. 98 of them were also in Group 2, so I took them out here. Another 121 I had already ruled out as clients for sales reasons, before any scan was run, and I never scanned them. That leaves 279, and every one of them was tried. I didn't pick which ones to report after seeing results.&lt;/p&gt;

&lt;p&gt;Of the 209 I could test, the countries I could identify were Romania (44), the UK (26), Germany (24), the US (21), the Netherlands (17), Japan (1) and Canada (1). For 75 I don't have a country on record.&lt;/p&gt;

&lt;p&gt;Group 1 is not a random sample of all businesses. It leans towards tech companies and startups, and towards the four European countries I pulled from Wikidata. Treat it as "a few hundred real small and mid-size company websites", not as "the average European business".&lt;/p&gt;

&lt;h3&gt;
  
  
  Group 2: the 100 biggest listed companies in the world
&lt;/h3&gt;

&lt;p&gt;I took the top 100 companies by market value from CompaniesMarketCap and saved the ranking on 2 November 2026, before scanning anything. Market value changes every day, so the saved copy (with a hash of the source pages) is what the study uses.&lt;/p&gt;

&lt;p&gt;The rule was simple: the list was fixed in advance. No swapping a company for an easier one, no second tries to get a nicer result, no replacing a blocked company with the next one down. When a company has several websites, I used the main corporate or main consumer homepage and wrote down which one (for example abc.xyz for Alphabet and about.meta.com for Meta).&lt;/p&gt;

&lt;h2&gt;
  
  
  Not every site let me in
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7020zmquj9xvvgdv85gx.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7020zmquj9xvvgdv85gx.jpg" alt="379 tried, 271 tested, 9 passed. Smaller companies: 279 tried, 209 tested (75%), 8 passed (3.8% of tested); not tested: 36 security wall or rate limit, 23 unreachable, 11 errors and timeouts. World's 100 biggest companies: 100 tried, 62 tested (62%), 1 passed (1.6% of tested, Shell); not tested: 14 security wall or gate page, 10 over 20 seconds to load, 9 unreachable, 5 other." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This part gets left out of most studies, so here it is in full.&lt;/p&gt;

&lt;p&gt;An automated test runs from a server, not from someone's laptop. A lot of websites block that on purpose. Bot protection services (Cloudflare and similar) show a challenge page instead of the real site. Others limit how often a server can visit, or just never answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Group 1: I could test 209 of 279 (75%).&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Why I couldn't test it&lt;/p&gt;

&lt;p&gt;Sites&lt;/p&gt;

&lt;p&gt;Security challenge or firewall&lt;/p&gt;

&lt;p&gt;32&lt;/p&gt;

&lt;p&gt;Rate limited (too many requests, HTTP 429)&lt;/p&gt;

&lt;p&gt;4&lt;/p&gt;

&lt;p&gt;Unreachable (no answer, DNS failure, site down)&lt;/p&gt;

&lt;p&gt;23&lt;/p&gt;

&lt;p&gt;Scan error, timeout, interrupted, HTTP 400/401&lt;/p&gt;

&lt;p&gt;11&lt;/p&gt;

&lt;p&gt;Total&lt;/p&gt;

&lt;p&gt;70&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Group 2: I could test 62 of 100.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Why I couldn't test it&lt;/p&gt;

&lt;p&gt;Sites&lt;/p&gt;

&lt;p&gt;Security challenge, firewall or gate page&lt;/p&gt;

&lt;p&gt;14&lt;/p&gt;

&lt;p&gt;Page took more than 20 seconds to load&lt;/p&gt;

&lt;p&gt;10&lt;/p&gt;

&lt;p&gt;Unreachable&lt;/p&gt;

&lt;p&gt;9&lt;/p&gt;

&lt;p&gt;Other (scan failed, HTTP 400, interrupted, only a regional shell page loaded)&lt;/p&gt;

&lt;p&gt;5&lt;/p&gt;

&lt;p&gt;Total&lt;/p&gt;

&lt;p&gt;38&lt;/p&gt;

&lt;p&gt;Big companies were harder to get into (38% couldn't be tested, against 25% of the smaller group). NVIDIA, Microsoft, Alphabet, Amazon, Tesla, Meta and Walmart are among the 38. For the record: when the page I got back was a challenge or a "click to continue" screen rather than the real homepage, I threw the result out, even if the score looked fine. Amazon is one of those. I checked the captured titles, headings and screenshots of the big companies by hand to catch this.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A blocked site is never counted as a fail.&lt;/strong&gt; It's simply not in the results. So all the pass rates below are out of the sites I could test (209 and 62), not out of everyone I tried (279 and 100). If you quote this study, please quote both.&lt;/p&gt;

&lt;p&gt;There is a real question hiding in here too. If a server can't get past the front door, some assistive tools and some privacy browsers may have trouble too. I didn't test that, so I won't claim it. But it's worth a look if you run one of those walls.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the test works
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1fvvu2oiazw9r7z5175.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1fvvu2oiazw9r7z5175.jpg" alt="How the test works, in five steps. 1: open the homepage in a fresh Chromium browser, close the cookie banner if possible; 20 seconds to load, 4 minutes per site at most. 2: test at two screen sizes, 1440 by 900 and 390 by 844, and merge the problems. 3: run axe-core 4.14 with every WCAG 2.0, 2.1 and 2.2 A and AA rule, plus a pixel check for text on photos and gradients. 4: only confirmed WCAG failures cost points: critical 15, serious 8, moderate 3, minor 1. 5: a pass needs a score of 90 or more, zero critical and zero serious problems. Blocked sites are left out, not counted as fails." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Every site got exactly the same test, run by the same scanner on the same server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One page, two screen sizes.&lt;/strong&gt; The scanner opens the homepage in a fresh Chromium browser twice: once at desktop size (1440 x 900) and once at phone size (390 x 844). The phone run uses Chrome's mobile mode, not a real iPhone with Safari. Problems found at either size are merged into one report.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cookie banners.&lt;/strong&gt; Most sites show a consent banner first. The scanner tries to close it the way a visitor would, then tests the page underneath. When it can't, the banner stays and gets tested as part of the page, which is fair, since a visitor sees it too.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The rules: axe-core plus a pixel check.&lt;/strong&gt; The main engine is axe-core 4.14, the open-source accessibility engine used inside many testing tools and browser extensions. I ran it with the rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA. WCAG (Web Content Accessibility Guidelines) is the standard that EU rules point to. The EU standard behind the Accessibility Act, EN 301 549, is built on WCAG level AA.&lt;/p&gt;

&lt;p&gt;axe-core has one known blind spot: text on top of a photo, a gradient or a video. It can't work out the background colour, so it marks those "needs review" and moves on. On modern homepages that's often the biggest headline on the page. So the scanner has a second check: it takes a screenshot of the element with the text hidden, reads the actual background pixels, and compares them with the text colour. It uses the 5th-worst percentile of the background, so a single dark pixel doesn't fail a light button, but white text running across a bright part of a photo does.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Three groups of findings, only one counts.&lt;/strong&gt; Every finding lands in one of three buckets:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;WCAG failures.&lt;/strong&gt; Confirmed breaks of a WCAG A or AA rule. Only these count toward the score and the pass/fail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Needs review.&lt;/strong&gt; Things a human should double-check, like contrast the scanner couldn't measure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Advice.&lt;/strong&gt; Best practices that aren't WCAG rules, like very small text or vague link text ("click here").&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Keeping review and advice out of the score means the score only goes down for problems the scanner is sure about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Time limits.&lt;/strong&gt; A page gets 20 seconds to load. The whole scan of one site (both screen sizes, all checks) gets four minutes. Two sites were scanned at a time.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the score works
&lt;/h2&gt;

&lt;p&gt;Each failing WCAG rule takes points off a starting score of 100. How many depends on how serious the problem is, as rated by axe-core:&lt;/p&gt;

&lt;p&gt;Impact&lt;/p&gt;

&lt;p&gt;Points off&lt;/p&gt;

&lt;p&gt;Critical&lt;/p&gt;

&lt;p&gt;15&lt;/p&gt;

&lt;p&gt;Serious&lt;/p&gt;

&lt;p&gt;8&lt;/p&gt;

&lt;p&gt;Moderate&lt;/p&gt;

&lt;p&gt;3&lt;/p&gt;

&lt;p&gt;Minor&lt;/p&gt;

&lt;p&gt;1&lt;/p&gt;

&lt;p&gt;The penalty grows a little with the number of elements affected, but slowly (it's scaled by the log of the count). One unlabelled button costs 15 points. Ten unlabelled buttons cost 30, not 150. This stops one sloppy menu from sending a page to zero, while still showing that ten problems are worse than one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;To pass, a page needs all three:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a score of 90 or more,&lt;/li&gt;
&lt;li&gt;zero critical problems,&lt;/li&gt;
&lt;li&gt;zero serious problems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last two rules matter. A page with one critical problem on one element scores 85 and fails. But a page could in theory reach 90 with one small serious issue, and I didn't want that to count. Critical and serious problems are the ones that can stop someone using the page, like a button a screen reader announces as just "button", or a headline someone can't read. So any one of those is a fail, whatever the score.&lt;/p&gt;

&lt;h2&gt;
  
  
  The results
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3f5doazaa45ol8h0ljte.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3f5doazaa45ol8h0ljte.jpg" alt="Results side by side. Smaller companies, 209 tested: 8 passed (3.8%), average score 61 (median 67), 45 one failing rule from a pass, 34% with at least one critical problem. Top 100 companies, 62 tested: 1 passed (1.6%, Shell), average score 53 (median 56.5), 8 one failing rule from a pass, 50% with at least one critical problem." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Group 1: smaller companies (209 tested)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;8 passed (3.8%).&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;45 (21.5%) were one failing rule away&lt;/strong&gt;: exactly one critical or serious rule stood between them and a pass.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;72 (34%) had at least one critical problem.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Average score 61, median 67.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Group 2: the 100 biggest companies (62 tested)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1 passed: Shell, with a score of 100.&lt;/strong&gt; For full transparency: Shell's cookie panel was still showing in the capture, and the score describes the page in that state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;8 were one failing rule away.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;31 (50%) had at least one critical problem.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Average score 53, median 56.5.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Split by rank, the top 50 went 1 pass out of 26 tested, and ranks 51 to 100 went 0 out of 36.&lt;/p&gt;

&lt;h3&gt;
  
  
  Big companies did no better
&lt;/h3&gt;

&lt;p&gt;I expected the big companies to win easily. They have accessibility teams, design systems and legal departments. They didn't. 1 in 62 passed, against 8 in 209 for the smaller group. Their average score was lower too (53 against 61).&lt;/p&gt;

&lt;p&gt;I want to be careful with this. The groups are different in size, in industry and in country, and the samples are small. I'm not claiming small companies are better at accessibility, or that money doesn't help. What the data does show is narrower and still interesting: &lt;strong&gt;a big budget didn't produce a passing homepage either.&lt;/strong&gt; Size isn't the thing that decides this.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problems that showed up most
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmvnmt37m60xelc8pufc6.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmvnmt37m60xelc8pufc6.jpg" alt="Most common WCAG failures, smaller companies (of 209) versus top 100 companies (of 62): text too faint 86% (180) vs 90% (56); links with no name 34% (71) vs 32% (20); label does not match name 24% (50) vs 52% (32); tap targets too small 21% (44) vs 21% (13); images with no description 18% (38) vs 16% (10); buttons with no name 13% (28) vs 19% (12)." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is what failed most often in Group 1. These are WCAG failures only, counted once per site.&lt;/p&gt;

&lt;p&gt;Problem&lt;/p&gt;

&lt;p&gt;Sites (of 209)&lt;/p&gt;

&lt;p&gt;Text too faint against its background&lt;/p&gt;

&lt;p&gt;180 (86%)&lt;/p&gt;

&lt;p&gt;Links with no readable name&lt;/p&gt;

&lt;p&gt;71 (34%)&lt;/p&gt;

&lt;p&gt;Visible label doesn't match the hidden name&lt;/p&gt;

&lt;p&gt;50 (24%)&lt;/p&gt;

&lt;p&gt;Tap targets too small on phones&lt;/p&gt;

&lt;p&gt;44 (21%)&lt;/p&gt;

&lt;p&gt;Images with no text description&lt;/p&gt;

&lt;p&gt;38 (18%)&lt;/p&gt;

&lt;p&gt;Buttons with no readable name&lt;/p&gt;

&lt;p&gt;28 (13%)&lt;/p&gt;

&lt;p&gt;Zooming blocked on phones&lt;/p&gt;

&lt;p&gt;26 (12%)&lt;/p&gt;

&lt;p&gt;Scroll areas you can't reach with a keyboard&lt;/p&gt;

&lt;p&gt;22 (11%)&lt;/p&gt;

&lt;p&gt;Group 2 had nearly the same top five: contrast on 56 of 62, label mismatch on 32, unnamed links on 20, small tap targets on 13, unnamed buttons on 12.&lt;/p&gt;

&lt;p&gt;Here is what each one means, and why it matters to a real person.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Text too faint against its background (86%)
&lt;/h3&gt;

&lt;p&gt;WCAG asks for a contrast ratio of at least 4.5 to 1 between normal text and its background, and 3 to 1 for large text (24 px, or about 19 px bold). Light grey text on white usually misses. So does white text on a busy photo.&lt;/p&gt;

&lt;p&gt;This one is everywhere because it looks good in a design file. Soft grey body text and pale captions feel calm and premium on a bright monitor. On a phone in the sun, on a cheap laptop screen, or for anyone over 50, they are hard to read. Low contrast doesn't only hurt people with a diagnosed visual impairment. It hurts nearly everyone a little.&lt;/p&gt;

&lt;p&gt;The fix is usually one line: a darker grey for body text, or a dark overlay behind text that sits on a photo.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Links with no readable name (34%)
&lt;/h3&gt;

&lt;p&gt;This is almost always an icon link: a logo in the footer, a social media icon, a "menu" or "search" icon with no text. A screen reader user hears "link" and nothing else. Imagine a page where five buttons all say "link".&lt;/p&gt;

&lt;p&gt;The fix is an &lt;code&gt;aria-label&lt;/code&gt; ("LinkedIn", "Open menu") or hidden text inside the link.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Visible label doesn't match the hidden name (24%)
&lt;/h3&gt;

&lt;p&gt;A button says "Get started", but in the code its hidden name is "Sign up for our free trial today". People who control their computer by voice say what they see: "click Get started". If the hidden name doesn't contain those words, nothing happens.&lt;/p&gt;

&lt;p&gt;The fix is to make the hidden name start with the visible text, or remove the hidden name and let the visible text do the job.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Tap targets too small on phones (21%)
&lt;/h3&gt;

&lt;p&gt;WCAG 2.2 added a minimum target size: 24 by 24 CSS pixels, or enough space around a smaller target. Tiny footer links and close buttons packed next to each other are the usual problem. For someone with a tremor, or anyone using their thumb on a bus, it means hitting the wrong thing.&lt;/p&gt;

&lt;p&gt;The fix is padding. The link can look the same; the tappable area just gets bigger.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Images with no text description (18%)
&lt;/h3&gt;

&lt;p&gt;Images that carry meaning (a product photo, a chart, a logo in a "trusted by" row) need alt text so a screen reader can describe them. Without it, a screen reader may read out the file name, like "IMG_4471_final_v2.jpg". Images that are pure decoration should have an empty alt (&lt;code&gt;alt=""&lt;/code&gt;) so they're skipped.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Buttons with no readable name (13%)
&lt;/h3&gt;

&lt;p&gt;The same problem as links, on buttons: a play button, a carousel arrow or a hamburger menu built from an icon with no label. Same fix: an &lt;code&gt;aria-label&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Zooming blocked on phones (12%)
&lt;/h3&gt;

&lt;p&gt;A single setting in the page's code (&lt;code&gt;user-scalable=no&lt;/code&gt; or a low &lt;code&gt;maximum-scale&lt;/code&gt; in the viewport tag) stops people from pinch-zooming. People with low vision rely on zoom. Removing that setting is a one-line change and almost never breaks anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Scroll areas you can't reach with a keyboard (11%)
&lt;/h3&gt;

&lt;p&gt;A box with its own scroll bar (a long list, a code sample, a horizontal row of cards) that can't get keyboard focus. Someone who can't use a mouse sees the first part and can never scroll to the rest. Adding &lt;code&gt;tabindex="0"&lt;/code&gt; and a label to the scroll box usually fixes it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 45 near-misses
&lt;/h2&gt;

&lt;p&gt;The number I find most hopeful is the 45 smaller companies that were one failing rule away from passing. That's more than five times as many as passed.&lt;/p&gt;

&lt;p&gt;For many of them the missing piece is one of the items above: a darker grey, a label on the footer icons, a zoom setting. A developer can fix most of those in an afternoon. To be precise about what "one rule away" means: a single rule can affect many elements on the page, and a site also needs a score of 90 to pass. So fixing that one rule gets a site close, and for most of them it would be enough, but I haven't re-tested them to prove it.&lt;/p&gt;

&lt;p&gt;If your site is one of them, you can &lt;a href="https://wolfitway.com/tools/wcag" rel="noopener noreferrer"&gt;re-run the same test yourself&lt;/a&gt; after a fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an automated test can't tell you
&lt;/h2&gt;

&lt;p&gt;Automated tools find a real share of accessibility problems, but nowhere near all of them. Here is what this test does &lt;strong&gt;not&lt;/strong&gt; check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Whether alt text makes sense.&lt;/strong&gt; It can see that an image has a description. It can't tell whether "image" or "banner" describes anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whether the page makes sense with a screen reader.&lt;/strong&gt; Reading order, whether headings tell a story, whether a form explains its errors.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whether everything works with a keyboard alone.&lt;/strong&gt; Menus that open on hover, pop-ups you can't close, focus that jumps to the wrong place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anything after the homepage.&lt;/strong&gt; Sign-up, checkout, booking, account pages. For an online shop, those matter more than the homepage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every state of the page.&lt;/strong&gt; The scan sees the page as it first loads, after the cookie banner. It doesn't open every menu or slide every carousel, and it doesn't test content inside third-party iframes (video players, chat widgets, maps).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real devices.&lt;/strong&gt; The phone test is Chrome in phone mode, not Safari on an iPhone with VoiceOver.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So, two honest readings of the results:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A fail is specific.&lt;/strong&gt; Every fail comes with a list of WCAG problems on named elements, with screenshots, so anyone can check them. Automated rules are tuned to avoid false alarms, but they're not perfect, which is why a person should confirm before fixing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A pass is a good start, not a finish line.&lt;/strong&gt; It means the homepage cleared every automated check on that day. It doesn't mean the site is fully accessible, and it doesn't make anyone "compliant" with the European Accessibility Act. Nothing automated can do that.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What this means for the European Accessibility Act
&lt;/h2&gt;

&lt;p&gt;The Act covers specific products and services, among them e-commerce, banking, transport, telecoms, e-books and some media services. Very small businesses providing services (fewer than 10 staff and no more than €2 million turnover) are exempt. Whether it applies to a given company depends on what they sell and how big they are, so I'm not saying any company in this study is breaking the law. I don't know their situation, and an automated scan couldn't prove it either way.&lt;/p&gt;

&lt;p&gt;What I can say: if the homepages of 271 real companies are any guide, most websites aren't ready yet, including the ones with the biggest budgets. And the most common problems are not hard engineering. They are design choices (pale text, tiny links) and small omissions (a missing label). That's good news. It means most sites can make real progress in days, not months.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you run a website: start here
&lt;/h2&gt;

&lt;p&gt;From this data, these five fixes would cover the most common failures:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check your text contrast.&lt;/strong&gt; Body text, captions, footer text and any text on a photo. Aim for 4.5:1. Darken the grey or add an overlay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Name every icon.&lt;/strong&gt; Every icon-only link and button gets an &lt;code&gt;aria-label&lt;/code&gt; that says what it does.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Match labels to what's visible.&lt;/strong&gt; If a button reads "Get started", its accessible name should start with "Get started".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Let people zoom.&lt;/strong&gt; Remove &lt;code&gt;user-scalable=no&lt;/code&gt; and &lt;code&gt;maximum-scale=1&lt;/code&gt; from your viewport tag.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make small targets bigger.&lt;/strong&gt; Give footer links, close buttons and pagination dots at least 24 x 24 px of tappable space.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then do the part no tool can: try your own homepage with only the keyboard (Tab, Enter, Esc), and once with your phone's screen reader turned on. Ten minutes of that will teach you more than any score.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Hall of Fame
&lt;/h2&gt;

&lt;p&gt;The homepages that passed are in the &lt;a href="https://wolfitway.com/museum/hall" rel="noopener noreferrer"&gt;Accessibility Hall of Fame&lt;/a&gt;, with the date they were tested. Only passing sites are ever shown there. I don't publish any site's failing score, and no failing company is named in this article. Sites change, and a fail on 2 November says nothing about next month.&lt;/p&gt;

&lt;p&gt;Want to know where your homepage stands? &lt;a href="https://wolfitway.com/tools/wcag" rel="noopener noreferrer"&gt;Scan it free with the same test&lt;/a&gt;. It's the same test the 379 homepages got: every problem, where it is, and how to fix it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is 379 a big enough sample?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It's big enough to show a clear pattern (low contrast on nearly 9 in 10 tested homepages is not noise). It's not big enough to rank countries or industries against each other, so I haven't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why not test more pages per site?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Time and fairness. Homepages are the one page every company has. A full-site study would need a different method, and a lot of manual work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why were so many sites blocked?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Bot protection. It's built to stop scrapers and attacks, and an automated accessibility test looks like a robot because it is one. I didn't try to get around it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a pass mean the site is accessible?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It means the homepage passed every automated WCAG A and AA check I ran, with no critical or serious problems, on the day of the test. A full accessibility review also needs people testing with assistive technology.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which tool did you use?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;axe-core 4.14 (open source, by Deque) inside my own scanner, plus a pixel-based contrast check for text on images and gradients. The scanner is the same one behind the free &lt;a href="https://wolfitway.com/tools/wcag" rel="noopener noreferrer"&gt;WCAG check&lt;/a&gt; on this site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use these numbers?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes, please do. A link to this article as the source is all I ask, and please quote how many sites were tested, not just tried.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method in one paragraph
&lt;/h2&gt;

&lt;p&gt;Group 1: 279 companies from public listings (Wikidata companies registered in DE/GB/NL/RO, BetaList, Y Combinator, Show HN, HN "Who is hiring?", Remote OK, 5 added by hand), all tried, 209 tested, scanned 22 October to 10 November 2026. Group 2: the top 100 listed companies by market value from CompaniesMarketCap, ranking saved 2 November 2026, fixed in advance with no substitutions, 62 tested, scanned 2 November 2026. Homepage only, desktop 1440 x 900 and Chromium phone emulation 390 x 844, axe-core 4.14 with WCAG 2.0/2.1/2.2 A and AA rules plus a pixel contrast check for text on images and gradients, cookie banners dismissed where possible, 20-second page load limit. Only confirmed WCAG failures are scored (100 minus 15/8/3/1 per critical/serious/moderate/minor rule, scaled by the log of affected elements). Pass = score 90 or more with zero critical and zero serious problems. Sites that couldn't be tested are excluded, not counted as fails. Results describe each page on the day it was scanned.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;How to cite: Wolfitway, "We tested 379 company homepages for accessibility. 9 passed", November 2026, wolfitway.com.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/website-accessibility-study-2026" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>a11y</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Gemini 4 Leaks: What They Show, What Is Unverified, and Why Google's Data Matters</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Sun, 04 Oct 2026 05:31:24 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/gemini-4-leaks-what-they-show-what-is-unverified-and-why-googles-data-matters-ob9</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/gemini-4-leaks-what-they-show-what-is-unverified-and-why-googles-data-matters-ob9</guid>
      <description>&lt;p&gt;&lt;em&gt;Important up front: none of what follows is confirmed by Google. Everything here is leaked, rumoured or posted by third parties. Treat it as speculation, not news.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I made this video
&lt;/h2&gt;

&lt;p&gt;Most "Gemini 4 leaked" videos are polished and scripted. I wanted to do the opposite: open a browser, look at the leaks as a normal user would, and react live. No script, no strategy.&lt;/p&gt;

&lt;p&gt;Before we start, one question to keep in mind. Every AI model needs data to produce a result. Who has the most data right now? Google. That, more than any benchmark, is the angle that could change things. Google either makes a serious comeback with workflows and automation built on that data, or this becomes another flop. Either outcome would surprise nobody.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step one: ask Gemini itself
&lt;/h2&gt;

&lt;p&gt;I asked Gemini directly whether the Gemini 4 leaks are real. The short answer it gave: no, they are not officially confirmed, and parts of them appear fabricated or unverified. That sets the tone. From here on we are speculating.&lt;/p&gt;

&lt;h2&gt;
  
  
  The "Argon" checkpoint claims
&lt;/h2&gt;

&lt;p&gt;One of the first accounts to post about it on X shared what it described as the first output from a Gemini 4 Pro checkpoint, internally code-named &lt;strong&gt;Argon&lt;/strong&gt;: a block-built 3D scene that looks like something you would make in Blender. The claims attached to it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The output took about 2.4 minutes on high thinking effort.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;An output limit of around 256K tokens, compared with 64K in previous Gemini models.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A context window of 2 million tokens at launch, roughly double what competitors offer today.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If those numbers hold, more context means much bigger jobs in one go: whole codebases, long document sets, full projects in a single request.&lt;/p&gt;

&lt;h2&gt;
  
  
  Benchmarks and pricing
&lt;/h2&gt;

&lt;p&gt;Several posts claim wild benchmark scores, high speed and low pricing. The figures circulating are roughly $2.25 per million input tokens and $11.25 per million output tokens. Nobody has verified the benchmarks or the prices. If the pricing is real, it would put pressure on the whole market.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3D demos
&lt;/h2&gt;

&lt;p&gt;This is where the leaks get interesting. The examples shared on Reddit and X include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A detailed race car&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A 3D city building, so architecture as well as objects&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A ship, and transformations of scenes&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The classic "pelican on a bicycle" test, with customisation&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A pagoda shown side by side: the older Flash model's version next to the claimed Gemini 4 Pro version. The difference is night and day.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If any of these came from one prompt with no outside software, that is a big shift. Anyone who has tried to get results like these in Blender or another 3D tool knows how much work they take.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it would mean if it is real
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Websites will not stay the same.&lt;/strong&gt; Interactive 3D that used to need a specialist could become a prompt.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Workflows and automation.&lt;/strong&gt; Huge context plus Google's data and products is where the real leverage would be.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Price pressure.&lt;/strong&gt; Cheap, capable models change what is worth building yourself.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  My take
&lt;/h2&gt;

&lt;p&gt;We have to wait for the official release. But there is rarely smoke without fire, and if the final model looks anything like these leaks, it will probably surprise us even more.&lt;/p&gt;

&lt;p&gt;The lesson for your business is the same either way: don't build on any single model. Build your own data, workflows and stack so you can switch to whichever model wins.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want an AI setup you own?
&lt;/h2&gt;

&lt;p&gt;I build AI workflows and automation that you own, so you can switch models without starting over. &lt;a href="https://wolfitway.com/book" rel="noopener noreferrer"&gt;Book a free call&lt;/a&gt; and we will look at what makes sense for your business.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/gemini-4-leaks-reaction" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>gemini</category>
      <category>google</category>
    </item>
    <item>
      <title>Stop Copying Successful Businesses: Build a Sovereign Moat Instead</title>
      <dc:creator>Dan Draguta</dc:creator>
      <pubDate>Sat, 03 Oct 2026 20:01:40 +0000</pubDate>
      <link>https://dev.to/dan_draguta_d18e1735edb6c/stop-copying-successful-businesses-build-a-sovereign-moat-instead-fl</link>
      <guid>https://dev.to/dan_draguta_d18e1735edb6c/stop-copying-successful-businesses-build-a-sovereign-moat-instead-fl</guid>
      <description>&lt;p&gt;Stop trying to copy successful businesses. It doesn't matter if you have their exact funnel, their exact ad spend or their exact code.   &lt;/p&gt;

&lt;p&gt;You will still lose. The copy-paste model of entrepreneurship is broken, and in the age of AI the only thing that can't be copied is you.  &lt;/p&gt;

&lt;h2&gt;
  
  
  The copycat paradox
&lt;/h2&gt;

&lt;p&gt;The usual advice is: find a competitor, reverse-engineer their success and do it better. That is advice for employees, not for founders who want to own what they build.&lt;/p&gt;

&lt;p&gt;We are moving from the information age to the synthesis age. In the synthesis age the &lt;strong&gt;how&lt;/strong&gt; is free. The &lt;strong&gt;why&lt;/strong&gt; is the only asset you have.&lt;/p&gt;

&lt;h2&gt;
  
  
  The industrial mindset is holding you back
&lt;/h2&gt;

&lt;p&gt;We were taught that a business is a machine: inputs go in, outputs come out, and if you want the same output you copy the machine. That worked in 1950 and in 1990.&lt;/p&gt;

&lt;p&gt;Today the machine is software, and software can be copied endlessly. If your business depends on a specific stack, a specific marketing tactic or a specific pricing model, you are a commodity. Commodities compete on price, and that is a race to the bottom.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;

&lt;strong&gt;The clone&lt;/strong&gt; focuses on the what and the how: "Which feature don't they have? How do I build a cheaper version?"&lt;/li&gt;
&lt;li&gt;

&lt;strong&gt;The sovereign&lt;/strong&gt; focuses on the who and the why: "Who am I uniquely positioned to serve, and why am I the only logical choice?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can copy the map, not the territory&lt;/p&gt;

&lt;p&gt;A business isn't a product. It is a context engine. When you look at Apple or Tesla you see the product. You don't see 20 years of context: the relationships, the supply-chain quirks, the cultural timing that let that product exist.&lt;/p&gt;

&lt;p&gt;Copying a business means copying the map while trying to navigate a territory that has changed since the map was drawn. In tech, tactics last about six months. Spend a year copying a competitor's strategy and by launch it no longer works. You are chasing a ghost.&lt;/p&gt;

&lt;p&gt;The contextual moat: a three-part system&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Data gravity&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Data isn't just numbers. It is gravity: it pulls people in. A clone has generic data ("here is a generic guide to losing weight"). A sovereign has proprietary data ("here is three years of biometric data from my community of 1,000 users showing a link between sleep and cortisol").&lt;/p&gt;

&lt;p&gt;You can't copy that data. You have to generate it and earn it. The business isn't the software. It is the feedback loop that makes the software smarter every day.  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Network topology&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is who you know and how you connect them. A clone builds a user base. A sovereign builds a network.&lt;/p&gt;

&lt;p&gt;A SaaS tool with only users will churn. A SaaS tool that connects specific freelancers with specific high-end clients isn't selling software any more. It is selling access, and access can't be copied.&lt;/p&gt;

&lt;p&gt;A real example: someone I know runs a niche job board for underwater welders. Anyone could copy the website. Nobody can copy the fact that he personally knows the top 50 hiring managers in that industry. That is his moat, and he earned it.  &lt;/p&gt;

&lt;h3&gt;
  
  
  3. Sovereign identity
&lt;/h3&gt;

&lt;p&gt;This is the hard part for tech people: you have to put yourself into the business. When AI can write 1,000 blog posts a minute, the only thing that matters is trust. Trust doesn't scale in the usual way. It is earned through friction.&lt;/p&gt;

&lt;p&gt;When you copy someone, you are a guest in their house, playing by their rules. When you build your own moat, you set the rules: "This is how we do things here. If you don't like it, that's fine." That friction is a filter. It builds a following, not just a customer list.&lt;/p&gt;

&lt;p&gt;The audit: do this now&lt;/p&gt;

&lt;p&gt;Look at your business model and product and ask one question:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;If a competitor stole my entire codebase and content library tomorrow, would I still win?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the answer is no, you are in the copycat trap. If it is yes, it's because at least one of the three is present: data, network or identity.&lt;/p&gt;

&lt;p&gt;From features to philosophy&lt;/p&gt;

&lt;p&gt;Stop selling 10 GB of storage. Start selling ownership of your data. Stop selling "marketing services". Start selling a contrarian growth philosophy, for example one that rejects paid ads.&lt;/p&gt;

&lt;p&gt;Yes, this alienates people. That is the point. You lose the people who would have copied you anyway and attract the people who share your worldview. You can't be independent while begging for attention by copying trends.   &lt;/p&gt;

&lt;p&gt;You become sovereign when you become the source, and when you are unapologetic about who you are, what you want and what you do.&lt;/p&gt;

&lt;p&gt;The moat nobody talks about: shared struggle&lt;/p&gt;

&lt;p&gt;The biggest moat isn't the code or the marketing. It is the shared struggle. When you copy a business you inherit its success but not its scars, and your audience connects with your scars: the time you failed, pivoted or nearly went broke.&lt;/p&gt;

&lt;p&gt;A clone has no scars. It is smooth, polished and boring. So document the war, not just the victory. If you are building a SaaS, show the bugs, the server crashes and the customer complaints. That transparency is the ultimate copy protection, because a copycat can't fake your pain.&lt;/p&gt;

&lt;p&gt;The bottom line&lt;/p&gt;

&lt;p&gt;You can't copy a business because you can't copy the context, the timing or the messy network of human relationships that made it work. Stop looking at your competitors and look at your own architecture:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;

Build data gravity.&lt;/li&gt;
&lt;li&gt;

Build a network.&lt;/li&gt;
&lt;li&gt;

Build a sovereign identity.&lt;/li&gt;
&lt;li&gt;

Embrace the struggle. That is your moat.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Don't be a clone. Be the source.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build your moat with me
&lt;/h2&gt;

&lt;p&gt;I help founders use AI to build moats like these instead of letting AI wipe them out: your own data, your own stack, no vendor lock-in. &lt;a href="https://wolfitway.com/book" rel="noopener noreferrer"&gt;Book a free call&lt;/a&gt; and we will map out yours.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://wolfitway.com/blog/stop-copying-successful-businesses-sovereign-moat" rel="noopener noreferrer"&gt;wolfitway.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>startup</category>
    </item>
  </channel>
</rss>
