Website review, no card needed
hotelengine.com website review
Visit site (opens in a new tab)Reviewed 4 November 202620 issues · 76 checks
This review found 20 issues worth fixing on hotelengine.com, 4 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Engine
- Homepage
- Phone render
- Links and pages
- 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.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 173 ms |
| May 23, 2026 | 168 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 180 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 175 ms |
| Aug 1, 2026 | 173 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 176 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 207 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 236 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 246 ms |
| Oct 24, 2026 | 243 ms |
| Oct 31, 2026 | 238 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user INP: 236 ms
236 msReal visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 173 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 3.7 MB
3.7 MBYour homepage downloads 3.7 MB on a phone, 552 KiB of it images (15%). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
113 KiB1 image is downloaded at several times the size a phone draws it, for example Engine_Icon_Black.png at 3,760 px wide, shown at 45 px. Resized copies would save about 113 KiB.
2 images in older formats
2 images (390 KiB) 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.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 125.0 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
Images must have alternative text (2 elements)
Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.
15 text elements with low contrast
15 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
38 links without text
38 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 2 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 (183 characters)
Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization, Service, SoftwareApplication and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("/images/66ecd535db1cc991480219ea_graph-image.png")”.
144 internal links, 16 external
The homepage links to 144 pages on hotelengine.com and 16 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Travel and spend for teams and agents.”.
Title: 59 characters
Your title is a healthy 59 characters: “Engine | All-in-One Travel Management Software for Business”.
Canonical URL set
The canonical URL is https://engine.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://engine.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,144 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (10 KiB, 56 links), a plain-text guide to the site for AI tools.
Other pages
5 linked pages hidden from search
/platform/product, /platform/product/travel-programs, /platform/product/group-room-blocks, /platform/product/event-planning and /platform/product/meeting-spaces are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=56349180&tm=gtm002&Ver=2&mid=726e1435-8d2d-416b-9cb1-5d2dbf887726&bo=1&sid=a0b0c4a0d83011f1a2da5dfc07f8d4b0&vid=a0b0c8e0d83011f1bf196de407f647d8&vids=1&msclkid=N&pi=91.
39 small tap targets
39 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 180 days; one year is the recommended minimum.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (engine.com).
Valid certificate (68 days left)
The certificate from Google Trust Services · WE1 verifies for hotelengine.com and is valid for another 68 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://hotelengine.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 49 links work
All 49 links checked from your homepage (40 internal, 9 external) answered without errors.
Domain and trust
4 checks passed
Domain is 32 years old
32 yearsengine.com was registered in May 1994 through Cloudflare, Inc.. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only letsencrypt.org, godaddy.com, digicert.com and pki.goog to issue certificates for engine.com, so a mis-issued certificate from anyone else is refused.
DNSSEC is on
engine.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.
Registered until May 2031
engine.com is registered until May 2031.
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 876 words of copy
The homepage carries about 876 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join free” and “Book a demo”.
16 calls to action
The homepage has 16 calls to action, for example “Pricing”, “Join free” and “Book a demo”.
Social proof on the page
Social proof on the homepage: 25 customer or partner logos, a star rating and “40,000+ businesses”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
Email authentication score: 100/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.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject 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:_spf.salesforce.com include:sendgrid.net include:amazonses.com include:7770829.spf08.hubspotemail.net i…”.
DKIM signing found
A DKIM key is published (selector “google”, “selector1” and “k1”), so receivers can verify mail really came from you.
Privacy and tracking
12 trackers load before any consent
12Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 7 mores (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.
41 cookies set on arrival
41Opening the homepage sets 41 cookies (measured from a US location before any click).
63 other companies contacted
Loading the homepage contacts 63 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.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- Webflow
- Framework
- Astro
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Hiring
- Hiring
- 76 open roles
- Teams
- Outbound (13), Growth (8), Engineering (7), Expansion (4)
- Job board
- greenhouse
- Careers page
- engine.com/platform/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on hotelengine.com, including 5 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.