Website review, no card needed
ohospitalitymanagement.com website review
Visit site (opens in a new tab)Reviewed 30 October 202628 issues · 101 checks
This review found 28 issues worth fixing on ohospitalitymanagement.com, 8 of them high impact, across 101 checks. The most urgent: improve image delivery. 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
87B- #5,434 of 80,558 reviewed websitesbeats 91%
- #2,812 of 39,621 online storesbeats 90%
- #5 of 934 Squarespace websitesbeats 99%
Closest competitors among online stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 93 ms |
| May 16, 2026 | 93 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 98 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 108 ms |
| Oct 24, 2026 | 108 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
ohospitalitymanagement.com does not allow embedding, so this is Google's rendering of the page.
Speed
Improve image delivery
6.5 s · 1.3 MB4 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.
Render-blocking requests
1.8 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 68
68/100Your mobile performance score is 68. 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 (Squarespace, Google Tag Manager and Facebook and others), adding 3.0 MB and 617 ms of main-thread time.
Reduce unused CSS
750 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Squarespace adds 419 ms
419 msSquarespace costs a phone 419 ms of main-thread work and 911 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.
Reduce unused JavaScript
475 KiBAbout 475 KiB of JavaScript is downloaded but never used on this page.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 1.6 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.
Legacy JavaScript
150 ms · 118 KiBPolyfills for old browsers add 118 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
105 KiB5 files are served with short cache lifetimes, so returning visitors download them again (105 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 492 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 93 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s 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.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: 94 ms
94 msReal visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 583 ms
583 msReal visitors wait 583 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
1 image over 500 KB
Shamrock+image+for+OHM+website.png weighs 659 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.1 MB in 75 requests
3.1 MBYour homepage downloads 3.1 MB in 75 requests on a phone: images 1.5 MB (8), scripts 1.2 MB (44) and fonts 172 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 2 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 (192 characters)
Your meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/615b5f60b9888e02d1a…”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
76 internal links, 8 external
The homepage links to 76 pages on ohospitalitymanagement.com and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “We do whatever it takes to make every guest smile!”.
Title: 61 characters
Your title is a healthy 61 characters: “Hospitality Management | O'Reilly Hospitality Management, LLC”.
Canonical URL set
The canonical URL is https://www.ohospitalitymanagement.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.ohospitalitymanagement.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, url, logo and description. 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 /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 (414 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
/restaurants has 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 25 found) and read each the way a search engine does.
6 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.
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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/615b5f60b9888e02d1adace2/65/5c5a…”.
2 checks passed
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
Short HSTS lifetime
HSTS is set, but max-age is 180 days; one year is the recommended minimum.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (ohospitalitymanagement.com).
Valid certificate (30 days left)
The certificate from Let's Encrypt · YR2 verifies for ohospitalitymanagement.com and is valid for another 30 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
http:// redirects to https
http://ohospitalitymanagement.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 29 links work
All 29 links checked from your homepage (27 internal, 2 external) answered without errors.
Domain and trust
No CAA record
ohospitalitymanagement.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
ohospitalitymanagement.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 17 years old
17 yearsohospitalitymanagement.com was registered in Jul 2009 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Registered until Jul 2027
ohospitalitymanagement.com is registered until Jul 2027.
Content and conversion
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 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 308 words of copy
The homepage carries about 308 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Contact Us” and “Learn More”.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
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.
Email authentication
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 80/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:us._netblocks.mimecast.com include:spf.protection.outlook.com -all”.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
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.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Analytics
- Google Analytics
- Hosting
- Squarespace
Company
- Employees
- 219
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on ohospitalitymanagement.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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.