Website review, no card needed
adaremanor.com website review
Visit site (opens in a new tab)Reviewed 18 October 202627 issues · 85 checks
This review found 27 issues worth fixing on adaremanor.com, 8 of them high impact, across 85 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.1 s |
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 167 ms |
| May 2, 2026 | 167 ms |
| May 9, 2026 | 167 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 164 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 167 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 176 ms |
| Aug 15, 2026 | 178 ms |
| Aug 22, 2026 | 179 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 186 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 187 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.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Speed
Reduce unused JavaScript
2.1 s · 880 KiBAbout 880 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.
Improve image delivery
500 ms · 3.5 MB19 images could be 3.5 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, Google Maps and Clarity and others), adding 1.7 MB and 1.1 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 37). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 777 ms
777 msGoogle Tag Manager costs a phone 777 ms of main-thread work and 1.1 MB 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
375 KiB5 files are served with short cache lifetimes, so returning visitors download them again (375 KiB).
1,752 HTML elements
The page has 1,752 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Maps adds 128 ms
128 msGoogle Maps costs a phone 128 ms of main-thread work and 435 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 226 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 108 ms
108 msYour server sent the HTML in 108 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 34.0 s
34.0 sYour largest element takes 34.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hero Video Player”.
Time to Interactive: 40.7 s
40.7 sThe page becomes fully interactive after 40.7 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 438 ms
438 msScripts block taps and scrolling for 438 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 167 ms to 187 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.069
0.069The layout barely moves while loading (CLS 0.069, good is under 0.1).
Images and page weight
Page weight: 15.7 MB in 143 requests
15.7 MBYour homepage downloads 15.7 MB in 143 requests on a phone: images 13.3 MB (54), scripts 2.0 MB (55) and fonts 213 KiB (6). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
19 images in older formats
19 images (3.5 MB) are 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.
6 images below the first screen load straight away
6 images further down the page (958 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
7 images far larger than shown
383 KiB7 images are downloaded at several times the size a phone draws them, for example dragon-brown-8.svg at 390 px wide, shown at 129 px. Resized copies would save about 383 KiB.
About 4.4 g of CO₂ per visit
4.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.44 g of CO₂e: 532.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
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
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
210 internal links, 28 external
The homepage links to 210 pages on adaremanor.com and 28 external pages.
8 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Acclaimed as one of Europe's best 5-star luxury resorts, Adare Manor sets the standard for elegance, fine dining, and I…”.
One H1 headline
Your main headline reads: “A Lavish Experience”.
Title: 55 characters
Your title is a healthy 55 characters: “Adare Manor | One of Europe's Best 5 Star Resort Hotels”.
Canonical URL set
The canonical URL is https://www.adaremanor.com/.
Structured data in place
Structured data found: BreadcrumbList, Hotel, ImageObject, Organization and WebPage.
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.adaremanor.com/sitemap_index.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,232 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.adaremanor.com/llms.txt (4 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
1 page slow to respond
https://www.adaremanor.com/home/contact-us took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 121 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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5663288&tm=gtm002&Ver=2&mid=5f3f919c-f331-4dc0-b961-8e9a0a651ced&bo=1&sid=ce198880caa211f1a84c29d0fec62238&vid=ce19b350caa211f18f0d53daeebc3ae9&vids=1&msclkid=N&pi=918.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
37 of 39 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 10 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 383 words of copy
The homepage carries about 383 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
31 calls to action
The homepage has 31 calls to action, for example “Contact Us”, “Newsletter Signup” and “Harry Lowes Chocolate Shop”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
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.
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 adaremanor.com, 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
- Analytics
- Google Tag Manager | Microsoft Clarity
Company
- Founded
- 1862
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on adaremanor.com, including 15 speed issues, 1 SEO issue 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.