Website review, no card needed

esland.co.uk logo

esland.co.uk website review

Visit site (opens in a new tab)Reviewed 2 November 202639 issues · 91 checks

This review found 39 issues worth fixing on esland.co.uk, 11 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
1.2 s642 msMay 16Oct 31799 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026923 ms
May 23, 2026880 ms
May 30, 2026931 ms
Jun 6, 20261.2 s
Jun 13, 2026965 ms
Jun 20, 2026942 ms
Jun 27, 2026964 ms
Jul 4, 2026782 ms
Jul 11, 2026709 ms
Jul 18, 2026786 ms
Jul 25, 2026733 ms
Aug 1, 2026814 ms
Aug 8, 2026895 ms
Aug 15, 2026794 ms
Aug 22, 2026889 ms
Aug 29, 2026824 ms
Sep 5, 2026872 ms
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 2026980 ms
Oct 3, 2026959 ms
Oct 10, 2026830 ms
Oct 17, 2026748 ms
Oct 24, 2026851 ms
Oct 31, 2026799 ms
Real-visitor tap response (INP)75th percentile, phones
103 ms76 msMay 16Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202685 ms
May 23, 202685 ms
May 30, 202683 ms
Jun 6, 202684 ms
Jun 13, 202686 ms
Jun 20, 202682 ms
Jun 27, 202684 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202686 ms
Jul 25, 202686 ms
Aug 1, 202691 ms
Aug 8, 2026100 ms
Aug 15, 202691 ms
Aug 22, 202687 ms
Aug 29, 202682 ms
Sep 5, 202685 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202686 ms
Oct 10, 202681 ms
Oct 17, 202683 ms
Oct 24, 202686 ms
Oct 31, 202688 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 esland.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. esland.co.uk at 0.5 s0.5 s
  2. esland.co.uk at 1.1 s1.1 s
  3. esland.co.uk at 1.6 s1.6 s
  4. esland.co.uk at 2.1 s2.1 s
  5. esland.co.uk at 2.7 s2.7 s
  6. esland.co.uk at 3.2 s3.2 s
  7. esland.co.uk at 3.8 s3.8 s
  8. esland.co.uk at 4.3 s4.3 s

Speed

9 to fix66
  • Use efficient cache lifetimes

    2.1 s · 1.9 MB

    42 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Render-blocking requests

    2.9 s

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

  • Mobile performance score: 66

    66/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, juniperwebsites.co.uk and Google/Doubleclick Ads and others), adding 2.2 MB and 527 ms of main-thread time.

  • Reduce unused CSS

    610 ms · 112 KiB

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

  • Improve image delivery

    608 KiB

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

  • Google Tag Manager adds 340 ms

    340 ms

    Google Tag Manager costs a phone 340 ms of main-thread work and 465 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • juniperwebsites.co.uk adds 184 ms

    184 ms

    juniperwebsites.co.uk costs a phone 184 ms of main-thread work and 1.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    348 KiB

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

  • 6 long tasks on the main thread

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

  • Minify CSS

    150 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Document request latency

    41 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    35 KiB

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

  • 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 JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 89 ms

    89 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 19.0 s

    19.0 s

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

  • Largest Contentful Paint: 5.5 s

    5.5 s

    Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies to store information on your compute…”.

  • Speed Index: 7.2 s

    7.2 s

    Visually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Total Blocking Time: 167 ms

    167 ms

    Scripts block the page for only 167 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

4 to fix50
  • 1 image over 500 KB

    0070EFD158EFF19D3B71AE78C338C508.jpg weighs 713 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.5 MB in 66 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 66 requests on a phone: scripts 2.1 MB (24), images 876 KiB (12) and fonts 348 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (841 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image far larger than shown

    469 KiB

    1 image is downloaded at several times the size a phone draws it, for example 0070EFD158EFF19D3B71AE78C338C508.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 469 KiB.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 8389
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 3 tap targets too small

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

  • All page content should be contained by landmarks (4 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 8577
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “Esland - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 58 internal links, 10 external

    The homepage links to 58 pages on esland.co.uk and 10 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Esland”.

  • Canonical URL set

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

  • 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.esland.co.uk/googlesitemap.asp.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 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.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 4 pages share 2 titles

    https://www.esland.co.uk/about and https://www.esland.co.uk/about-us/about-us all use the title “Esland - About us”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.esland.co.uk/about, https://www.esland.co.uk/about-us/about-us, https://www.esland.co.uk/about-us/care-with-education, https://www.esland.co.uk/ethos-and-values, https://www.esland.co.uk/our-impact and https://www.esland.co.uk/locations and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://www.esland.co.uk/therapeutic-approach, https://www.esland.co.uk/therapeutic-approach/therapeutic-approach, https://www.esland.co.uk/therapeutic-model and https://www.esland.co.uk/therapeutic-pathways took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No call to action on the first screen

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

  • 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: 10 testimonial or review blocks. 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 520 words of copy

    The homepage carries about 520 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Sign up for ongoing updates” and “Join us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 esland.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
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on esland.co.uk, including 14 speed issues, 4 SEO issues and 5 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