Site Speed and Page Experience: Why Slow Adviser Websites Lose Enquiries

Google groups its main page experience signals under the name Core Web Vitals. There are three, and each measures a different part of what a visitor feels while a page loads.

Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on the screen, usually a hero image, a headline block or a video poster, to appear. Google's threshold for a good experience is under 2.5 seconds. Between 2.5 and 4 seconds is classed as needing improvement, and anything over 4 seconds is poor. On adviser websites the largest element is very often a stock photograph of a smiling couple or a city skyline, uploaded at full resolution straight from a photo library.

Interaction to Next Paint (INP) replaced the older First Input Delay metric in 2024. It measures how quickly the page responds when someone taps, clicks or types, across the whole visit rather than just the first interaction. A good score is under 200 milliseconds. Poor INP feels like a button that does nothing when tapped, a menu that opens a beat late, or a form field that lags behind the keyboard. It is usually caused by heavy JavaScript competing for the browser's attention, which on adviser sites tends to mean chat widgets, tracking tags and page builder scripts.

Cumulative Layout Shift (CLS) measures visual stability, meaning how much content jumps around as the page loads. A good score is under 0.1. Everyone has experienced poor CLS: you go to tap "Book a call" and a cookie banner or late-loading image pushes the button down, so you tap something else instead. On a mobile screen this is not just irritating, it actively causes mis-taps and abandonment.

Google assesses each metric at the 75th percentile of real visits. That detail matters. It means a page only passes if three quarters of actual visitors get a good experience, so a fast result on your own device tells you very little about the visitor on an older Android phone in a rural area.

It is also worth being clear about what Core Web Vitals are not. They are not the single biggest ranking factor in organic search; the relevance and quality of your content still matter far more. Google has described page experience as something that can separate pages of similar relevance rather than something that overrides relevance. The stronger commercial argument for speed is about conversion and paid media efficiency, which the next sections cover. Treat good vitals as a baseline of professionalism, the digital equivalent of a tidy reception area, rather than a magic SEO lever.

Traffic from Meta, meaning Facebook and Instagram, behaves very differently from someone who searched for an adviser on a desktop at lunchtime. Paid social visitors are overwhelmingly on mobile, they are often on cellular connections, and they arrive inside an in-app browser rather than Chrome or Safari. The in-app browser has to start up, fetch your page and render it while the person is still half-engaged with their feed. Their patience is measured in a couple of seconds, not ten.

This creates a pattern that many adviser firms see in their analytics without understanding it. Meta reports a healthy number of link clicks, but GA4 records far fewer sessions, and the gap is widest on the campaigns with the cheapest clicks. Part of that gap is tracking and consent, but a meaningful part is people abandoning before the page has loaded enough for the analytics tag to fire. You paid for the click, in effect, and the website threw it away.

Paid social prospects are also typically earlier in their thinking than search prospects. Someone searching for an independent financial adviser near them has a problem they want solved. Someone who saw an ad about retirement income while scrolling is curious but not committed. The lower the intent, the less friction they will tolerate, and a slow or jumpy page is pure friction. This is one reason many firms find Meta instant forms convert better than sending people to a website; we compare the trade-offs in Meta instant forms vs landing pages. But if you choose landing pages for lead quality reasons, which is often the right call, the page has to be genuinely fast on a mid-range phone.

A few practical implications follow. First, test and measure on mobile first. Your desktop scores are almost irrelevant for social campaigns. Second, landing pages built for paid social should be lighter than your main website: no autoplay video, no slider, no chat widget popping up after three seconds, and a single focused form. Third, check how the page looks inside the Facebook and Instagram in-app browsers specifically, because fonts, cookie banners and embedded calendars sometimes behave differently there than in a normal browser.

Finally, watch the ratio of landing page sessions to ad clicks by campaign as a rough health check. If one campaign loses far more visitors between click and landing than the others, and the creative and audience are similar, the landing page is the most likely culprit. Fixing speed on that page can improve results without changing the targeting, the budget or the ad at all, which makes it one of the cheapest optimisations available to an adviser firm running social campaigns.

