Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Web development tips for a fast site that converts

Updated · 9 min read

Short answer Build for the phone first, with the same content as desktop. Keep the first screen light: sized, compressed images and few add-on scripts. Give each service its own page with plain links. Build in form labels, readable contrast and big tap targets. Before launch, check Google isn't blocked, redirect old addresses and test on a real phone.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Web development tips: the 12 to build in

Each item is cheapest to get right while the pages are built. Hand this table to whoever builds your site, or check it yourself on Wix or Squarespace.

#Build this inWhyHow to check
1HTTPS on every pageChrome now asks permission before opening a public site without itType http:// and your domain: it should switch to https://
2Same content on phone and desktopGoogle ranks the phone versionPrices, reviews and service details all show on a phone
3Layout that fits the screenWithout a viewport tag, phones show a zoomed-out pageRead every page on a phone without pinching
4Buttons at least 24 by 24 pixelsThe accessibility standard's minimum tap targetTap each button with a thumb
5Phone number as a tap-to-call linkOne tap starts the callTap it on a phone
6Compressed images with set sizes; top image not lazy-loadedBig photos slow the first screen; missing sizes make the page jumpPageSpeed Insights on mobile
7Few third-party scriptsChat widgets, trackers and embeds slow pagesList every add-on; remove what nobody uses
8One page per service, readable addressesEach page can match one search/drain-cleaning/, words split by hyphens
9Menus made of real linksGoogle follows standard linksRight-click a menu item: "Open link in new tab" appears
10A unique title per pageSearchers see the title firstRead each browser tab
11Forms with labels and autofillFaster on a phone; usable with a screen readerFill every form on a phone, then by keyboard only
12Tracking live on launch dayLeads you didn't record can't be countedCalls, forms and bookings show in Google Analytics

How fast should a small business website be?

Fast enough to pass Google's three Core Web Vitals on phones. web.dev says they cover "loading, interactivity, and visual stability": main content within 2.5 seconds, a response to a tap within 200 milliseconds, and a layout shift score of 0.1 or less. Details: Core Web Vitals: does speed affect ranking?

Speed helps, but relevance wins:

"Google Search always seeks to show the most relevant content, even if the page experience is sub-par." (Google Search Central: Understanding page experience)

Build decisions that keep a page fast:

  • Set image sizes. web.dev: "Always include width and height size attributes on your images and video elements." Otherwise text jumps as photos load, and visitors tap the wrong thing.
  • Load the top image first. Lazy-loading (fetching images only as they scroll into view) is fine lower down, but web.dev warns: "Never lazy-load your LCP image," the biggest item on the first screen.
  • Resize before you upload. A photo straight off a phone is far larger than the box it fills.
  • Count your add-ons. web.dev calls third-party scripts "a common cause of performance slowdowns caused by resources outside the site owner's control." Every chat bubble, tracker and review widget is one.

On a hosted builder, the platform runs the server; you control photos, embeds and add-ons. On WordPress the server is yours too: web.dev says "hosting should be the first thing you consider," and speed depends on "the number and quality of plugins."

What does mobile-first mean for my website?

Google judges your site by its phone version:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile-first indexing best practices)

The same page gives the fix for the usual mistake: "Make sure that your mobile site contains the same content as your desktop site." If the phone layout hides reviews or service details to look tidy, Google may not count them.

  • Viewport tag. It fits the page to the screen. web.dev: "A page without the viewport meta tag loads very zoomed out, making the text hard to read."
  • Tap targets. WCAG 2.2, the web accessibility standard, sets a Level AA minimum of "24 by 24 CSS pixels," with exceptions such as a link inside a sentence. Make call and book buttons bigger.
  • Tap-to-call. Write the number as a tel: link. MDN, the main web developer reference, says phones dial it when tapped.

How should the pages be structured?

Give each service its own page, reachable from the menu or a related page. What goes on that page: On-page SEO for service pages.

