Website review, no card needed
amberhotel.ch website review
Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 85 checks
This review found 35 issues worth fixing on amberhotel.ch, 13 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
73CClosest competitors among reviewed websites
Compare side by sideOne 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
Reduce unused JavaScript
4.5 s · 1,012 KiBAbout 1,012 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s 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 cdn-website.com and others), adding 2.9 MB and 1.2 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.
Google Tag Manager adds 638 ms
638 msGoogle Tag Manager costs a phone 638 ms of main-thread work and 799 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.
Use efficient cache lifetimes
550 ms · 156 KiB16 files are served with short cache lifetimes, so returning visitors download them again (156 KiB).
Reduce unused CSS
450 ms · 61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
cdn-website.com adds 183 ms
183 mscdn-website.com costs a phone 183 ms of main-thread work and 1.4 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.
Google Maps adds 237 ms
237 msGoogle Maps costs a phone 237 ms of main-thread work and 454 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Improve image delivery
55 KiB2 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.9 s
17.9 sYour largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AMBER SKI-IN/OUT FRONT LINE HOTEL & SPA IN SAAS FEE, SWITZE…”.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 346 ms
346 msScripts block taps and scrolling for 346 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 97 requests
3.2 MBYour homepage downloads 3.2 MB in 97 requests on a phone: scripts 1.7 MB (47), images 706 KiB (16) and fonts 655 KiB (13). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
27 internal links, 8 external
The homepage links to 27 pages on amberhotel.ch and 8 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “First line hotel next to the slopes. Spacious romantic & family rooms. Modern ski room. All rates include rich breakfas…”.
One H1 headline
Your main headline reads: “Amber Ski-in/out”.
Title: 49 characters
Your title is a healthy 49 characters: “Ski in-out Hotel & Spa. Best Location in Saas Fee”.
Canonical URL set
The canonical URL is https://www.amberhotel.ch/.
Structured data in place
Structured data found: 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.amberhotel.ch/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 (727 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.amberhotel.ch/llms.txt (4 KiB, 24 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.amberhotel.ch/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://www.amberhotel.ch/fr and https://www.amberhotel.ch/home all use the title “Ski in-out Hotel & Spa. Best Location in Saas Fee”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.amberhotel.ch/fr and https://www.amberhotel.ch/home use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://www.amberhotel.ch/breakfast 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Every page has a meta description
All 9 pages that loaded have a meta description.
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 9 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.amberhotel.ch/alt=.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://irp.cdn-website.com/fonts/fontawesome-webfont.woff2?v=4.7.0' from origin 'https://www.amberh…”.
2 checks passed
Tap targets are thumb-sized
18 of 22 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,036 words of copy
The homepage carries about 1,036 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: “BOOK NOW”.
5 calls to action
The homepage has 5 calls to action, for example “BOOK ONLINE” and “BOOK NOW”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) 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 amberhotel.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
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 amberhotel.ch, including 16 speed 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.