landsec.com website review

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

About 422 KiB of JavaScript is downloaded but never used on this page.

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

About 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).

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

2 third-party services load with your homepage (Optanon and Google Tag Manager), adding 16 KiB and 0 ms of main-thread time.

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.

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

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

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 9 characters: “Not Found”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 9 characters: “Not Found”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.landsec.com/sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 6 pages on landsec.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.landsec.com/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.

https://www.landsec.com/en, https://www.landsec.com/en/media-insights/press-releases/landsec-acquires-100-stake-in-metrocentre-gateshead, https://www.landsec.com/en/talent/working-at-landsec, https://www.landsec.com/en/investors/investors-overview, https://www.landsec.com/en/about/about-landsec/our-properties and https://www.landsec.com/en/media-insights/media-centre all use the title “Not Found”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.landsec.com/en/media-insights/press-releases/landsec-acquires-100-stake-in-metrocentre-gateshead, https://www.landsec.com/en/talent/working-at-landsec, https://www.landsec.com/en/investors/investors-overview, https://www.landsec.com/en/about/about-landsec/our-properties and https://www.landsec.com/en/media-insights/media-centre use the same meta description. A description written for each page earns more clicks.

https://www.landsec.com/en/about/about-landsec/our-properties has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.landsec.com/en/media-insights/press-releases/landsec-acquires-100-stake-in-metrocentre-gateshead, https://www.landsec.com/en/talent/working-at-landsec, https://www.landsec.com/en/investors/investors-overview and https://www.landsec.com/en/about/about-landsec/our-properties took over 3 s to send their HTML from our server.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

7 images failed to load on a phone, for example https://content.landsec.com/media/yayesrvy/wmagpiebanner.webp.

2 errors were logged to the browser console while the page loaded, for example “Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid…”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 4 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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