Website review, no card needed
nobuhotels.com website review
Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 82 checks
This review found 34 issues worth fixing on nobuhotels.com, 13 of them high impact, across 82 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 232 ms |
| Jun 6, 2026 | 244 ms |
| Jun 13, 2026 | 252 ms |
| Jun 20, 2026 | 256 ms |
| Jun 27, 2026 | 258 ms |
| Jul 4, 2026 | 251 ms |
| Jul 11, 2026 | 246 ms |
| Jul 18, 2026 | 244 ms |
| Jul 25, 2026 | 244 ms |
| Aug 1, 2026 | 256 ms |
| Aug 8, 2026 | 265 ms |
| Aug 15, 2026 | 277 ms |
| Aug 22, 2026 | 293 ms |
| Aug 29, 2026 | 295 ms |
| Sep 5, 2026 | 297 ms |
| Sep 12, 2026 | 303 ms |
| Sep 19, 2026 | 297 ms |
| Sep 26, 2026 | 296 ms |
| Oct 3, 2026 | 296 ms |
| Oct 10, 2026 | 291 ms |
| Oct 17, 2026 | 292 ms |
| Oct 24, 2026 | 287 ms |
| Oct 31, 2026 | 287 ms |
| Nov 7, 2026 | 286 ms |
| Nov 14, 2026 | 282 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.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.7 s
5.5 s
6.3 s
Speed
Reduce unused JavaScript
10.2 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.2 s faster on a phone.
Google Tag Manager adds 2.3 s
2.3 sGoogle Tag Manager costs a phone 2.3 s of main-thread work and 2.0 MB 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.
Render-blocking requests
1.9 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Accessibe Accessibility Overlay and others), adding 3.4 MB and 3.1 s of main-thread time.
Use efficient cache lifetimes
800 ms · 196 KiB8 files are served with short cache lifetimes, so returning visitors download them again (196 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 670 ms. During a long task the page ignores taps.
Google CDN adds 421 ms
421 msGoogle CDN costs a phone 421 ms of main-thread work and 742 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.
Improve image delivery
375 KiB5 images could be 375 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,867 HTML elements
The page has 1,867 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Minify JavaScript
8 KiB8 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Largest Contentful Paint: 28.5 s
28.5 sYour largest element takes 28.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to enhance user experience and to…”.
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 273 ms
273 msReal visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 961 ms
961 msReal visitors wait 961 ms for your server to start answering (75th percentile). Good is under 800 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 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 232 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.7 MB in 144 requests
23.7 MBYour homepage downloads 23.7 MB in 144 requests on a phone: media 18.2 MB (1), scripts 3.8 MB (54) and images 1.0 MB (23). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
261 KiB1 image is downloaded at several times the size a phone draws it, for example Atlanta1.jpg at 2,000 px wide, shown at 335 px. Resized copies would save about 261 KiB.
About 6.7 g of CO₂ per visit
6.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.72 g of CO₂e: 806.3 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
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.
55 form fields without a label
55 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, VideoObject and WebPage) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.nobuhotels.com/content/uploads/2024/06/Scre…”.
14 links with vague text
14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
113 internal links, 20 external
The homepage links to 113 pages on nobuhotels.com and 20 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Experience unparalleled sophistication at our world-renowned hotels and discover why Nobu Hotels is ranked among the to…”.
One H1 headline
Your main headline reads: “Nobu Hotels”.
Title: 55 characters
Your title is a healthy 55 characters: “A Leading Group Among Luxury Hotel Chains - Nobu Hotels”.
Canonical URL set
The canonical URL is https://www.nobuhotels.com/.
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.nobuhotels.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.nobuhotels.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,074 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 70 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
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=283022140&tm=gtm002&Ver=2&mid=81d8b103-7025-4c27-8182-8c9b90cb468e&bo=1&sid=7fd582d0e49b11f1a974d560e7ba0188&vid=7fd599f0e49b11f1a4e2d3f595e9960b&vids=1&msclkid=N&pi=9.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
28 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 904 words of copy
The homepage carries about 904 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: “RESERVE”.
14 calls to action
The homepage has 14 calls to action, for example “Reserve”, “Contact Us” and “Learn More”.
3 short forms
3 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 2 of them by other companies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 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 nobuhotels.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
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- OVHcloud
Hiring
- Hiring
- 4 open roles
- Teams
- Front Office (1), Kitchen (1), Pastry Kitchen (1)
- Job board
- greenhouse
- Careers page
- www.nobuhotels.com/careers (opens in a new tab)
Company
- Founded
- 1994
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on nobuhotels.com, including 22 speed issues, 2 SEO issues and 4 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.