Website review, no card needed
uncruise.com website review
Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 89 checks
This review found 37 issues worth fixing on uncruise.com, 14 of them high impact, across 89 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
83B- #21,275 of 92,694 reviewed websitesbeats 72%
- #13,278 of 49,311 online storesbeats 67%
- #12,840 of 44,484 Shopify storesbeats 64%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 102 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 126 ms |
| Oct 31, 2026 | 124 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
Improve image delivery
4.7 s · 3.8 MB22 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.
Reduce unused JavaScript
2.5 s · 923 KiBAbout 923 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.9 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, Clarity and tidio.co and others), adding 2.3 MB and 1.2 s of main-thread time.
Google Tag Manager adds 753 ms
753 msGoogle Tag Manager costs a phone 753 ms of main-thread work and 1.2 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.
Use efficient cache lifetimes
500 ms · 85 KiB23 files are served with short cache lifetimes, so returning visitors download them again (85 KiB).
Render-blocking requests
350 ms18 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 306 ms. During a long task the page ignores taps.
2,971 HTML elements
The page has 2,971 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
tidio.co adds 85 ms
85 mstidio.co costs a phone 85 ms of main-thread work and 515 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.
Legacy JavaScript
250 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
11 KiBAbout 11 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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 32.1 s
32.1 sYour largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MEET YOUR FLOATING BASECAMP-UnCruise Adventures”.
Time to Interactive: 32.7 s
32.7 sThe page becomes fully interactive after 32.7 s. Good is under 3.8 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 102 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 487 ms
487 msScripts block taps and scrolling for 487 ms in total while the page loads. Good is under 200 ms.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, 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).
7 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 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: 464 ms
464 msReal visitors wait 464 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.8 MB in 367 requests
23.8 MBYour homepage downloads 23.8 MB in 367 requests on a phone: media 13.2 MB (3), images 6.6 MB (42) and scripts 2.5 MB (114). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Kayaking_in_Costa_Rica_2.jpg weighs 847 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.2 MB5 images are downloaded at several times the size a phone draws them, for example Kayaking_in_Costa_Rica_2.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 1.2 MB.
2 images in older formats
2 images (897 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 6.7 g of CO₂ per visit
6.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.75 g of CO₂e: 809.6 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
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h2 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
271 internal links, 26 external
The homepage links to 271 pages on uncruise.com and 26 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “All-inclusive small ship cruises with just 22 to 86 guests. Explore Alaska, Hawaii, Mexico, Costa Rica, and the Galapag…”.
Title: 54 characters
Your title is a healthy 54 characters: “UnCruise Adventures | Award Winning Small Ship Cruises”.
Canonical URL set
The canonical URL is https://uncruise.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://uncruise.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 (8,645 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://uncruise.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://uncruise.com/collections/all, https://uncruise.com/pages/combo-packages and https://uncruise.com/pages/cruise-specials have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://uncruise.com/collections/all, https://uncruise.com/blogs/baja/why-the-sea-of-cortez-is-called-the-worlds-aquarium, https://uncruise.com/pages/about-us, https://uncruise.com/collections/alaska-adventure-cruises, https://uncruise.com/collections/hawaii-adventure-cruises and https://uncruise.com/collections/mexico-adventure-cruises and 9 others have 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 75 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.
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
5 broken images
5 images failed to load on a phone, for example https://aimcmgpixel.myaudiences.app/dot/c728dbf4-82ee-4ee8-a190-07c0ecb40d32?cbust=744645935433666.9&url_path=https%3A%2F%2Funcruise.com%2F.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
41 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
Thin social proof
Social proof on the homepage: 44 testimonial or review blocks. 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.
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 7,282 words of copy
The homepage carries about 7,282 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Us” and “Request Info”.
24 calls to action
The homepage has 24 calls to action, for example “Call Us”, “Contact Us” and “Gift Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 2 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (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.
51 other companies contacted
Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 uncruise.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Teams
- Engineering (2), Deck (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on uncruise.com, including 18 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.