Home
/
Blog
/
Web Design

Web development best practices for 2026

Web Design
Maximillian Giddens
Maximillian Giddens
November 10, 2026
10
min read
TL;DR

Most websites still fail the basics. Only 48% of mobile sites pass Google's Core Web Vitals, and 95.9% of the top million home pages have detectable WCAG failures. The fixes are old and unglamorous: set a speed budget, write semantic HTML, build to WCAG 2.2 AA, apply security fixes within a day and put your content in HTML that AI crawlers can read. Then measure real visitors, and keep the stack simple enough to maintain.

Web development best practices for 2026
Maximillian Giddens

Written by

Maximillian Giddens
Web Developer + SEO Executive

Max builds most of what you see on our sites, then makes sure Google can read it. He works in loops: build, test, pull it apart, build it better. His best fixes arrive out of nowhere, usually with the headphones on and something loud playing. Ask him which DJ set changed his life and clear your afternoon.

Read bio ↓

Fewer than half of mobile websites pass Google's Core Web Vitals. The 2025 Web Almanac puts it at 48%. Accessibility is worse: WebAIM's 2026 scan found WCAG failures on 95.9% of the top million home pages. That's the case for web development best practices in two numbers.

Most sites fail on problems the industry has understood for a decade: hero images that load last, forms with no labels, plugins nobody updates. Then there's content that only appears once JavaScript runs, which many AI crawlers never see.

This guide covers the practices that move those numbers in 2026, with the evidence behind each. It's written for people who commission websites as much as for the people who build them. If you're paying for a new site, use it as a list of questions for whoever builds it.

None of it needs a bigger budget. It needs someone who still cares about the site a year after launch.

What are web development best practices in 2026?

Web development best practices are the build habits that make a site load quickly on a mid-range phone, work for disabled visitors, resist known exploits and stay cheap to change after launch. In 2026 that means a speed budget, semantic HTML, WCAG 2.2, fast patching, content crawlers can read and data from real visitors.

Web development is the engineering under the design: the code, the hosting, the CMS and everything else that decides how a page behaves. If the line between the two is blurry, we've written up where web design ends and development starts.

Very little on this list is new. What's changed is the price of skipping it.

Google now scores responsiveness with Interaction to Next Paint, which replaced First Input Delay in March 2024. WCAG 2.2 became an international ISO standard in October 2025. And AI tools now read your pages alongside Google, often with less patience for JavaScript.

How fast should a website load in 2026?

Fast enough to pass Google's Core Web Vitals for real visitors. The main content should appear within 2.5 seconds, taps should get a response within 200 milliseconds and the layout shouldn't jump (a shift score under 0.1). Google measures all three at the 75th percentile of page loads, so one fast test on your laptop proves very little.

Those three measures are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). In the 2025 Web Almanac, 48% of mobile sites passed all three, up from 36% in 2023. LCP is where most sites fall down. Good INP and CLS scores were common (77% and 81% of mobile sites), but only 62% had good LCP.

Some of that damage is self-inflicted. About 16% of pages lazy-load the image that's meant to appear first, which tells the browser to fetch the most important picture last. And 62% of mobile pages have at least one image without set dimensions, so the layout jumps when it arrives.

Weight is the slower problem. The median mobile home page has nearly tripled in size since 2015 and now ships 632 KB of JavaScript. Median mobile Total Blocking Time rose 58% in a year, to 1,916 milliseconds. That's almost two seconds in which the browser is too busy running scripts to respond quickly.

The fix is a performance budget. Agree the numbers before design starts: an LCP target, a cap on JavaScript and a maximum page weight. Then hold every new feature to them. Speed is lost by a thousand small yeses, and a chat widget has to earn its place like anything else.

Write HTML that means something

Semantic HTML means using the element built for the job: a button for actions, a link to go somewhere, a label on every form field and headings in order. It costs nothing at build time. Screen readers, search engines and AI crawlers all lean on it to work out what a page says.

Get it wrong and people and machines both lose the thread. If your main heading is a styled div, nothing reading the code knows it's the heading. If your menu button is a div with a click handler, a keyboard user can't reach it.