ItemWhat Google saysWhat to ask for
LinksIt can generally crawl a link only if it's an anchor element with an href attributeMenus and buttons that are real links, not scripts
Page addresses"we recommend using hyphens (-) instead of underscores (_)"/roof-repair/, not /services.php?id=3
HeadingsOut-of-order headings don't matter to Search, but semantic order is "fantastic for screen readers"Keep them in order
Titles"a good title is unique to the page, clear and concise"Service, city, business name
SitemapYou "might not need a sitemap" with about 500 pages or fewer, well linkedTurn on the platform's sitemap; submit it in Search Console
Structured dataIt doesn't guarantee a rich resultAdd business details: local business schema

Sources: Google Search Central's link, URL, SEO Starter Guide, sitemap and structured data pages.

Accessibility: build it in, not on later

Build to WCAG 2.2 Level AA. W3C says content that meets 2.2 also meets 2.1 and 2.0, the versions some laws name.

Build itemThe ruleWho it helps
Text contrastAt least 4.5:1, or 3:1 for large text (WCAG 1.4.3, AA)People with low vision read your prices and number
Alt textMeaningful images have a text alternative (WCAG 1.1.1, A)Screen-reader users hear what photos show
Form autofillName, phone and email fields state their purpose in code (WCAG 1.3.5, AA)Everyone: browsers can then "suggest and 'autofill' the right content" (W3C)
Keyboard useEverything works from a keyboard (WCAG 2.1.1, A)People who can't use a mouse can still book

PageSpeed Insights includes an accessibility score from Google's Lighthouse. Then tab through your booking form by keyboard, because:

"A “clean” report does not necessarily mean everything is accessible." (ADA.gov: Guidance on Web Accessibility and the ADA)

US: for businesses, the Justice Department "does not have a regulation setting out detailed standards" (ADA.gov), but the ADA still applies. Lawsuits and deadlines: ADA website compliance.

Canada: in Ontario, since January 1, 2021, a business or non-profit with 50 or more employees must make its public website meet WCAG 2.0 Level AA (minus live captions and pre-recorded audio descriptions) for content posted after January 1, 2012. The duty sits with whoever controls the site, "either directly or through a contractual relationship" (Government of Ontario). In Manitoba, since May 1, 2025, a business or non-profit with at least one employee must make new web content, and any content customers need to get its goods or services, meet WCAG 2.1 Level AA (Manitoba Accessibility Office).

Is HTTPS still needed?

Yes, and visitors now notice. On October 21, 2026, Chrome's security team wrote:

"we have now rolled out a change where Chrome explicitly asks users for permission before making an insecure HTTP connection." (Google Chrome Security blog)

The post says this is now on for all users by default. Certificates can be free: Let's Encrypt "provides free TLS certificates." Ask your host or builder to turn HTTPS on for every page.

Don't expect a ranking boost. Google lists HTTPS under page experience, then says: "Beyond Core Web Vitals, other page experience aspects don't directly help your website rank higher in search results."

After launch, security is mostly updates. web.dev: "Attackers actively seek out old software with vulnerabilities." On WordPress, keep themes and plugins updated and remove ones nobody maintains.

Before launch: the checks that protect your traffic

  1. No noindex tag on the live site. Test copies often carry this "don't list me" tag. Left on, Google "will drop that page entirely from Google Search results" (Google Search Central: noindex).
  2. robots.txt doesn't block the site. The file tells crawlers "which URLs the crawler can access on your site." A test copy's block-everything rule, left on, keeps Google from reading your pages.
  3. Every old address redirects. A 301 (permanent) redirect is, for Google, "a strong signal that the redirect target should be processed." More: traffic dropped after a redesign.
  4. Missing pages return a real 404. Google drops a URL that returns 404. A "not found" screen served as a normal page shows in Search Console as a "soft 404." Put your number and service links on it.
  5. Tracking works. Mark calls, forms and bookings as key events in Google Analytics 4: GA4 key events. Verify the site in Search Console.
  6. A real phone on mobile data. Tap the number, send a test form, book a test slot.

Old web development advice to skip

