Web development tips for a fast site that converts
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 callWeb 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 in | Why | How to check |
|---|---|---|---|
| 1 | HTTPS on every page | Chrome now asks permission before opening a public site without it | Type http:// and your domain: it should switch to https:// |
| 2 | Same content on phone and desktop | Google ranks the phone version | Prices, reviews and service details all show on a phone |
| 3 | Layout that fits the screen | Without a viewport tag, phones show a zoomed-out page | Read every page on a phone without pinching |
| 4 | Buttons at least 24 by 24 pixels | The accessibility standard's minimum tap target | Tap each button with a thumb |
| 5 | Phone number as a tap-to-call link | One tap starts the call | Tap it on a phone |
| 6 | Compressed images with set sizes; top image not lazy-loaded | Big photos slow the first screen; missing sizes make the page jump | PageSpeed Insights on mobile |
| 7 | Few third-party scripts | Chat widgets, trackers and embeds slow pages | List every add-on; remove what nobody uses |
| 8 | One page per service, readable addresses | Each page can match one search | /drain-cleaning/, words split by hyphens |
| 9 | Menus made of real links | Google follows standard links | Right-click a menu item: "Open link in new tab" appears |
| 10 | A unique title per page | Searchers see the title first | Read each browser tab |
| 11 | Forms with labels and autofill | Faster on a phone; usable with a screen reader | Fill every form on a phone, then by keyboard only |
| 12 | Tracking live on launch day | Leads you didn't record can't be counted | Calls, 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.
| Item | What Google says | What to ask for |
|---|---|---|
| Links | It can generally crawl a link only if it's an anchor element with an href attribute | Menus and buttons that are real links, not scripts |
| Page addresses | "we recommend using hyphens (-) instead of underscores (_)" | /roof-repair/, not /services.php?id=3 |
| Headings | Out-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 |
| Sitemap | You "might not need a sitemap" with about 500 pages or fewer, well linked | Turn on the platform's sitemap; submit it in Search Console |
| Structured data | It doesn't guarantee a rich result | Add 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 item | The rule | Who it helps |
|---|---|---|
| Text contrast | At 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 text | Meaningful images have a text alternative (WCAG 1.1.1, A) | Screen-reader users hear what photos show |
| Form autofill | Name, 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 use | Everything 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
- 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).
- 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.
- 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.
- 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.
- Tracking works. Mark calls, forms and bookings as key events in Google Analytics 4: GA4 key events. Verify the site in Search Console.
- 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 read | What's true now |
|---|---|
| Use Google's Mobile-Friendly Test | Retired December 1, 2023, with the Mobile Usability report. Use PageSpeed Insights and a real phone |
| FID is a Core Web Vital | INP (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 characters | Google 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 Vitals | No. Those measure loading, interactivity and visual stability |
| Set up goals in Google Analytics | GA4 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?
- Speed numbers, PageSpeed vs Search Console: Core Web Vitals and ranking.
- Accessibility rules and lawsuits: ADA website compliance.
- Rebuilding a site that already ranks: traffic dropped after a redesign.
- Pricing the build and upkeep: website cost for a small business.
- Fast site, still no calls: website not getting leads.
- Want it built and checked for you: Website Agent.