The common shortcut is to patch bad markup with ARIA attributes. WebAIM found that home pages using ARIA averaged 59.1 detectable errors, against 42 on pages without it. The pattern makes sense. ARIA tends to turn up on custom widgets rebuilt from divs, where it's covering for behaviour a native element would have given you free.

Use the native element first. Reach for ARIA only when HTML has nothing that fits.

What accessibility standard should a UK website meet?

Build to WCAG 2.2 at level AA. UK public sector websites must meet it, and it became an ISO standard in October 2025. Every UK service provider must also make reasonable adjustments under the Equality Act 2010, and WCAG 2.2 AA is the clearest evidence you've done so. Sell into the EU and the European Accessibility Act applies too.

The audience is bigger than most clients guess. About one in four people in the UK report a disability. Add ageing eyes, a cracked screen or a phone in bright sun, and far more of your visitors benefit from decent contrast and clear labels.

The European Accessibility Act has applied since 28 June 2025. It reaches UK businesses that sell covered products and services, online shops included, to consumers in the EU.

Most failures are boring. Six problems make up 96% of the errors WebAIM detected: low-contrast text (on 83.9% of home pages), missing alt text (53.1%), missing form labels (51%), empty links, empty buttons and a missing page language. Fix those six and most automated errors go away. Then test with a keyboard and a screen reader, because automated checks can't catch everything.

How do you keep a website secure?

Apply security updates within a day, run as few plugins as you can, put two-factor login on every admin account and keep backups you've tested. Timing matters most. The most heavily exploited WordPress vulnerabilities are attacked at scale a median of five hours after they go public.

Breaches are common. The government's Cyber Security Breaches Survey 2025/26 found 43% of UK businesses had a breach or attack in the previous 12 months. Phishing was the most common, hitting 38% of all businesses. Yet only 47% use two-factor authentication, and just 5% hold Cyber Essentials.

If your site runs on WordPress, plugins are the soft spot. Patchstack logged 11,334 new vulnerabilities in the WordPress ecosystem in 2025, up 42% on 2024. Plugins accounted for 91% of them, and 46% had no fix from the developer by the time they went public. A monthly update routine can't keep pace with that.

Hosted platforms change the job without removing it. On Webflow, the provider patches the servers and the platform code, so there's no plugin update queue to manage. Headless builds keep the CMS (Sanity, for example) separate from the public site, which shrinks what an attacker can reach. Neither protects a reused password, and that's what two-factor login is for.

We've compared the trade-offs in Webflow vs WordPress. Whoever looks after your site, get the patching routine in writing. Here's what a website care plan should include.

Which web development best practices help in AI search?

AI search rewards the same basics as Google. Put your content in the HTML, use clear headings, keep pages fast and check crawlers aren't blocked. Google says its AI features need no special files or markup. Most other big AI crawlers don't run JavaScript, so content that only loads through scripts may never reach them.

Google's guide to its generative AI features, last updated in July 2026, is blunt about it. You don't need llms.txt files, AI-specific markup or content chopped into tiny chunks, and Google Search ignores those files anyway. What it asks for is crawlable pages and useful, original content.

Structured data still earns rich results in normal search, so keep it. Just keep it matching what's on the page.

Google can render JavaScript. Many other AI crawlers can't. When Vercel analysed traffic across its network in late 2024, OpenAI's and Anthropic's crawlers downloaded JavaScript files without running them, and OpenAI's GPTBot alone made 569 million requests in a month.

If your prices, services or reviews only appear after a script runs, those tools may never see them. Server-rendered or static HTML fixes that.

Also check nothing is blocking them by accident. Since July 2025, new Cloudflare accounts block known AI crawlers by default, so a site can drop out of AI answers without anyone touching robots.txt. We've covered what Cloudflare's AI standoff means for SEO, and you can run your site through our free AI SEO audit to see where it stands.

Measure what real visitors get

A Lighthouse score comes from one simulated visit on one simulated phone. Google's Core Web Vitals assessment uses field data from real Chrome users, which you'll find in PageSpeed Insights and the Core Web Vitals report in Search Console. When the lab and the field disagree, believe the field.

For your own numbers, Google's open-source web-vitals library can send LCP, INP and CLS from every visit into your analytics. That shows you which pages and devices are slow, which a single test never will.

