Website review, no card needed

thetigerhotel.com logo

thetigerhotel.com website review

Visit site (opens in a new tab)Reviewed 21 October 202626 issues · 80 checks

This review found 26 issues worth fixing on thetigerhotel.com, 7 of them high impact, across 80 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s752 msMay 2Oct 17989 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.1 s
May 16, 20261.6 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 2026957 ms
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 2026988 ms
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026989 ms
Real-visitor tap response (INP)75th percentile, phones
90 ms75 msMay 2Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202686 ms
May 9, 202686 ms
May 16, 202679 ms
May 23, 202677 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202686 ms
Jun 20, 202685 ms
Jun 27, 202678 ms
Jul 4, 202679 ms
Jul 11, 202677 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202677 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202680 ms
Sep 5, 202680 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202688 ms
Oct 10, 202680 ms
Oct 17, 202680 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 thetigerhotel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thetigerhotel.com at 0.6 s0.6 s
  2. thetigerhotel.com at 1.2 s1.2 s
  3. thetigerhotel.com at 1.7 s1.7 s
  4. thetigerhotel.com at 2.3 s2.3 s
  5. thetigerhotel.com at 2.9 s2.9 s
  6. thetigerhotel.com at 3.5 s3.5 s
  7. thetigerhotel.com at 4.1 s4.1 s
  8. thetigerhotel.com at 4.6 s4.6 s

Speed

8 to fix48
  • Render-blocking requests

    4.9 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.9 s.

  • Reduce unused JavaScript

    2.0 s · 423 KiB

    About 423 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 86). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    850 ms · 116 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google Tag Manager and termly.io and others), adding 2.9 MB and 620 ms of main-thread time.

  • website-files.com adds 381 ms

    381 ms

    website-files.com costs a phone 381 ms of main-thread work and 2.1 MB 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.

  • Reduce unused CSS

    300 ms · 34 KiB

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

  • Google Tag Manager adds 89 ms

    89 ms

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

  • 9 long tasks on the main thread

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

  • Improve image delivery

    17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 86 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    A phone's processor spends 1.8 s on main-thread work while loading, 941 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.3 s

    14.3 s

    Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1 of 6”.

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 387 ms

    387 ms

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

  • 6 images without width and height

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

  • 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 86 ms to 80 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: 1.4 s

    1.4 s

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

  • Real-user INP: 85 ms

    85 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 379 ms

    379 ms

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

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

    -55%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.3 MB in 68 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 68 requests on a phone: images 1.5 MB (17), scripts 1.2 MB (15) and fonts 523 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6425cdac136709059d05a948_voco-tiger-logo-blk-landscape-black 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 0.9 g of CO₂ per visit

    0.93 g

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

Google 100100
2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 10082
  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Upscale modern meets historic architecture”, “What's Happening” and “Sleep, eat & everything in between”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Meta description is long (230 characters)

    Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 19 internal links, 10 external

    The homepage links to 19 pages on thetigerhotel.com and 10 external pages.

4 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “voco™ The Tiger Hotel - Columbia, Missouri”.

  • 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.thetigerhotel.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://www.thetigerhotel.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 (353 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages without a meta description

    https://www.thetigerhotel.com/event/arrive-early and https://www.thetigerhotel.com/terms-of-use have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.thetigerhotel.com/who-we-are, https://www.thetigerhotel.com/highlights, https://www.thetigerhotel.com/rooms, https://www.thetigerhotel.com/eat-and-drink/eat-and-drink, https://www.thetigerhotel.com/eat-and-drink/glenns-cafe and https://www.thetigerhotel.com/eat-and-drink/twain and 2 others use the same meta description. A description written for each page earns more clicks.

  • 9 pages with very little text

    https://www.thetigerhotel.com/who-we-are, https://www.thetigerhotel.com/eat-and-drink/eat-and-drink, https://www.thetigerhotel.com/eat-and-drink/vault, https://www.thetigerhotel.com/eat-and-drink/wilder, https://www.thetigerhotel.com/event-services/book-an-event and https://www.thetigerhotel.com/contact and 3 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.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 14 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 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 9 small tap targets

    9 of 21 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

2 to fix83
  • 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.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 276 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: “BOOK NOW” and “Join Our Team”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “BOOK NOW” and “Join Our Team”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) 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).

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 thetigerhotel.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
Webflow
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on thetigerhotel.com, including 14 speed issues, 4 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