Website review, no card needed

foxtons.co.uk logo

foxtons.co.uk website review

Visit site (opens in a new tab)Reviewed 30 October 202629 issues · 86 checks

This review found 29 issues worth fixing on foxtons.co.uk, 4 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
242 ms198 msMay 9Oct 24231 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026203 ms
May 16, 2026203 ms
May 23, 2026211 ms
May 30, 2026222 ms
Jun 6, 2026233 ms
Jun 13, 2026237 ms
Jun 20, 2026230 ms
Jun 27, 2026225 ms
Jul 4, 2026219 ms
Jul 11, 2026217 ms
Jul 18, 2026220 ms
Jul 25, 2026221 ms
Aug 1, 2026222 ms
Aug 8, 2026228 ms
Aug 15, 2026228 ms
Aug 22, 2026229 ms
Aug 29, 2026232 ms
Sep 5, 2026233 ms
Sep 12, 2026237 ms
Sep 19, 2026237 ms
Sep 26, 2026237 ms
Oct 3, 2026236 ms
Oct 10, 2026233 ms
Oct 17, 2026233 ms
Oct 24, 2026231 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of foxtons.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. foxtons.co.uk at 0.4 s0.4 s
  2. foxtons.co.uk at 0.8 s0.8 s
  3. foxtons.co.uk at 1.1 s1.1 s
  4. foxtons.co.uk at 1.5 s1.5 s
  5. foxtons.co.uk at 1.9 s1.9 s
  6. foxtons.co.uk at 2.3 s2.3 s
  7. foxtons.co.uk at 2.6 s2.6 s
  8. foxtons.co.uk at 3.0 s3.0 s

Speed

4 to fix84
  • Render-blocking requests

    1.1 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 84

    84/100

    Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    300 ms · 656 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (656 KiB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Clarity and Google Tag Manager and others), adding 608 KiB and 286 ms of main-thread time.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.

  • Improve image delivery

    35 KiB

    1 image could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 898 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Time to Interactive: 14.8 s

    14.8 s

    The page becomes fully interactive after 14.8 s. Good is under 3.8 s.

  • Real-user INP: 295 ms

    295 ms

    Real visitors wait 295 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 35% slower for real visitors

    +35%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.5 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 355 ms

    355 ms

    Scripts block taps and scrolling for 355 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 231 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • Page weight: 2.1 MB in 60 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 60 requests on a phone: scripts 1.6 MB (19), images 333 KiB (18) and other files 94 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    small_portrait_busy_london_street_with_historic_statue_traff is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.60 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9295
  • All page content should be contained by landmarks (46 elements)

    All page content should be contained by landmarks: 46 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Foxtons: Estate Agents In London. Properties for Sale, Short & Long lets”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 124 internal links, 12 external

    The homepage links to 124 pages on foxtons.co.uk and 12 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Chosen for our service, famous for our results. Properties for sale, short and long lets in London. Learn more about ou…”.

  • One H1 headline

    Your main headline reads: “London's Estate Agent”.

  • Canonical URL set

    The canonical URL is https://www.foxtons.co.uk/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.foxtons.co.uk/sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.foxtons.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (671 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 3 pages slow to respond

    https://www.foxtons.co.uk/myfoxtons/applicants, https://www.foxtons.co.uk/buy/buy_whyuse and https://www.foxtons.co.uk/help/property-fraud took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 92 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187149519&Ver=2&mid=b51e18b2-a25c-4573-a7eb-db3efb70ae62&bo=3&sid=df06a100d43b11f1ac8169116d37dee6&vid=df06df80d43b11f1881b97e1fa0809e8&vids=0&msclkid=N&pi=918639831&l.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://server-side-tagging-iitc75mtea-uc.a.run.app/g/collect?v=2&tid=G-314881246&gtm=45g92e6as1z87…”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    19 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 408 words of copy

    The homepage carries about 408 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy” and “Get a free valuation”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Buy”, “Contact” and “Get a valuation”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at foxtons.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Founded
1981
Headquarters
London

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on foxtons.co.uk, including 13 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25