Website review, no card needed
mpevans.co.uk website review
Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 82 checks
This review found 35 issues worth fixing on mpevans.co.uk, 12 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 106 ms |
| May 16, 2026 | 106 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 116 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 109 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
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Reduce unused JavaScript
2.1 s · 416 KiBAbout 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 747 KiB79 files are served with short cache lifetimes, so returning visitors download them again (747 KiB).
Render-blocking requests
2.0 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
500 ms · 498 KiB3 images could be 498 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused CSS
450 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
2,035 HTML elements
The page has 2,035 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 637 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, irdataservices.com and Google Fonts and others), adding 929 KiB and 184 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 401 ms of it running JavaScript. That is comfortably low.
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 5.3 s
5.3 sReal visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.
Largest content (LCP) got 56% slower for real visitors
+56%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 106 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
Total Blocking Time: 60 ms
60 msScripts block the page for only 60 ms while loading. Good is under 200 ms.
Images and page weight
3 images far larger than shown
468 KiB3 images are downloaded at several times the size a phone draws them, for example hero-banner-compressed-1.webp at 2,560 px wide, shown at 180 px. Resized copies would save about 468 KiB.
About 0.4 g of CO₂ per visit
0.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.38 g of CO₂e: 45.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.3 MB in 99 requests
1.3 MBYour homepage downloads 1.3 MB in 99 requests on a phone: images 637 KiB (72), scripts 553 KiB (11) and stylesheets 77 KiB (6). That is a lean page.
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
Frames without titles
10 frames have no title, so screen-reader users cannot tell what they contain.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 117 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “M.P. Evans Group PLC - Sustainable Indonesian palm oil - M.P. Evans”.
Meta description is long (205 characters)
Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
271 internal links, 16 external
The homepage links to 271 pages on mpevans.co.uk and 16 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.mpevans.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.mpevans.co.uk/sitemap.xml.
AI search readiness
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.mpevans.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 (1,880 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.mpevans.co.uk/investors/market-prices/cpo-price, https://www.mpevans.co.uk/about, https://www.mpevans.co.uk/about/history, https://www.mpevans.co.uk/about/strategy, https://www.mpevans.co.uk/plantations and https://www.mpevans.co.uk/plantations/map-and-locations and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mpevans.co.uk/investors, whose canonical is https://www.mpevans.co.uk/investors/why-invest. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://www.mpevans.co.uk/investors took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 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.
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 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 13 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 “Connecting to 'https://fonts.googleapis.com/css2?family=Fira+Sans:wght@400;500;700&display=swap' violates the following…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 753 words of copy
The homepage carries about 753 words of visible text.
5 checks passed
25 calls to action
The homepage has 25 calls to action, for example “Learn more”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 mpevans.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
- CMS
- WordPress
- 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 35 issues on mpevans.co.uk, including 18 speed issues, 5 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.