Website review, no card needed
h-hotels.com website review
Visit site (opens in a new tab)Reviewed 25 October 202619 issues · 73 checks
This review found 19 issues worth fixing on h-hotels.com, 5 of them high impact, across 73 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) |
|---|---|
| May 2, 2026 | 971 ms |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 998 ms |
| Jun 27, 2026 | 975 ms |
| Jul 4, 2026 | 991 ms |
| Jul 11, 2026 | 965 ms |
| Jul 18, 2026 | 967 ms |
| Jul 25, 2026 | 963 ms |
| Aug 1, 2026 | 944 ms |
| Aug 8, 2026 | 958 ms |
| Aug 15, 2026 | 949 ms |
| Aug 22, 2026 | 940 ms |
| Aug 29, 2026 | 948 ms |
| Sep 5, 2026 | 939 ms |
| Sep 12, 2026 | 932 ms |
| Sep 19, 2026 | 930 ms |
| Sep 26, 2026 | 907 ms |
| Oct 3, 2026 | 893 ms |
| Oct 10, 2026 | 878 ms |
| Oct 17, 2026 | 867 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 117 ms |
| May 9, 2026 | 118 ms |
| May 16, 2026 | 118 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 110 ms |
| Oct 17, 2026 | 108 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.6 s
3.0 s
Speed
Reduce unused JavaScript
3.0 s · 571 KiBAbout 571 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
882 KiB14 images could be 882 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
300 ms · 56 KiBAbout 56 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.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
4 third-party services on the page
4 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and thehotelsnetwork.com and others), adding 601 KiB and 314 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 53 KiB6 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 127 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.1 s
16.1 sYour largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Um Erkenntnisse über unsere Webseite, die Webseitennutzung …”.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 239 ms
239 msScripts block taps and scrolling for 239 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 117 ms to 108 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 89 ms
89 msReal visitors wait 89 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: 216 ms
216 msReal visitors wait 216 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 80 requests
3.8 MBYour homepage downloads 3.8 MB in 80 requests on a phone: images 2.4 MB (30), scripts 1.1 MB (30) and fonts 102 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.7 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
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails 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.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Urlaub buchen bei H-Hotels” and “Exklusive Vorteile für Sie – Bei H-Hotels übernac…”). One clear main headline is easier for people and search engines.
83 internal links, 10 external
The homepage links to 83 pages on h-hotels.com and 10 external pages.
7 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “H-Hotels.com: Die Hyperion, H4, H2 und H+ Hotels in Europa. Buchen Sie mit exklusiven Vorteilen und Bestpreis Garantie!”.
Title: 54 characters
Your title is a healthy 54 characters: “H-Hotels.com - Offizielle Webseite HYPERION & H-Hotels”.
Canonical URL set
The canonical URL is https://www.h-hotels.com/.
Structured data in place
Structured data found: BreadcrumbList 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.
XML sitemap found
Your XML sitemap is reachable at https://www.h-hotels.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.
No llms.txt
There is no https://www.h-hotels.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.
2 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 (567 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 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
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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 446 words of copy
The homepage carries about 446 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Presse-Download”.
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 h-hotels.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 1969
- Headquarters
- Bad Arolsen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on h-hotels.com, including 10 speed issues, 1 SEO issue 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.