Website review, no card needed
rathwood.com website review
Visit site (opens in a new tab)Reviewed 9 November 202615 issues · 74 checks
This review found 15 issues worth fixing on rathwood.com, 1 of them high impact, across 74 checks. The most urgent: no social proof. 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
91A- #1,499 of 120,620 reviewed websitesbeats 98%
- #673 of 68,290 online storesbeats 98%
- #645 of 62,230 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.0 s |
| Nov 7, 2026 | 976 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 143 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 126 ms |
| Oct 31, 2026 | 124 ms |
| Nov 7, 2026 | 124 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.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Improve image delivery
900 ms · 321 KiB7 images could be 321 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 314 KiB9 files are served with short cache lifetimes, so returning visitors download them again (314 KiB).
Reduce unused JavaScript
150 ms · 50 KiBAbout 50 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 54 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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 173 ms of it running JavaScript. That is comfortably low.
Server response: 160 ms
160 msYour server sent the HTML in 160 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 143 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 354 ms
354 msReal visitors wait 354 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 3.3 s
3.3 sThe page is fully interactive after 3.3 s.
Speed Index: 2.2 s
2.2 sVisually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
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.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 35 requests
3.4 MBYour homepage downloads 3.4 MB in 35 requests on a phone: media 2.5 MB (1), images 604 KiB (8) and scripts 161 KiB (18). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
143 KiB5 images are downloaded at several times the size a phone draws them, for example ark-playcentre.webp at 1,200 px wide, shown at 350 px. Resized copies would save about 143 KiB.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.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
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
SEO
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
30 internal links, 8 external
The homepage links to 30 pages on rathwood.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Wander the woods.Stay for the day.”.
Title: 65 characters
Your title is a healthy 65 characters: “Rathwood | Woodland, food & family days out in Tullow, Co. Carlow”.
Canonical URL set
The canonical URL is https://www.rathwood.com/.
Structured data in place
Structured data found: LocalBusiness, TouristAttraction and WebSite.
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://www.rathwood.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.rathwood.com/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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (415 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page with very little text
https://www.rathwood.com/contact 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 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
3 small tap targets
3 of 15 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 404 words of copy
The homepage carries about 404 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: “NOW BOOKING Santa Train Book now”.
3 calls to action
The homepage has 3 calls to action, for example “Opening hours & contact”, “Contact” and “Sign up”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 cookie set on arrival
1Opening 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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 rathwood.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on rathwood.com, including 3 speed issues, 1 SEO issue and 4 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.