On Google Ads the cost of slow pages is more direct. Every keyword receives a Quality Score from one to ten, built from three components: expected click-through rate, ad relevance and landing page experience. Landing page experience reflects how useful, relevant and easy to use Google judges your page to be once someone clicks, and load speed and mobile usability are part of that judgement.

Quality Score feeds into Ad Rank, which determines both where your ad appears and how much you pay. A higher Quality Score means you can hold the same position for a lower cost per click; a lower one means you pay more for the same position or slip down the page. In adviser marketing, where high-intent terms around pension advice or inheritance tax planning commonly cost £8 to £25 per click, even a modest change in what you pay per click compounds quickly across a month of spend.

Google does not publish an exact formula, and speed is only one input into landing page experience. Relevance of the content to the search, clarity about who you are and what you offer, and transparency about the business all matter too. But a landing page experience rating of "below average" in keyword diagnostics is a clear signal that something on the page is costing you money, and speed is frequently part of the story on adviser sites built on heavy themes.

There is also a second, simpler effect. Even if your Quality Score held steady, a slow page converts a smaller share of the clicks you have already paid for. If your landing page converts at 4% when it loads quickly and 3% when it is slow, your cost per lead rises by a third without any change in your bids. Across a typical UK Google Ads cost per lead range of £60 to £130 for advisers, that difference can be the margin between a channel that pays back comfortably and one the partners start to question.

To see where you stand, open the keywords view in Google Ads, add the Quality Score, Landing page experience and Expected CTR columns, and sort by spend. Focus on your highest-spend keywords first. If they show below average landing page experience, check which final URL they point to, run that URL through PageSpeed Insights on mobile, and look honestly at whether the page answers the search. You can model the effect of a lower cost per click or a higher conversion rate on your lead volumes with our lead budget calculator, which helps build the business case for fixing a page the agency has been happy to keep sending traffic to.

Across adviser and wealth firm websites, the same causes of slow pages appear again and again. Few of them are exotic. Most come from well-intentioned additions that were never assessed for their performance cost.

• Heavy multipurpose themes and page builders. Many adviser sites run on WordPress themes designed to do everything, which means loading code for features you never use on every page. Page builders add layers of nested markup and scripts. The site looks fine but ships several times more code than it needs.
• Hero sliders and carousels. Rotating banners with three or four large images are still common on adviser homepages. They delay the largest contentful paint, often cause layout shift, and very few visitors ever see slide three. A single strong static image or headline almost always performs better.
• Chat widgets. Live chat and AI assistants can be useful, but many load a large bundle of JavaScript immediately and then pop open after a few seconds, which hurts INP and can cause layout shift. They should load after the main content and only on pages where they earn their place.
• Tag bloat. Over time, sites accumulate tracking tags: Google Analytics, Google Ads, the Meta pixel, LinkedIn Insight, heatmap tools, call tracking, an old remarketing tag from a previous agency and several things nobody can identify. Each adds network requests and processing. Tags left behind by former suppliers are particularly common.
• Unoptimised images. Team photos uploaded at 5,000 pixels wide, PNG files where a compressed WebP would do, and no responsive sizing, so a phone downloads the desktop version. This is often the single largest and easiest win.
• Third-party calculators and embeds. Pension, mortgage and retirement calculators embedded from external providers, along with embedded calendars, review widgets and video players, all load code from someone else's servers that you do not control.
• Cookie banners. Consent management platforms are necessary, but some load slowly, block rendering, or appear late and shove content around the screen. Getting consent right also matters for measurement, which we cover in our guide to GA4 consent mode for adviser websites.
• Web fonts. Multiple font families and weights loaded from external services can delay text appearing, and fallback fonts swapping in late cause small layout shifts.

The common thread is that each item was added for a reason by someone who did not have to account for its cost in lost enquiries. A chat widget is installed because a supplier demonstrated it, a calculator because a partner liked it at a conference, a tag because an agency needed it for one campaign two years ago. Individually each seems harmless. Together they turn a reasonably built site into one that struggles on mobile. That is a governance problem as much as a technical one, which is why the later section on managing agencies and suppliers matters as much as any individual fix.

