Website review, no card needed
maybourne.com website review
Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 80 checks
This review found 29 issues worth fixing on maybourne.com, 8 of them high impact, across 80 checks. The most urgent: page weight: 11.8 MB in 99 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 156 ms |
| May 30, 2026 | 156 ms |
| Jun 6, 2026 | 164 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 165 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 168 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 191 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 200 ms |
| Oct 17, 2026 | 201 ms |
| Oct 24, 2026 | 204 ms |
| Oct 31, 2026 | 207 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.0 s
Speed
audioeye.com adds 1.0 s
1.0 saudioeye.com costs a phone 1.0 s of main-thread work and 298 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
150 ms · 5.0 MB29 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Optimizely and others), adding 1.1 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
340 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 340 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Google Tag Manager adds 315 ms
315 msGoogle Tag Manager costs a phone 315 ms of main-thread work and 475 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,987 HTML elements
The page has 1,987 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
202 KiB10 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.9 s
20.9 sThe page becomes fully interactive after 20.9 s. Good is under 3.8 s.
Total Blocking Time: 978 ms
978 msScripts block taps and scrolling for 978 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
9 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: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 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.6 s
0.6 sReal visitors see the first content after 0.6 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 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 1.6 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.8 MB in 99 requests
11.8 MBYour homepage downloads 11.8 MB in 99 requests on a phone: media 8.4 MB (3), scripts 2.3 MB (47) and images 674 KiB (19). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BER-THE-ROOFTOP-POOL-FEAST-OFF-PISTE-06 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).
About 3.3 g of CO₂ per visit
3.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.35 g of CO₂e: 401.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
44 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: 44 passed and 2 failed. 2 mores 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 (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
100 internal links, 9 external
The homepage links to 100 pages on maybourne.com and 9 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Maybourne Hotel Collection”.
Title: 43 characters
Your title is a healthy 43 characters: “Creating Stories of Distinction - Maybourne”.
Canonical URL set
The canonical URL is https://www.maybourne.com/en.
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.maybourne.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 (677 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.maybourne.com/llms.txt (4 KiB, 23 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.maybourne.com/en/festive has no <title>, so Google invents the link text in results.
1 page without a meta description
https://www.maybourne.com/en/festive has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 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.
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.
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.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
63 of 63 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: 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.
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 605 words of copy
The homepage carries about 605 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BOOK” and “CONTACT”.
7 calls to action
The homepage has 7 calls to action, for example “Book”, “Contact” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 maybourne.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
- Next.js
- Hosting
- Episerver
Hiring
- Hiring
- 23 open roles
- Job board
- adp
Company
- Founded
- 2005
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on maybourne.com, including 15 speed issues, 2 SEO issues and 2 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.