Website review, no card needed

mailordertrees.co.uk logo

mailordertrees.co.uk website review

Visit site (opens in a new tab)Reviewed 11 November 202622 issues · 80 checks

This review found 22 issues worth fixing on mailordertrees.co.uk, 7 of them high impact, across 80 checks. The most urgent: page weight: 7.2 MB in 360 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
1.3 s733 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 2026923 ms
Oct 3, 2026801 ms
Oct 10, 2026804 ms
Oct 17, 2026931 ms
Oct 24, 20261.0 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
201 ms148 msMay 23Nov 7180 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026154 ms
May 30, 2026157 ms
Jun 6, 2026160 ms
Jun 13, 2026162 ms
Jun 20, 2026165 ms
Jun 27, 2026169 ms
Jul 4, 2026176 ms
Jul 11, 2026179 ms
Jul 18, 2026175 ms
Jul 25, 2026171 ms
Aug 1, 2026172 ms
Aug 8, 2026177 ms
Aug 15, 2026183 ms
Aug 22, 2026191 ms
Aug 29, 2026194 ms
Sep 5, 2026195 ms
Sep 12, 2026195 ms
Sep 19, 2026188 ms
Sep 26, 2026189 ms
Oct 3, 2026190 ms
Oct 10, 2026192 ms
Oct 17, 2026192 ms
Oct 24, 2026185 ms
Oct 31, 2026182 ms
Nov 7, 2026180 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 mailordertrees.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix90
  • 7,106 HTML elements

    The page has 7,106 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Render-blocking requests

    550 ms

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Shopify adds 2 ms

    2 ms

    Shopify costs a phone 2 ms of main-thread work and 874 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.

  • Improve image delivery

    212 KiB

    9 images could be 212 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Cloudflare CDN and Unpkg and others), adding 1,011 KiB and 3 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    28 KiB

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

  • Reduce unused CSS

    22 KiB

    About 22 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.2 s

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

  • Server response: 32 ms

    32 ms

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

Core Web Vitals

3 to fix100
  • 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.

  • Time to Interactive: 6.9 s

    6.9 s

    The page becomes fully interactive after 6.9 s. Good is under 3.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 text “🔄”.

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

    +16%

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

10 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: 195 ms

    195 ms

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

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (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.

  • Real-user TTFB: 692 ms

    692 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Speed Index: 3.1 s

    3.1 s

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

  • Cumulative Layout Shift: 0.006

    0.006

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

2 to fix50
  • Page weight: 7.2 MB in 360 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 360 requests on a phone: images 5.7 MB (246), scripts 833 KiB (50) and fonts 326 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 12 images far larger than shown

    504 KiB

    12 images are downloaded at several times the size a phone draws them, for example 10_1024x1024.png at 553 px wide, shown at 88 px. Resized copies would save about 504 KiB.

  • About 2.0 g of CO₂ per visit

    2.05 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.05 g of CO₂e: 245.5 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 load when needed

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

Accessibility

5 to fixGoogle 8793
  • 7 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 528 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 4 H1 headlines

    There are 4 <h1> headlines (“2 For 1 Sale Now On”, “Native Trees” and “Flowering Cherry Trees”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 633 internal links, 1 external

    The homepage links to 633 pages on mailordertrees.co.uk and 1 external page.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Buy Trees, Fruit Trees, Shrubs and Hedging Plants Online from MailOrderTrees.co.uk. Buy British Grown Tree Gifts Online…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Buy Trees, Fruit Trees, Shrubs and Gifts from Mail Order Trees”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.mailordertrees.co.uk/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.mailordertrees.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.mailordertrees.co.uk/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without an H1

    https://www.mailordertrees.co.uk/collections/all, https://www.mailordertrees.co.uk/collections/ornamental-tree-buy-one-get-one-free, https://www.mailordertrees.co.uk/collections/ornamental-trees, https://www.mailordertrees.co.uk/collections/acacia-mimosa-trees, https://www.mailordertrees.co.uk/collections/acer-japanese-maple-trees and https://www.mailordertrees.co.uk/collections/acer-trees-sycamore-and-maple-trees and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.mailordertrees.co.uk/collections/acer-japanese-maple-trees, https://www.mailordertrees.co.uk/collections/acer-trees-sycamore-and-maple-trees, https://www.mailordertrees.co.uk/collections/aesculus-horse-chestnut-trees, https://www.mailordertrees.co.uk/collections/alnus-alder-trees, https://www.mailordertrees.co.uk/collections/amelanchier-amelanchier-trees and https://www.mailordertrees.co.uk/collections/betula-birch-trees and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 149 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 a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0557/0657/files/wildlife.png?v=1703061573.

  • 4 small tap targets

    4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “imageLoaded is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 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 426 words of copy

    The homepage carries about 426 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join Our Mission” and “Shop Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Join Our Mission”, “Buy One Get One Free” and “Shop Now”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 mailordertrees.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Cmp Insert Code · Gsc Countdown Timer · Shopify App Template Php · Freegifts · Restockrocket · All In One Discount · ywxi.net · trustpilot.com · trustedsite.com · bogos.io · designpackscdn.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on mailordertrees.co.uk, including 6 speed issues, 3 SEO issues and 1 conversion gap. 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