Local website SEO and speed: the technical basics worth fixing

Start with a real mobile visit

Open your important pages on a phone using a normal connection. Watch how quickly the main content appears, whether the layout jumps, and whether the menu and contact controls respond. Test the enquiry form rather than assuming that a visually correct page works.

Use a diagnostic tool such as PageSpeed Insights to investigate what you observe. A lab result is a controlled test, while field data reflects real users when enough data is available. Do not treat one score from one run as a complete assessment of the site.

Understand the three Core Web Vitals

Largest Contentful Paint measures when the main visible content is rendered. Interaction to Next Paint measures responsiveness to interactions. Cumulative Layout Shift measures unexpected visual movement. Google's published good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds, and CLS at or below 0.1, evaluated at the 75th percentile of visits.

These metrics help identify a poor experience; they do not replace content relevance or guarantee a ranking increase. A business can improve a performance score while still having unclear service information or a broken form. Prioritize changes that make real customer tasks easier.

Optimize images without losing their usefulness

Large original photos should be resized for their actual display size and encoded efficiently. Use modern formats where appropriate, reserve space with dimensions or an aspect ratio, and provide descriptive alternative text when the image communicates information.

Load images below the first screen lazily, but do not indiscriminately delay the main hero image. A visitor should not download a huge desktop image for a tiny mobile card. Responsive image choices and sensible compression can reduce transfer size without turning project photos into blurry evidence.

• Match image dimensions to the layout.
• Reserve image space to reduce layout shift.
• Use meaningful alt text, not lists of SEO keywords.
• Limit unnecessary sliders, widgets, and autoplay media.

Make your indexation policy intentional

Check that pages meant for search are accessible, have appropriate canonical URLs, and are not accidentally marked noindex. Include useful indexable pages in an XML sitemap. Search Console can help identify discovered pages, indexing issues, and the version Google has selected.

Keep checkout, account, internal search, and other non-search pages out of the sitemap when appropriate. A robots.txt block is not the same as a noindex directive: a blocked page may prevent the crawler from seeing noindex. Do not index near-duplicate city templates simply because they can be generated.

Use clear titles, links, and structured information

Give each important page a descriptive title and main heading. Link service pages from navigation or other relevant pages rather than leaving them isolated. Write a useful meta description, while recognizing that Google may choose a different search snippet.

Structured data should describe the real business and visible page content. It is not a place to invent reviews, locations, or ratings. Valid markup can make information easier to interpret, but it does not guarantee a rich result or improved ranking.

Prioritize reliability before minor score improvements

Fix broken pages, inaccessible controls, failed submissions, and severely slow content before chasing marginal score changes. Document each improvement and retest the task it affects. A website migration should also preserve important URLs or use appropriate redirects.

After changes, compare real enquiry activity and relevant search performance over a sensible period. Website speed is one part of a larger system that includes the offer, content, reputation, and response process. A technically tidy website should help customers, not merely satisfy a checklist.