Website review, no card needed

rlhco.com logo

rlhco.com website review

Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 81 checks

This review found 33 issues worth fixing on rlhco.com, 10 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
7.5 s2.5 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.6 s
May 16, 20265.9 s
May 23, 20266.2 s
May 30, 20266.5 s
Jun 6, 20266.8 s
Jun 13, 20266.9 s
Jun 20, 20266.7 s
Jun 27, 20266.3 s
Jul 4, 20265.3 s
Jul 11, 20264.0 s
Jul 18, 20263.5 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.4 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
494 ms299 msMay 9Oct 24321 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026412 ms
May 16, 2026431 ms
May 23, 2026443 ms
May 30, 2026459 ms
Jun 6, 2026471 ms
Jun 13, 2026470 ms
Jun 20, 2026454 ms
Jun 27, 2026431 ms
Jul 4, 2026396 ms
Jul 11, 2026369 ms
Jul 18, 2026359 ms
Jul 25, 2026354 ms
Aug 1, 2026354 ms
Aug 8, 2026355 ms
Aug 15, 2026362 ms
Aug 22, 2026366 ms
Aug 29, 2026372 ms
Sep 5, 2026377 ms
Sep 12, 2026376 ms
Sep 19, 2026374 ms
Sep 26, 2026366 ms
Oct 3, 2026359 ms
Oct 10, 2026345 ms
Oct 17, 2026331 ms
Oct 24, 2026321 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 rlhco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rlhco.com at 0.4 s0.4 s
  2. rlhco.com at 0.9 s0.9 s
  3. rlhco.com at 1.3 s1.3 s
  4. rlhco.com at 1.7 s1.7 s
  5. rlhco.com at 2.1 s2.1 s
  6. rlhco.com at 2.6 s2.6 s
  7. rlhco.com at 3.0 s3.0 s
  8. rlhco.com at 3.4 s3.4 s

Speed

7 to fix62
  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Osano CMP and Facebook and others), adding 1.1 MB and 892 ms of main-thread time.

  • Render-blocking requests

    850 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

  • Reduce unused JavaScript

    661 KiB

    About 661 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 378 ms

    378 ms

    Google Tag Manager costs a phone 378 ms of main-thread work and 542 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

    381 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (381 KiB).

  • Reduce unused CSS

    150 ms · 128 KiB

    About 128 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.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 239 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    75 KiB

    Polyfills for old browsers add 75 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    73 KiB

    3 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    10 KiB

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 132 ms

    132 ms

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

Core Web Vitals

6 to fix67
  • 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.

  • Time to Interactive: 35.4 s

    35.4 s

    The page becomes fully interactive after 35.4 s. Good is under 3.8 s.

  • Total Blocking Time: 1.3 s

    1.3 s

    Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user INP: 298 ms

    298 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 754 ms

    754 ms

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

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

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

    -44%

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Pave the way for adventure—and save—with our latest hotel o…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 5.7 MB in 229 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 229 requests on a phone: other files 3.0 MB (102), scripts 2.2 MB (72) and fonts 220 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    sih_tpmem_1600x500.webp 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.6 g of CO₂ per visit

    1.63 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.63 g of CO₂e: 195.2 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

6 to fixGoogle 9192
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 45 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: 45 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

3 to fixGoogle 8591
  • No structured data

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

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

  • 6 links with vague text

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

  • 78 internal links, 16 external

    The homepage links to 78 pages on rlhco.com and 16 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Book a hotel room among our global properties in the United States, Canada, Egypt, Peru, Columbia, Chile, Ecuador, and …”.

  • One H1 headline

    Your main headline reads: “Sonesta Hotels and Resorts”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Sonesta - Hotels, Resorts and Cruises”.

  • Canonical URL set

    The canonical URL is https://www.sonesta.com/.

  • 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.sonesta.com/sitemap/sitemap-index.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://www.sonesta.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,155 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix71
  • 15 pages without a title

    https://www.sonesta.com/our-brands, https://www.sonesta.com/offers, https://www.sonesta.com/manage-reservation, https://www.sonesta.com/support, https://www.sonesta.com/offers/members-always-save and https://www.sonesta.com/offers/advance-purchase-corporate-offer and 9 others have no <title>, so Google invents the link text in results.

  • 5 pages without a meta description

    https://www.sonesta.com/manage-reservation, https://www.sonesta.com/offers/members-always-save, https://www.sonesta.com/offers/advance-purchase-corporate-offer, https://www.sonesta.com/offers/long-term-stay and https://www.sonesta.com/egypt-hotels have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.sonesta.com/our-brands, https://www.sonesta.com/offers, https://www.sonesta.com/manage-reservation, https://www.sonesta.com/support, https://www.sonesta.com/offers/members-always-save and https://www.sonesta.com/offers/advance-purchase-corporate-offer and 9 others 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 51 found) and read each the way a search engine does.

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

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://www.sonesta.com/?showBanner=True.

  • 7 small tap targets

    7 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 trust badges. 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 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,047 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign In or Join” and “Book Now”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Sign In or Join”, “Book Now” and “Learn More”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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: Osano

    A consent management tool (Osano) 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 rlhco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Gatsby
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 rlhco.com, including 13 speed issues, 3 SEO 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

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