Test on the phone your customers carry. Google uses the mobile version of your site for indexing and ranking, and a mid-range Android on mobile data will show you problems a MacBook never will: tap targets too small, layouts that crush, forms that fight the keyboard.

One UK change makes measuring easier. The Data (Use and Access) Act 2025 added an exception to the cookie rules for analytics. Under the ICO's guidance, you can set analytics cookies without consent if their only purpose is statistics that improve your site, visitors are told and given a simple, free way to object, and any third-party provider acts as your processor.

Anything linked to advertising still needs consent, so check your setup against the ICO's wording before you change your banner. Our website analytics best practices cover what to track once it's running.

Pick boring tools on purpose

The best stack for a business website is the one your team can still run in a year. Build for the person maintaining it then, who may not be the person who built it. A site only its original developer understands turns into a rebuild the day that developer moves on.

Most marketing sites don't need a heavy JavaScript framework. They need fast HTML and a CMS the marketing team can use without filing a ticket. Before adding a library, check the Baseline status of the native feature. Baseline "widely available" means a feature has worked across Chrome, Edge, Firefox and Safari for at least 30 months, so plenty of old polyfills and plugins can go.

We build on Webflow and Sanity. Both let a marketing team publish without a developer, and that matters more to most businesses than any framework benchmark. If you're commissioning a new website, ask who will update it a year from now, and ask to see the documentation they'll work from.

None of this photographs well

Speed budgets, form labels and patch schedules never make the portfolio. Nobody screenshots a 1.9-second LCP. They still decide which sites keep earning for five years and which get rebuilt after two.

If you only do a few things this year, start with the field data in Search Console. Fix the six accessibility errors WebAIM keeps finding. Get a patching routine in writing. Then switch JavaScript off in your browser and look at what's left of your homepage.

Whatever's missing is missing for a lot of AI crawlers too. The checks take an afternoon. Keeping them passing is the habit.

Maximillian Giddens

Written by

Maximillian Giddens

Web Developer + SEO Executive

Max builds most of what you see on our sites, then makes sure Google can read it. He works in loops: build, test, pull it apart, build it better. His best fixes arrive out of nowhere, usually with the headphones on and something loud playing. Ask him which DJ set changed his life and clear your afternoon.

Questions

Web development questions, answered straight.

Forty second answers with no jargon. Anything else, ring the office and ask whoever picks up.

Does page speed affect Google rankings?

Yes, though relevance comes first. Google says Core Web Vitals are used by its ranking systems, and also that it will show the most relevant page even when its page experience is poor. Speed counts most when several pages answer a search equally well. It always counts for the visitor waiting on a slow page.

What are the Core Web Vitals thresholds?

Largest Contentful Paint should be 2.5 seconds or less, Interaction to Next Paint 200 milliseconds or less, and Cumulative Layout Shift 0.1 or less. Google assesses each one at the 75th percentile of page loads, separately for mobile and desktop. INP replaced First Input Delay as the responsiveness measure in March 2024.

Is WCAG 2.2 a legal requirement for UK websites?

For public sector websites, yes: they must meet WCAG 2.2 at level AA. The law doesn't name a standard for private businesses. Every UK service provider still has a duty to make reasonable adjustments under the Equality Act 2010, and WCAG 2.2 AA is the clearest way to show you've met it. If you sell covered products or services to EU consumers, the European Accessibility Act applies as well.

Do I need an llms.txt file for AI search?

Not for Google. Its guide to generative AI features says you don't need AI text files such as llms.txt to appear in Google Search, and that Google Search ignores them. Your time is better spent getting content into the HTML and checking crawlers aren't blocked.

How quickly should I install security updates?

Within a day for anything marked as a security fix, and sooner for a popular plugin. Patchstack found the most heavily exploited WordPress vulnerabilities were attacked at scale a median of five hours after going public, and 46% of new vulnerabilities had no fix at disclosure. Automatic updates and a web application firewall cover that gap better than a monthly check.

How can I check my website against these best practices?

Start with free tools. PageSpeed Insights and the Core Web Vitals report in Search Console show real-visitor speed data. WAVE flags the common accessibility errors, and a keyboard-only run through your main pages catches more. For security, compare your CMS and plugin versions with the latest releases and confirm two-factor login is on for every account.

Build bold · Grow fast

Know your price before you pick up the phone.

CONTACT US