Before fixing anything, establish a reliable baseline. The most common mistake is running a single PageSpeed Insights test, seeing a score, and either panicking or relaxing. The headline score is useful as a prompt, but it is not the measure Google uses to judge your page experience.

There are two kinds of data, and understanding the difference saves a great deal of confusion.

Field data comes from real visitors using Chrome, collected in the Chrome User Experience Report. It reflects actual devices, networks and behaviour over the previous 28 days, and it is what Google uses for its Core Web Vitals assessment. Field data appears at the top of a PageSpeed Insights report, provided your site has enough traffic. Smaller adviser sites sometimes lack enough visits for page-level data, in which case PageSpeed Insights may show origin-level data for the whole domain, or nothing at all.

Lab data comes from a simulated test run at a single moment on an emulated device and connection. It is the part of PageSpeed Insights that produces the performance score out of 100 and the list of diagnostics. Lab data is excellent for diagnosing problems and checking whether a fix worked, because you can run it immediately. But it can differ significantly from field data in either direction, and scores fluctuate between runs.

Use the tools together:

• PageSpeed Insights for individual URLs. Always check the mobile tab first. Look at the field data assessment, then use the lab diagnostics to find causes, such as the specific image identified as the LCP element or the scripts taking the most main-thread time.
• Google Search Console Core Web Vitals report for the site as a whole. It groups URLs with similar issues, separates mobile from desktop, and shows trends over time, which is what you need to track whether improvements stick.
• Chrome DevTools, including its Lighthouse and Performance panels, for whoever does the hands-on technical work.
• GA4 engagement data by landing page and device, to connect speed issues to commercial outcomes such as form starts and enquiry submissions.

Prioritise measurement on pages that carry commercial weight: paid landing pages, the homepage, the main service pages and the contact or booking page. A slow blog post from 2019 matters far less than a slow page receiving most of your Google Ads budget. Record the baseline for each in a simple spreadsheet with the date, LCP, INP, CLS and conversion rate, so that later improvements can be shown in business terms rather than as abstract scores. That record also protects you when a supplier claims a change made no difference, or when a later redesign quietly undoes the work.

Not every fix is worth the same effort. The order below reflects what typically delivers the largest improvement for adviser sites with the least risk and cost.

1. Compress and resize images. Convert large photographs to WebP or AVIF, serve appropriately sized versions to mobile using responsive image markup, and make sure the hero image is not lazy-loaded. It should load immediately, while images further down the page load lazily. For many sites this alone moves LCP from poor to good.

2. Remove the slider. Replace the homepage carousel with a single static hero containing a clear headline, a short supporting line and one call to action. This usually improves both speed and conversion, because one focused message outperforms several rotating ones.

3. Audit and prune tags. List every script loading on the site, identify its owner and purpose, and remove anything without a current, named use. Move remaining marketing tags into Google Tag Manager so they can be governed in one place. Consider whether server-side tagging or the Meta Conversions API can replace some browser-side load while improving measurement at the same time.

4. Defer non-essential third parties. Chat widgets, review carousels, video embeds and calculators should load after the main content, or only when a visitor interacts. A video can show a lightweight thumbnail that loads the player on tap. A calculator can sit on its own page rather than the homepage.

5. Fix layout shift. Set width and height attributes on images and embeds so the browser reserves space, make sure the cookie banner overlays content rather than pushing it, and avoid injecting notices above existing content after load.

6. Reduce font load. Limit the site to one or two font families and a small number of weights, host them locally where licensing allows, and use font-display settings that show text immediately.

7. Improve hosting and caching. Cheap shared hosting is a false economy for a firm spending thousands per month on ads. Good managed hosting, a content delivery network and proper page caching improve server response time, which underpins every other metric.

8. Consider a rebuild if the theme is the problem. If a site built on a heavy page builder still performs poorly after the steps above, it may be cheaper over two or three years to rebuild on a lean foundation than to keep patching. This is the point at which a specialist website review pays for itself.

