Website review, no card needed
hotelbennett.com website review
Visit site (opens in a new tab)Reviewed 13 November 202629 issues · 86 checks
This review found 29 issues worth fixing on hotelbennett.com, 11 of them high impact, across 86 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 193 ms |
| May 30, 2026 | 193 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 201 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 201 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 198 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 130 ms |
| Oct 31, 2026 | 129 ms |
| Nov 7, 2026 | 125 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.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
4.0 s
4.6 s
Speed
Reduce unused JavaScript
1.4 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
audioeye.com adds 2.3 s
2.3 saudioeye.com costs a phone 2.3 s of main-thread work and 414 KiB 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.
Use efficient cache lifetimes
1.2 s · 933 KiB60 files are served with short cache lifetimes, so returning visitors download them again (933 KiB).
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 4.3 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 (audioeye.com, Google Tag Manager and Facebook and others), adding 2.3 MB and 3.6 s of main-thread time.
Improve image delivery
1.2 MB3 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 740 ms
740 msGoogle Tag Manager costs a phone 740 ms of main-thread work and 961 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.
Minify JavaScript
450 ms · 56 KiB56 KiB could be saved by minifying JavaScript.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Reduce unused CSS
22 KiBAbout 22 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: 150 ms
150 msYour server sent the HTML in 150 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.8 s
13.8 sYour largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.7 s
24.7 sThe page becomes fully interactive after 24.7 s. Good is under 3.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 508 ms
508 msScripts block taps and scrolling for 508 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
10 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 729 ms
729 msReal visitors wait 729 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 193 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 141 requests
5.0 MBYour homepage downloads 5.0 MB in 141 requests on a phone: scripts 2.4 MB (56), images 2.1 MB (12) and fonts 189 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
drew-castelhano-hotel-bennett-exterior-twilight-reedit-2-.jp weighs 1.1 MB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1,001 KiB3 images are downloaded at several times the size a phone draws them, for example drew-castelhano-hotel-bennett-exterior-twilight-reedit-2-.jp at 1,920 px wide, shown at 390 px. Resized copies would save about 1,001 KiB.
7 images in older formats
7 images (1.9 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.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 168.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Invalid ARIA attributes
6 elements use ARIA attributes their role does not allow, which confuses screen readers.
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.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 89 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
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
115 internal links, 17 external
The homepage links to 115 pages on hotelbennett.com and 17 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Charleston Roots Reimagined”.
Title: 55 characters
Your title is a healthy 55 characters: “Charleston Luxury Hotels | Hotel Bennett Charleston, SC”.
Canonical URL set
The canonical URL is https://www.hotelbennett.com/.
Structured data in place
Structured data found: Hotel.
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.hotelbennett.com/sitemap.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.hotelbennett.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,107 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.hotelbennett.com/rooms and https://www.hotelbennett.com/rooms/rooms all use the title “Hotel Rooms at Hotel Bennett - Deluxe Double Queen and King | Charles…”. 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://www.hotelbennett.com/welcome/destinations-by-lexus and https://www.hotelbennett.com/reservations have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.hotelbennett.com/rooms and https://www.hotelbennett.com/rooms/rooms use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hotelbennett.com/rooms, whose canonical is https://www.hotelbennett.com/rooms/rooms. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 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.
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
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 483 words of copy
The homepage carries about 483 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BOOK”.
40 calls to action
The homepage has 40 calls to action, for example “BOOK”, “Book” and “Book A Room”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
26 other companies contacted
Loading the homepage contacts 26 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 hotelbennett.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 24 open roles
- Job board
- adp
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on hotelbennett.com, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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.