Why agency websites lose valuations in five seconds.

What "slow" actually costs

The damage is not one big event. It is a slow leak in three places at once.

• People leave before the page appears. The longer a page takes to show something useful, the more visitors abandon it — and mobile visitors, on patchy connections, abandon fastest.
• Google notices. Page experience is a ranking input. It will not rescue thin content, but between two similar agency sites in the same town, the faster one has an advantage it keeps.
• Your paid traffic costs more. If you run Google Ads, a slow landing page hurts quality score, so you pay more for the same click and then convert fewer of them.

How speed is measured now

Google's Core Web Vitals are three numbers, and Google reports them from what real visitors experienced on your site, not from a lab test.

• LCP (Largest Contentful Paint) — how long until the main thing appears. On a property page that is almost always the hero photo. Aim for 2.5 seconds or better.
• INP (Interaction to Next Paint) — how quickly the page responds when someone taps. This replaced First Input Delay in March 2024 and it is much less forgiving. Aim for 200 milliseconds or better.
• CLS (Cumulative Layout Shift) — how much the page jumps about while loading. The classic offender is a property image with no dimensions set, shoving the text down as it arrives. Aim for 0.1 or below.

You can see your own scores free in Google Search Console, under Core Web Vitals, and test individual pages with PageSpeed Insights. Check the field data section rather than the lab score — that is what counts.

Why agency sites in particular are slow

Estate agency websites have a harder job than most small business sites, and the same handful of causes come up again and again.

• Photographs straight from the camera. A property gallery of twenty images at three or four megabytes each is the single biggest cause. They need resizing and converting before they are served.
• Third-party widgets. Portal feeds, review widgets, chat bubbles, mortgage calculators and tracking scripts each add a connection and a chunk of JavaScript. Four or five of them will wreck INP on their own.
• Page builders. Many agency sites are built on a stack of plugins loading their own CSS and JavaScript on every page, whether that page uses them or not.
• Search results loading everything at once. A results page that loads sixty full-size photos before showing anything will fail LCP no matter how good the hosting is.

The fixes, in the order worth doing them

Do these in sequence. The first two usually account for most of the gain.

1. Fix the images. Resize to the largest size actually displayed, serve WebP or AVIF, set explicit width and height on every image so nothing shifts, and lazy-load everything below the fold — but never the hero image, which should load eagerly and be preloaded.
2. Audit third-party scripts. List every external script and justify each one. Remove what nobody uses. Defer anything that is not needed for the first paint.
3. Sort out caching and hosting. Static pages should be served from cache, ideally from a CDN edge near the visitor. Shared hosting with no caching layer will cap how fast the site can ever be.
4. Self-host and preload fonts. Two weights is plenty. Use font-display: swap so text is readable while fonts load.
5. Paginate or lazy-load search results. Show a first batch, then load more on demand.

What good looks like

A well-built agency site should show its hero image in well under two seconds on a mid-range phone on 4G, respond to taps immediately, and not move around while it loads. That is achievable on a modest budget. It is mostly a matter of discipline about images and scripts rather than expensive infrastructure.

If you want to know where yours stands, put your address into PageSpeed Insights and look at the field data — or ask us for a free site review and we will go through it with you in plain English.