SEO courseModule 4 of 10: Speed, mobile and safetyLesson 4.1
Page speed: hosting, images and Core Web Vitals
How fast your pages load, how quickly they respond when someone taps, and whether things jump around while they load. Behind all three: how quickly your server answers, and whether your site stays online.
By Morgan King, founder of Reyse. Facts checked October 2026. Jump to Your turn
Why it matters
Property pages are heavy. Slow ones send people back to the portal in seconds.
Why Google cares
Evidence: Official guidance
Used by Google’s ranking systems since 2021
Do this first
Shrink your listing photos. It’s usually the biggest single win.
What it is
A magazine where every page takes ten seconds to appear and the pictures keep jumping about. You’d put it down, however good the articles were.
Think of it like
Door speed
A shop with a door that takes ten seconds to creak open loses customers before they even step inside. A slow-loading page does exactly the same.
Think of it like
Staff response
A shop where staff take ages to notice you’ve asked for help feels broken, even if they get there eventually. That’s a page that’s slow to respond to a tap.
Think of it like
Stability
Shelves that shift while you’re browsing make you grab the wrong thing. A page whose buttons jump about while it loads causes the same mis-taps.
Same search, two agencies. Watch what happens by the time the slow one finishes loading.
Page’s loaded. Customer browses listings.
Still loading. Customer’s already back on Google, clicking the next result.
Why it matters to the people searching
Someone looking for a home on their commute, on patchy signal, gives your site a few seconds before going back to the portal. Property pages are heavy (big photos, maps, galleries, chat widgets), so they’re slow far more often than agents realise.
buyers
Browse photo-heavy listings on phones. Slow galleries send them back to the portal.
tenants
Compare lots of rentals fast. A slow site is simply skipped.
sellers
Judge your marketing by how polished your own site feels.
landlords
Same, often reading long pages on desktop.
To Google and Bing
Evidence: Official guidanceGoogle says Core Web Vitals are used by its ranking systems, and has since 2021. There are three, measured from real Chrome users over the last 28 days: loading (Largest Contentful Paint, good is 2.5 seconds or less), responsiveness (Interaction to Next Paint, good is 200 milliseconds or less) and stability (Cumulative Layout Shift, good is 0.1 or less). It’s one signal among many, and relevance matters more, but a slow site also loses the people who do click. A slow server slows everything, and can limit how much of your site Google .
The evidence: Google says Core Web Vitals are used by its ranking systems, and that relevance matters more.
- Loading (LCP): good is 2.5 seconds or less
- 2.5sLoading (LCP): good is 2.5 seconds or less
- Responding (INP): good is 200 milliseconds or less
- 200msResponding (INP): good is 200 milliseconds or less
- Staying still (CLS): good is 0.1 or less
- 0.1Staying still (CLS): good is 0.1 or less
An agent example
A lettings branch’s listing pages load 25 full-size photos straight from the CRM, around 6MB each, plus a chat widget, a heatmap tool and two analytics tags. Resizing the photos before they reach the site and delaying the chat widget takes the main photo from six seconds to under two on a mid-range phone.
Your turn: check yours, then fix it
- 1Go to pagespeed.web.dev, paste a page’s address and press Analyze.
- 2Read the Mobile tab first. The top block is real-user data (if your site has enough visitors); below it is a lab test.
- 3Check the three Core Web Vitals against the good thresholds, then read Diagnostics: it lists exactly what’s slowing you down.
- 4Test five page types: homepage, search results, a listing, the valuation page and a guide.
- Open Experience, then Core Web Vitals, and click into any Poor group for example pages.
- 1Enter your address at gtmetrix.com and open the Waterfall tab once it finishes.
- 2Look for the longest bars. It’s almost always one image or script worth fixing first.
- Use a mid-range Android phone on 4G, not your office Wi-Fi, and time how long a listing takes to show its main photo and price.
Here are the PageSpeed Insights diagnostics for a page on my estate agency website, which has large photo galleries. Rank these issues by likely impact and give me step-by-step fixes for [WordPress / my platform]. Explain anything technical in plain English.
- 1Resize photos to the size they’re actually shown at, and compress them. A 6MB photo shown 800 pixels wide is wasted weight.
- 2Use modern formats (WebP or AVIF) where your platform allows.
- 3Lazy-load images further down the page, but never the main photo at the top.
- 4Better still, resize in the CRM or feed so full-size photos never reach the site.
- 1Chat widgets, heatmaps, social feeds and extra analytics tags all slow pages. Remove what you don’t use.
- 2Delay the rest until after the page loads. Test the effect of each by removing one at a time.
- Give images and embeds fixed dimensions, and reserve space for banners, so nothing shifts as they load.
- 1WordPress: a caching plugin such as WP Rocket or LiteSpeed Cache.
- 2Any site: Cloudflare’s free plan adds a speed layer whoever your host is.
- 1Ask your host about caching and capacity. Cheap shared hosting struggles with big property sites.
- 2Compare hosts with UK data centres, such as SiteGround, Kinsta, WP Engine, Krystal or 34SP.
- 3If you’re on a property platform, ask them for their server response times and a written plan to improve them.
- Paste your PageSpeed results into an AI tool and ask what to fix first and how (prompt above).
Then: Re-test after each change and log the numbers. The real-user data in PageSpeed and Search Console catches up over about 28 days.
Rather we did this for you? It’s part of Found First.
Keep it up
New photos, plugins and widgets quietly slow sites down without anyone noticing. Check monthly.
Go deeperServer response time (TTFB)
Time to First Byte is how long your server takes to start answering, before anything else can happen. Under about 0.8 seconds is a reasonable target.
Test it at webpagetest.org with a UK location, at different times of day and during a feed import. Search Console’s Crawl stats (under Settings) shows your average response time to Google over 90 days.
Big property sites slow down when every search runs a heavy database query, or when feeds import at peak times. Ask your developer to review slow queries and move imports to quiet hours.
Go deeperStaying online
A site that’s down loses the visitor in the moment, and if it happens often, Google visits less and can drop pages.
Set up free monitoring with UptimeRobot so you hear about outages that happen while nobody’s looking. Rare, brief blips aren’t worth acting on; frequent downtime means your host isn’t reliable enough.
Sources
- 1.Understanding Core Web Vitals and Google search results, Google Search Central
- 2.Understanding page experience, Google Search Central
Facts checked October 2026, and re-checked every quarter. Spotted something out of date? Tell us.
Worked through it? Mark it done and we’ll keep track on this device.