Website review, no card needed
acehotel.com website review
Visit site (opens in a new tab)Reviewed 18 October 202632 issues · 83 checks
This review found 32 issues worth fixing on acehotel.com, 14 of them high impact, across 83 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.3 s |
| May 2, 2026 | 3.2 s |
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 139 ms |
| May 2, 2026 | 143 ms |
| May 9, 2026 | 144 ms |
| May 16, 2026 | 148 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 199 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 240 ms |
| Sep 26, 2026 | 254 ms |
| Oct 3, 2026 | 270 ms |
| Oct 10, 2026 | 285 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
Reduce unused JavaScript
1.9 s · 883 KiBAbout 883 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Google Tag Manager adds 1.8 s
1.8 sGoogle Tag Manager costs a phone 1.8 s of main-thread work and 1.5 MB 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.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.4 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 (Google Tag Manager, WordPress and Bing Ads and others), adding 3.9 MB and 2.2 s of main-thread time.
Improve image delivery
946 KiB11 images could be 946 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
WordPress adds 308 ms
308 msWordPress costs a phone 308 ms of main-thread work and 2.3 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 315 ms. During a long task the page ignores taps.
1,924 HTML elements
The page has 1,924 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
64 KiBAbout 64 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.
Use efficient cache lifetimes
1 KiB2 files are served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 221 ms
221 msReal visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 97% slower for real visitors
+97%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 139 ms to 285 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 129 requests
4.4 MBYour homepage downloads 4.4 MB in 129 requests on a phone: images 2.2 MB (62), scripts 1.9 MB (25) and stylesheets 84 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 149.3 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
ARIA attributes must conform to valid values (8 elements)
ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
30 elements hidden from screen readers can still receive keyboard focus.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 84 images in the HTML carry an alt attribute.
47 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: 47 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
21 links with vague text
21 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
236 internal links, 18 external
The homepage links to 236 pages on acehotel.com and 18 external pages.
8 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Stylish & unique lifestyle hotels in Sydney, New York, Brooklyn, Palm Springs, Seattle, Kyoto, Toronto, and Athens. Boo…”.
One H1 headline
Your main headline reads: “Welcome toAce Hotel”.
Title: 62 characters
Your title is a healthy 62 characters: “Ace Hotel | Hotels in North America, Japan, Australia & Greece”.
Canonical URL set
The canonical URL is https://acehotel.com/.
Structured data in place
Structured data found: Brand, Hotel, ItemList, Organization and Resort.
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://acehotel.com/sitemap_index.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (5,141 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://acehotel.com/llms.txt (2 KiB, 12 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://acehotel.com/eat-drink is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://acehotel.com/private-spaces/meetings-events has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.
5 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.
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 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Manifest: Line: 1, column: 1, Syntax error.”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
48 of 51 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,824 words of copy
The homepage carries about 1,824 words of visible text.
8 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Book Now”, “Shop - Link opens in new tab” and “Contact”.
3 short forms
3 short forms (7 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 77 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Opening hours shown
Your opening hours are 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.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 acehotel.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
- WordPress
- Analytics
- Google Tag Manager
Company
- Founded
- 1999
- Headquarters
- Portland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on acehotel.com, including 21 speed issues, 1 SEO issue 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.