A business owner can approve a new homepage and still launch a weak website.
The visible parts get most of the attention: layout, colors, photography and copy. The quieter parts are easier to miss. Pages load slowly on phones. Analytics never record a submitted form. Search engines have little structured information to work with. A lead reaches a shared inbox with no source attached.
Routeless reviewed 113 Fresno business websites in August 2026 to see how common those problems were. The sample covered 63 home-service companies, 48 healthcare businesses and two legal businesses. National chains were excluded.
The median mobile performance score was 60 out of 100. Median measured load time was 8.4 seconds. About one-third of the sites, 33.6%, published no structured data, and 40.7% had no detectable analytics. The audit of 113 Fresno business websites also found that 71.7% had no homepage contact form and 21.2% were running on DIY builders.
A local sample cannot stand in for every small-business website in the country. It can still show where a redesign often goes wrong: the project ends when the pages look finished.
Speed is part of the user experience
An eight-second load is not an abstract technical problem when the visitor is trying to call a dentist, check a restaurant menu or request a repair estimate from a phone.
The Fresno audit found that 97.3% of the sites had a Largest Contentful Paint above 2.5 seconds. The median homepage weighed 2.8 MB. Common causes are familiar to developers: oversized images, third-party scripts, old themes and marketing tools added one at a time.
The fix usually starts before launch. Image sizes, fonts, scripts and tracking tags should be tested on a mobile connection, not just on a developer’s laptop. A fast staging site can become a slow production site once chat, scheduling, advertising pixels and analytics are switched on.
Measurement has to survive the redesign
A redesign can improve traffic and still leave the owner unable to tell which pages produce business.
That makes the 40.7% figure on undetected analytics worth attention. Installing Google Analytics or another platform is only the first step. The useful question is whether the site records the actions the business cares about.
For a service company, that might be a submitted quote request, a phone tap or a booked appointment. An ecommerce site needs a different event model. A multi-location business may need the location, service requested and landing page attached to the lead.
These events should be tested with the same care as navigation and forms. Otherwise the new site launches with cleaner design and the same blind spots.
Structured data should describe what is already on the page
The Fresno sample found no structured data on 33.6% of the sites.
Schema markup will not rescue weak content or make a business more authoritative than it is. Its job is narrower. It gives machines a clearer description of information already visible on the page: the organization, location, services, articles, products or other supported entities.
The implementation should be boring. Mark up what the page says. Keep names, addresses and services consistent. Do not invent reviews, locations or claims to fill a schema field.
Business pages are now read by traditional search crawlers and AI-driven search systems. Both work better when the page leaves less room for guessing about what a company does and where it operates.
The form is where the website meets the business
One of the more surprising findings in the audit was that 71.7% of homepages had no contact form.
A phone number can be enough for some companies. But when a form exists, the design team should know what happens after someone clicks submit.
A roofing company may want to route requests by city. A dental office may separate appointment requests from insurance questions. A property business may need to preserve the listing a visitor was viewing. If every submission lands in the same inbox with none of that context, staff have to reconstruct it by hand.
The website does not need a complicated automation stack to improve this. A few deliberate fields and a reliable handoff to the CRM can remove repetitive work.
Platform choice should follow the requirements
The audit found that 21.2% of the sites used DIY website builders. That number is easy to turn into an argument for custom development, but the platform itself is not the useful dividing line.
A five-page site for a small company may work perfectly well on a simple builder. The requirements change when the website becomes part of operations: leads need routing, multiple systems exchange data, organic traffic has to be protected during a migration, or the company needs detailed measurement.
At that point, the build should follow the workflow instead of forcing the workflow into whatever the template can handle.
Before calling a redesigned site finished, test key pages on mobile and submit every important form. Confirm where the data lands. Check that conversion events fire once. Review canonical tags, robots directives and sitemap output. Validate the structured data that is present. Compare important URLs before and after launch.
Those checks are not as visible as a new hero section. If they happen only after launch, the redesign was scoped too narrowly.
Leave a Reply