Most people judge a website by its appearance. That matters. It is not the whole story.
If the page takes too long to start, people leave. They tap back and call someone else. Google notices the same delay and treats the site as weaker than a faster competitor. For a local business — a law firm, a clinic, a contractor — that usually means fewer calls and fewer contact-form submissions, not a missing logo.
Intrepid Network has built and maintained sites in San Diego since 1996. When a client asks us to “speed it up” or clean up an old web presence, we are rarely flipping one switch. We make the site respond faster, tell search engines the right phone number, and send leftover domain names to the current site without breaking email. Here is that work in plain language.
Slow is expensive
Your browser has to wait for the server to start talking before it can draw the page. That wait is called time to first byte. Google wants it well under a second. A WordPress site with no page cache often spends two seconds or more just thinking. Every new visitor pays that tax.
Speed also shows up as:
- Phones. Most local searches happen on a mobile screen. Extra shopping-cart code on a site that does not sell products makes that phone work harder.
- Zoom and access. Some themes lock pinch-to-zoom. That fails accessibility checks and frustrates people who need larger text.
- Trust. If Google still sees an old phone number in the site’s hidden “business card” (structured data), search results can keep advertising the wrong number.
Make the server stop rebuilding every page
Without a cache, WordPress rebuilds the homepage from scratch on every visit. We turn on page caching so the next visitor gets a saved copy. Logged-in editors still see fresh drafts. We minify extra spaces in code on the server. We do not smash every file into one giant file when the connection already handles many small files well.
Sometimes a cache plugin is installed that talks to a service that is not running. That does not make the site faster. It just adds errors. We turn that off.
Cloudflare sits in front of the site and stores images, fonts, and style files close to the visitor. The old “auto minify” buttons on Cloudflare’s free plan are gone. Minifying still happens on the website itself. What Cloudflare can still do — deliver files from the edge, hint the browser to start early, serve fonts locally — we turn on. One Cloudflare tool (Rocket Loader) has a habit of breaking forms and menus, so we leave it off when the theme is picky.
After this kind of pass, test scores usually jump: desktop into the 90s, mobile out of the 50s. Repeat visits feel snappy. The very first visit after a cache clear can still be slower. That is normal.
Do not load a store if you do not sell products
Many WordPress themes are built for shops. They include a cart icon, product search, and extra style files even when WooCommerce is not installed. A law firm or professional office does not need that weight.
We turn off shop-only settings that are safe to remove and leave the real site alone: menus, contact forms, spam protection. If the business does not sell SKUs, the site should not pretend it does.
The phone number in Google has to match the phone number on the page
Search engines read a hidden block of data that describes the business: name, address, phone, hours. Plugins often fill that in automatically as a generic “Organization” and keep an old number.
You cannot paste a better block on top and hope Google ignores the old one. Two stories confuse the crawler. We turn off the plugin’s automatic business card and put in the correct one — current phone, address, and what the firm actually does. Then we check Google’s Rich Results Test.
We also look at what humans see. It is common for the desktop header to show the new number while the mobile header still dials the old one. That lives in the theme’s mobile header, not in the page builder. Both have to match.
Two small settings that still fail checklists
Pinch to zoom. If the theme says the page is “not scalable,” phones cannot zoom. We switch that to scalable.
The robots file. Search engines read a short text file at the site root to find the sitemap. If that file already exists on the server, a plugin setting will not replace it. We add the sitemap line to the real file and confirm the sitemap address actually works.
Old domain names should send people to the new site
Firms collect domain names over the years. The current brand is live. An older site may still be running. An even older name may have no website at all — the browser just fails — while email on that name still matters.
We set permanent redirects (301) so:
oldsite.com/about-us/becomesnewsite.com/about-us/- Bookmarks and leftover Google listings land on the right page
- Email on the old names keeps working
A control-panel “redirect” button is not always enough. WordPress can intercept the request first. In that case the redirect belongs at the top of the site’s rules file. For a name with no hosting plan, we use Cloudflare as a traffic director: web requests go to the new site; mail records stay pointed at the email host.
We do not touch mail settings to make a web redirect. After nameservers change, someone should send a test message.
Renewal is part of the same job. “Auto-renew” with no card on file is not auto-renew.
What “done” looks like
You should be able to:
- Open the old domain and land on the current site, including interior pages
- Call the number on the phone header and get the current line
- See Google’s test accept one clean business listing
- Feel the homepage start faster on a second load
What we cannot promise in one afternoon: Google updating every search snippet the same day, or a perfect score on a phone over a slow radio. Field data lags lab tests. That is expected.
If the site looks finished and still feels late, the work is under the surface — saved pages, extra theme weight, the number Google believes, and old names that never got a forwarding address. That is the layer we fix so the part you see can actually earn the call.