Website review, no card needed
chapeldown.com website review
Visit site (opens in a new tab)Reviewed 6 November 202631 issues · 89 checks
This review found 31 issues worth fixing on chapeldown.com, 8 of them high impact, across 89 checks. The most urgent: page weight: 12.7 MB in 330 requests. 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
86B- #11,781 of 120,865 reviewed websitesbeats 87%
- #7,195 of 68,427 online storesbeats 85%
- #6,972 of 62,354 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 161 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 165 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 167 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 152 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
Speed
Render-blocking requests
1.2 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
500 ms · 1.6 MB24 images could be 1.6 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and PayPal and others), adding 1.5 MB and 1.2 s of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 340 KiB16 files are served with short cache lifetimes, so returning visitors download them again (340 KiB).
Reduce unused JavaScript
560 KiBAbout 560 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 355 ms
355 msGoogle Tag Manager costs a phone 355 ms of main-thread work and 341 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.
Cookiebot adds 351 ms
351 msCookiebot costs a phone 351 ms of main-thread work and 182 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.
PayPal adds 284 ms
284 msPayPal costs a phone 284 ms of main-thread work and 389 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.
Reduce unused CSS
40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 58 ms
58 msYour server sent the HTML in 58 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 25.0 s
25.0 sThe page becomes fully interactive after 25.0 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 423 ms
423 msScripts block taps and scrolling for 423 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.126
0.126The layout shifts by 0.126 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 161 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 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.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 540 ms
540 msReal visitors wait 540 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 12.7 MB in 330 requests
12.7 MBYour homepage downloads 12.7 MB in 330 requests on a phone: media 6.8 MB (3), images 2.7 MB (44) and scripts 1.3 MB (67). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (88 KiB) is 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.
About 3.6 g of CO₂ per visit
3.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.60 g of CO₂e: 432.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
10 dropdowns have no label.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (97 elements)
All page content should be contained by landmarks: 97 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 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: 41 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (201 characters)
Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
154 internal links, 7 external
The homepage links to 154 pages on chapeldown.com and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “VISIT OUR HOME”.
Title: 50 characters
Your title is a healthy 50 characters: “Chapel Down | Award-winning English Sparkling Wine”.
Canonical URL set
The canonical URL is https://chapeldown.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://chapeldown.com/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.
3 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,103 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://chapeldown.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
7 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 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
46 of 51 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 850 words of copy
The homepage carries about 850 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “Shop All”.
14 calls to action
The homepage has 14 calls to action, for example “Shop”, “Shop All” and “Book a Tour or Event”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 chapeldown.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Rebuy Personalization Engine · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Page Speed Optimizer · rebuyengine.com · w3apps.co
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
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Headquarters
- Tenterden
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on chapeldown.com, including 15 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.