Website review, no card needed
motel-one.com website review
Visit site (opens in a new tab)Reviewed 2 November 202633 issues · 80 checks
This review found 33 issues worth fixing on motel-one.com, 12 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 233 ms |
| May 23, 2026 | 233 ms |
| May 30, 2026 | 233 ms |
| Jun 6, 2026 | 237 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 255 ms |
| Jun 27, 2026 | 268 ms |
| Jul 4, 2026 | 279 ms |
| Jul 11, 2026 | 290 ms |
| Jul 18, 2026 | 288 ms |
| Jul 25, 2026 | 289 ms |
| Aug 1, 2026 | 296 ms |
| Aug 8, 2026 | 305 ms |
| Aug 15, 2026 | 321 ms |
| Aug 22, 2026 | 341 ms |
| Aug 29, 2026 | 347 ms |
| Sep 5, 2026 | 355 ms |
| Sep 12, 2026 | 356 ms |
| Sep 19, 2026 | 349 ms |
| Sep 26, 2026 | 349 ms |
| Oct 3, 2026 | 349 ms |
| Oct 10, 2026 | 354 ms |
| Oct 17, 2026 | 358 ms |
| Oct 24, 2026 | 358 ms |
| Oct 31, 2026 | 354 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
1.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.9 s
9.0 s
Speed
Use efficient cache lifetimes
1.4 s · 2.2 MB190 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
1.1 s · 705 KiBAbout 705 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 10.4 s
A phone's processor spends 10.4 s on main-thread work while loading, 5.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,194 HTML elements
The page has 5,194 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
754 KiB13 images could be 754 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 715 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (fraud0.com, Usercentrics CMP and Google Tag Manager and others), adding 217 KiB and 160 ms of main-thread time.
Reduce unused CSS
40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 13.2 s
13.2 sVisually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video player”.
Real-user INP: 348 ms
348 msReal visitors wait 348 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 233 ms to 354 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
6 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 423 ms
423 msReal visitors wait 423 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 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 239 requests
3.8 MBYour homepage downloads 3.8 MB in 239 requests on a phone: images 1.6 MB (26), scripts 1.5 MB (153) and other files 286 KiB (35). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
csm_MO_Koblenz_Bar-1147_2ddb65eeda.jpeg 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 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.7 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (98 characters)
Your title is 98 characters, so Google will cut it off around 60: “Motel One | Make a reservation at affordable design hotels in Berlin, Munich, Vienna or M…”.
2 H1 headlines
There are 2 <h1> headlines (“Motel One Design Hotels: arrive, feel at home, un…” and “Your benefits at a glance:”). One clear main headline is easier for people and search engines.
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found ((untyped), BreadcrumbList, Corporation and WebSite) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
264 internal links, 40 external
The homepage links to 264 pages on motel-one.com and 40 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.motel-one.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.motel-one.com/sitemap.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: 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 (2,204 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.motel-one.com/llms.txt (5 KiB, 33 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.motel-one.com/en/hotels/erfurt/hotel-erfurt-city is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.motel-one.com/en/the-travel-edit, https://www.motel-one.com/en/hotels/coming-soon, https://www.motel-one.com/en/services/at-a-glance and https://www.motel-one.com/en/corporate/overview have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.motel-one.com/en/the-travel-edit, https://www.motel-one.com/en/travel-compass and https://www.motel-one.com/en/services/at-a-glance have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 140 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,056 words of copy
The homepage carries about 1,056 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: “BOOK BOOK BOOK” and “BOOK A HOTEL NOW”.
5 calls to action
The homepage has 5 calls to action, for example “Register nowRegister nowRegister now”, “Download from the App Store” and “Contact”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks, a star rating and 13 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
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.
2 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 motel-one.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
- Motel One
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on motel-one.com, including 16 speed issues, 4 SEO issues and 3 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.