Website review, no card needed
thecoconutcambridge.com website review
Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 73 checks
This review found 35 issues worth fixing on thecoconutcambridge.com, 10 of them high impact, across 73 checks. The most urgent: improve image delivery. 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
73C- #84,944 of 113,933 reviewed websitesbeats 22%
- #54,073 of 65,819 online storesbeats 15%
- #50,804 of 60,228 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 2.1 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.2 s · 656 KiB28 images could be 656 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
5,513 HTML elements
The page has 5,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (extendons.com, Shopify and Amazon Web Services and others), adding 367 KiB and 773 ms of main-thread time.
Reduce unused JavaScript
600 ms · 156 KiBAbout 156 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
extendons.com adds 687 ms
687 msextendons.com costs a phone 687 ms of main-thread work and 23 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 431 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 6 KiBPolyfills for old browsers add 6 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
22 KiB22 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
Use efficient cache lifetimes
3 KiB3 files are served with short cache lifetimes, so returning visitors download them again (3 KiB).
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Make it look real”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Total Blocking Time: 381 ms
381 msScripts block taps and scrolling for 381 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Largest content (LCP) got 33% faster for real visitors
-33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 249 requests
3.3 MBYour homepage downloads 3.3 MB in 249 requests on a phone: images 1.8 MB (59), other files 797 KiB (105) and scripts 470 KiB (49). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
make-it-look-real.png 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).
2 images far larger than shown
96 KiB2 images are downloaded at several times the size a phone draws them, for example make-it-look-real.png at 1,536 px wide, shown at 390 px. Resized copies would save about 96 KiB.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
76 buttons without a name
76 buttons have no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (21 characters)
Your meta description is only 21 characters: “The Coconut Cambridge”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
250 internal links, 2 external
The homepage links to 250 pages on thecoconutcambridge.com and 2 external pages.
5 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “The Coconut Cambridge – The coconut cambridge”.
Canonical URL set
The canonical URL is https://thecoconutcambridge.com/.
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://thecoconutcambridge.com/sitemap.xml.
AI search readiness
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 (3,074 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://thecoconutcambridge.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://thecoconutcambridge.com/collections/confectionary, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://thecoconutcambridge.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://thecoconutcambridge.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://thecoconutcambridge.com/collections/all, https://thecoconutcambridge.com/customer_authentication/redirect, https://thecoconutcambridge.com/policies/shipping-policy, https://thecoconutcambridge.com/collections/fresh-fruit, https://thecoconutcambridge.com/collections/fresh-meat-fish and https://thecoconutcambridge.com/collections/bakery and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://thecoconutcambridge.com/collections/all, https://thecoconutcambridge.com/customer_authentication/redirect, https://thecoconutcambridge.com/collections/fresh-fruit, https://thecoconutcambridge.com/collections/fresh-meat-fish, https://thecoconutcambridge.com/collections/bakery and https://thecoconutcambridge.com/collections/rice and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://thecoconutcambridge.com/pages/wholesale-partnership-form 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
48 small tap targets
48 of 164 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 688 words of copy
The homepage carries about 688 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact information”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
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.
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 thecoconutcambridge.com, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Eaze Button · Powerful Form Builder · Essential Post Purchase Upsell · extendons.com · amazonaws.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
- E-commerce
- Shopify
- Hosting
- Shopify
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 thecoconutcambridge.com, including 12 speed issues, 3 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.