You may still readWhat's true now
Use Google's Mobile-Friendly TestRetired December 1, 2023, with the Mobile Usability report. Use PageSpeed Insights and a real phone
FID is a Core Web VitalINP (Interaction to Next Paint) replaced it on March 12, 2024
HTTPS gives a ranking edge"a very lightweight signal" in 2014; now aspects beyond Core Web Vitals "don't directly help"
Keep titles under 60 charactersGoogle sets no limit; it shortens titles to fit the screen. Put key words first
Block duplicates with robots.txt"Don't use the robots.txt file for canonicalization purposes." Use a canonical tag or redirect
Alt text counts toward Core Web VitalsNo. Those measure loading, interactivity and visual stability
Set up goals in Google AnalyticsGA4 calls them key events

Example

Illustrative cases, not measured results.

A roofer rebuilding on WordPress

The old site used addresses like /services.php?id=3. The developer moves 40 pages to plain addresses such as /roof-repair/, redirects each one, and removes the test copy's noindex tag before launch. Old links land on the right new page.

A Toronto physiotherapy clinic with 60 staff

Ontario's rule applies, so the site is built to WCAG 2.2 Level AA, which also covers Ontario's 2.0 standard. The booking form gets labels and autofill.

A cleaning company on Squarespace

It can't touch the server, so it fixes what it controls: a 5 MB photo at the top of the home page, two unanswered chat widgets, and a phone number that wasn't tappable.

FAQ

Should I use a website builder or hire a developer?

Either can meet the 12 items. A builder runs hosting for you; custom code gives more control. Compare: Wix, Squarespace or WordPress.

How do I test mobile-friendliness now that Google's test is gone?

Run PageSpeed Insights on mobile: it checks performance, accessibility, best practices and SEO. Then use the site on a real phone.

Do I need AI features, an app or voice search work?

Not before the basics: a fast, phone-friendly page that makes calling easy. For voice assistants: voice search for a local business.

Different for you?

Keep learning

NextMobile menu design: hamburger, tab bar or sticky header?Pick a mobile menu people open and Google can crawl: when visible links, a hamburger, a tab bar or a sticky header fits, tap sizes, and a quick test.

Do it yourself

Webflow SEO checklist: every setting to check, and where it isA Webflow SEO checklist for a small business site: where each on-page, technical and local setting lives in Webflow, and what Google actually requires.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Mobile site and mobile-first indexing best practices
  2. Google Search Central: Understanding page experience in Google Search results
  3. web.dev: Web Vitals
  4. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12 (2024)
  5. web.dev: Optimize Cumulative Layout Shift
  6. web.dev: Optimize Largest Contentful Paint
  7. web.dev: Load third-party JavaScript
  8. web.dev: Optimize Time to First Byte
  9. web.dev: Responsive web design basics
  10. MDN: The anchor element (tel: links)
  11. W3C: Understanding Success Criterion 2.5.8 Target Size (Minimum)
  12. W3C: Understanding Success Criterion 1.3.5 Identify Input Purpose
  13. W3C: Understanding Success Criterion 1.4.3 Contrast (Minimum)
  14. W3C: Understanding Success Criterion 1.1.1 Non-text Content
  15. W3C: Understanding Success Criterion 2.1.1 Keyboard
  16. W3C: WCAG 2 Overview
  17. ADA.gov: Guidance on Web Accessibility and the ADA
  18. Government of Ontario: How to make websites accessible
  19. Manitoba Accessibility Office: Checklist for Businesses and Non-Profit Organizations (Information and Communication)
  20. Google Search Central: Link best practices
  21. Google Search Central: URL structure best practices
  22. Google Search Central: SEO Starter Guide
  23. Google Search Central: Influencing your title links in search results
  24. Google Search Central: Learn about sitemaps
  25. Google Search Central: General structured data guidelines
  26. Google Chrome Security blog: Chrome now warns before insecure HTTP connections (October 21, 2026)
  27. Google Search Central Blog: HTTPS as a ranking signal (2014)
  28. Let's Encrypt
  29. web.dev: Top ways sites get hacked by spammers
  30. Google Search Central: Block Search indexing with noindex
  31. Google Search Central: Introduction to robots.txt
  32. Google Search Central: How to specify a canonical URL
  33. Google Crawling Infrastructure: How HTTP status codes affect Google's crawlers
  34. Google Search Central Blog: The mobile-friendly testing tool (retired December 1, 2023)
  35. PageSpeed Insights: About PageSpeed Insights
  36. Google Analytics developer docs: Set up events