Web design for 2027: what is actually changing for small-business sites
Native page transitions, layouts that adapt per component, sites read by AI before people, and speed measured on every tap. What I am changing in 2027 builds, and what I am not.
Every year there is a “design trends” list full of gradients and 3D blobs. That is not this. This is the short list of changes I’m actually making on the small-business sites we build heading into 2027, and the reasons behind them.
1. Page transitions without a framework
For years, the smooth slide from one page to the next was something only single-page apps could do, and it came with a pile of JavaScript. Browsers now have a built-in answer, the View Transition API, which can animate between two separate pages of a normal site (MDN).
Why I care… it lets a fast, simple multi-page site feel as polished as an app, and a browser that does not support it just loads the next page like it always has. Nobody gets a broken site. That is the kind of upgrade I like, all upside and a safe floor.
The rule I use: the transition has to be short, and it has to respect the visitor’s reduced motion setting. More on that in Motion graphics on a small-business site.
2. Layouts that adapt per component, not per screen
Old responsive design asked one question: how wide is the screen? Container queries let a component ask how much room IT has (MDN). A service card can be a wide row in the main column and a tight stack in a sidebar, using the same code.
For an owner this mostly shows up as fewer weird layouts. The page you edit in your CMS looks right wherever that block lands, without a developer adding a special case.
3. Your site gets read by AI before it gets read by people
This is the BIG one. A growing share of people ask an assistant “who does X near me” and get an answer that was built from somebody’s website. Sometimes they click through. Often they do not.
What that rewards is not new. It is the same stuff good SEO always wanted, done properly:
- Real HTML headings that match what people ask.
- Plain text for your services, your service area and your prices, not text baked into images.
- Structured data that says who you are, where you are and what you offer.
- Pages that render without waiting on a script.
We publish an llms.txt file on our own site, a short plain-text map of the important pages, following the proposal at llmstxt.org. I wouldn’t call it a ranking factor, it’s too early to say that, BUT it costs almost nothing and it makes the site easier for these tools to read. I go deeper in Designing for AI answers.
4. Speed is measured on every tap, not just the first load
Google’s responsiveness metric is now Interaction to Next Paint, which looks at how quickly the page reacts to taps and clicks across the whole visit. Good is 200 milliseconds or less (web.dev).
That changes how I think about scripts. A site can load fast and still feel sticky when someone taps the menu, because a chat widget and three trackers are fighting for the main thread. The fix is usually less, not more: fewer third-party scripts, and the ones that stay load late.
I made the longer case for this in Why your website should be boring and fast.
5. Motion that means something
Motion is back, and I’m glad. Scroll-driven animations can now run in CSS without a library, and WebGL is fast enough on a mid-range phone to do real things. Our own home page has a WebGL hero.
BUT the bar is higher, not lower. Motion has to tell the visitor something, it has to stay out of the way of the content, and it has to stop when nobody is looking at it. I’ll cover the how-to in Scroll-driven animation and view transitions without a library.
What I’m NOT changing
- The phone number and the main call to action stay at the top.
- Forms stay short.
- Text stays readable at a normal size with real contrast.
- Hosting stays on the edge, static first, so a page is HTML on a server close to the visitor. The reasoning is in Why we build on Cloudflare.
None of those are trends. They’re the reason the site exists.
Where to start
If you’re planning a refresh for next year, start by opening your own site on your phone, on cellular, and tapping around for two minutes. Anything that feels slow or confusing goes on the list first. The trends come after.
If you’d like help sorting that list, let me know. Thanks!
FAQ
Frequently asked questions.
The questions clients ask most after reading this.
Do I need a redesign for 2027?
What are view transitions?
How do AI assistants affect web design?
More development reading
Related from the lab.
Development
How AI changes a website build in 2027, and what it doesn't
AI now writes a lot of the code and first drafts on a website project. What that speeds up, what still takes a person, and what to ask any web designer about how they use it.
3 min
Development
Scroll-driven animation and view transitions without a library
Browsers can now animate page changes and tie animation to scrolling in plain CSS. A practical walkthrough with code, the reduced motion guard, and how to ship it as a safe enhancement.
3 min
Development
Designing for AI answers: how a 2027 website gets read by machines and people
More people meet your business through an AI answer before they visit your site. What we do on our own site so assistants read it correctly: clean HTML, structured data, llms.txt and a plain-text twin of every page.
3 min