Work through the list on your highest-value pages first, measure after each change, and stop when the commercially important pages pass on mobile field data. Perfection on a 100-point lab score is not the goal. A page that reliably shows its main content in under 2.5 seconds on a mid-range phone, responds instantly to taps and does not jump around will do its job. For the broader conversion picture beyond speed, including headlines, trust signals and form design, see our guide to landing pages that convert.

Most adviser websites do not become slow because of one bad decision. They become slow gradually, one tag, plugin, widget and image at a time, often added by different people who each assumed someone else was watching performance. Fixing speed once is relatively easy. Keeping it fixed requires a small amount of ongoing governance.

Start by naming an owner. In a smaller firm this might be the practice manager or the partner responsible for marketing; in a larger one, a marketing manager. Their job is not to do technical work but to approve changes and check the numbers each month. Without an owner, every supplier has an incentive to add their own script and none has an incentive to remove anyone else's.

Next, write a short performance standard into supplier agreements. It does not need to be elaborate. Something along these lines is enough:

• Commercially important pages must pass Core Web Vitals on mobile in Search Console field data.
• No new script, widget or plugin is added without written approval and a stated purpose.
• Any agency adding tracking documents what it added and removes it when the engagement ends.
• Images are compressed and sized before upload.
• Landing pages for paid campaigns are tested on mobile and inside the Meta in-app browser before launch.

Ask your paid media agency to report landing page experience status and mobile speed for its main landing pages alongside cost per lead. An agency that drives traffic to a slow page and reports only on clicks is not looking at the whole funnel. Equally, your web developer should understand that a new feature which slows the paid landing pages has a real cost in lost enquiries, however impressive it looks in a demo.

Build a quarterly review into the calendar. Open the Search Console Core Web Vitals report, check for new poor or needs improvement URLs, run the top five commercial pages through PageSpeed Insights on mobile, and review the list of tags in Tag Manager. This takes under an hour and catches most regressions before they become expensive.

Finally, be wary of plugins sold on the promise of more conversions, such as exit-intent pop-ups, social proof notifications and countdown timers. Some have a place, but many add weight, create layout shift and, for a regulated adviser firm, can sit uneasily with the Consumer Duty expectation that communications support good customer outcomes rather than applying pressure. Our wider guide on website conversion optimisation for advisers covers which conversion tactics are worth the trade-off.

Speed work is best approached as a short, focused project followed by light ongoing maintenance. Here is a practical sequence for the next month.

Week one: baseline. List your ten most commercially important URLs, including every paid landing page. Run each through PageSpeed Insights on mobile and record field and lab LCP, INP and CLS. Open the Search Console Core Web Vitals report and note how many mobile URLs are poor, need improvement or are good. Pull GA4 conversion rates for the same pages by device. Check Quality Score and landing page experience for your highest-spend Google Ads keywords.

Week two: quick wins. Compress and resize images on the priority pages, make sure the hero image loads first, remove or replace the homepage slider, and set explicit dimensions on images and embeds. Review the cookie banner so it overlays rather than displaces content. These changes are low-risk and can usually be done without a developer on a well-built site, or in a day or two by one.

Week three: scripts and third parties. Audit every tag and script, remove those without a current owner, move the rest into Tag Manager, and defer chat widgets, video players, calculators and review widgets so they do not compete with the main content. Retest the priority pages after each change to confirm improvement, and check that tracking still records conversions correctly.

Week four: governance and review. Agree a written performance standard with your web and paid media suppliers, name an internal owner, and schedule a quarterly review. Compare the new lab results with your baseline, and set a date four to six weeks out to check field data, which updates slowly because it covers a rolling 28-day window.

After that, judge the project by commercial outcomes rather than scores. Over the following two months, look for:

• A higher ratio of landing page sessions to ad clicks, especially from paid social.
• Improved landing page experience ratings and steadier or lower cost per click in Google Ads.
• A higher form start and submission rate on mobile.
• A lower cost per enquiry at the same budget.

If the priority pages still struggle after the quick wins and script clean-up, the underlying platform is probably the constraint, and it is worth getting a proper assessment of whether to rebuild. If you would like an outside view of how your website and landing pages perform as part of your wider lead generation, our team can review the full journey from ad click to booked meeting and show where enquiries are being lost.