Website review, no card needed

preferredhotels.com logo

preferredhotels.com website review

Visit site (opens in a new tab)Reviewed 20 November 202645 issues · 80 checks

This review found 45 issues worth fixing on preferredhotels.com, 10 of them high impact, across 80 checks. The most urgent: page weight: 31.4 MB in 275 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
5.4 s3.2 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.8 s
Jun 6, 20264.7 s
Jun 13, 20264.8 s
Jun 20, 20264.8 s
Jun 27, 20265.1 s
Jul 4, 20265.1 s
Jul 11, 20265.0 s
Jul 18, 20265.0 s
Jul 25, 20264.7 s
Aug 1, 20264.6 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.4 s
Sep 19, 20264.2 s
Sep 26, 20264.0 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.5 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
167 ms132 msMay 30Nov 14161 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026136 ms
Jun 6, 2026141 ms
Jun 13, 2026154 ms
Jun 20, 2026162 ms
Jun 27, 2026162 ms
Jul 4, 2026161 ms
Jul 11, 2026154 ms
Jul 18, 2026150 ms
Jul 25, 2026148 ms
Aug 1, 2026145 ms
Aug 8, 2026144 ms
Aug 15, 2026147 ms
Aug 22, 2026153 ms
Aug 29, 2026155 ms
Sep 5, 2026160 ms
Sep 12, 2026160 ms
Sep 19, 2026157 ms
Sep 26, 2026157 ms
Oct 3, 2026157 ms
Oct 10, 2026160 ms
Oct 17, 2026162 ms
Oct 24, 2026162 ms
Oct 31, 2026162 ms
Nov 7, 2026163 ms
Nov 14, 2026161 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

Full-page screenshot of preferredhotels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. preferredhotels.com at 0.4 s0.4 s
  2. preferredhotels.com at 0.8 s0.8 s
  3. preferredhotels.com at 1.1 s1.1 s
  4. preferredhotels.com at 1.5 s1.5 s
  5. preferredhotels.com at 1.9 s1.9 s
  6. preferredhotels.com at 2.3 s2.3 s
  7. preferredhotels.com at 2.7 s2.7 s
  8. preferredhotels.com at 3.0 s3.0 s

Speed

7 to fix
  • Google Tag Manager adds 2.3 s

    2.3 s

    Google Tag Manager costs a phone 2.3 s of main-thread work and 1.8 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.

  • Main-thread work: 8.8 s

    A phone's processor spends 8.8 s on main-thread work while loading, 6.0 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, commoninja.com and Facebook and others), adding 4.1 MB and 4.0 s of main-thread time.

  • commoninja.com adds 764 ms

    764 ms

    commoninja.com costs a phone 764 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.

  • Facebook adds 311 ms

    311 ms

    Facebook costs a phone 311 ms of main-thread work and 275 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.

  • Optanon adds 260 ms

    260 ms

    Optanon costs a phone 260 ms of main-thread work and 256 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.

  • Google Maps adds 201 ms

    201 ms

    Google Maps costs a phone 201 ms of main-thread work and 394 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.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

1 checks passed
  • Server response: 30 ms

    30 ms

    Your server sent the HTML in 30 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • 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.

  • Speed Index: 17.0 s

    17.0 s

    Visually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.22

    0.22

    For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.9 s

    2.9 s

    The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.183

    0.183

    The layout shifts by 0.183 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 17% slower for real visitors

    +17%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 136 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 27% faster for real visitors

    -27%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.8 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

5 to fix18
  • Page weight: 31.4 MB in 275 requests

    31.4 MB

    Your homepage downloads 31.4 MB in 275 requests on a phone: images 25.3 MB (68), scripts 5.6 MB (95) and stylesheets 252 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 22.0 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    20.3 MB

    9 images are downloaded at several times the size a phone draws them, for example Asia_0.jpg at 3,880 px wide, shown at 360 px. Resized copies would save about 20.3 MB.

  • 25 images in older formats

    25 images (23.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 14 images below the first screen load straight away

    14 images further down the page (22.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 8.9 g of CO₂ per visit

    8.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.90 g of CO₂e: 1067.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

10 to fixGoogle 8889
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (73 elements)

    All page content should be contained by landmarks: 73 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (5 elements)

    Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (11 elements).

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8370
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (92 characters)

    Your title is 92 characters, so Google will cut it off around 60: “Preferred Hotels & Resorts: The World's Best Independent Hotels | Preferred Hotels & Reso…”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 46 internal links, 1 external

    The homepage links to 46 pages on preferredhotels.com and 1 external page.

3 checks passed
  • One H1 headline

    Your main headline reads: “Luxury Travel Begins Here”.

  • 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://preferredhotels.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://preferredhotels.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 (1,725 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 3 pages share a title

    /, https://preferredhotels.com/hotels/switzerland/beausite-zermatt and https://preferredhotels.com/ipredirect all use the title “Preferred Hotels & Resorts: The World's Best Independent Hotels | Pre…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://preferredhotels.com/hotels/switzerland/beausite-zermatt and https://preferredhotels.com/ipredirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://preferredhotels.com/hotels/austria/das-edelweiss-salzburg-mountain-resort, https://preferredhotels.com/hotels/brazil/nannai-muro-alto, https://preferredhotels.com/hotels/colombia/ek-hotel, https://preferredhotels.com/hotels/france/hotel-dame-des-arts, https://preferredhotels.com/hotels/india/leela-palace-jaipur and https://preferredhotels.com/hotels/italy/corso-281 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://preferredhotels.com/hotels/austria/das-edelweiss-salzburg-mountain-resort, https://preferredhotels.com/hotels/brazil/nannai-muro-alto, https://preferredhotels.com/hotels/colombia/ek-hotel, https://preferredhotels.com/hotels/france/hotel-dame-des-arts, https://preferredhotels.com/hotels/india/leela-palace-jaipur and https://preferredhotels.com/hotels/italy/corso-281 and 8 others have 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

  • 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

3 to fix60
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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,698 words of copy

    The homepage carries about 1,698 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Reserve Your Stay”, “Book Your Next Travel Adventure” and “Join Today”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 14 other companies contacted

    Loading the homepage contacts 14 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 preferredhotels.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
Drupal
Framework
Next.js
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1968
Headquarters
Chicago

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on preferredhotels.com, including 16 speed issues, 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
preferredhotels.com website review: scores and fixes