Website review, no card needed

ambassatours.com logo

ambassatours.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 95 checks

This review found 43 issues worth fixing on ambassatours.com, 15 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s2.0 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
134 ms108 msMay 2Oct 17129 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026120 ms
May 9, 2026120 ms
May 16, 2026116 ms
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026116 ms
Jul 4, 2026116 ms
Jul 11, 2026118 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026121 ms
Aug 15, 2026125 ms
Aug 22, 2026128 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026129 ms
Sep 19, 2026129 ms
Sep 26, 2026130 ms
Oct 3, 2026129 ms
Oct 10, 2026131 ms
Oct 17, 2026129 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

Full-page screenshot of ambassatours.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ambassatours.com at 0.6 s0.6 s
  2. ambassatours.com at 1.2 s1.2 s
  3. ambassatours.com at 1.8 s1.8 s
  4. ambassatours.com at 2.5 s2.5 s
  5. ambassatours.com at 3.1 s3.1 s
  6. ambassatours.com at 3.7 s3.7 s
  7. ambassatours.com at 4.3 s4.3 s
  8. ambassatours.com at 4.9 s4.9 s

Speed

14 to fix35
  • Reduce unused JavaScript

    10.2 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.2 s faster on a phone.

  • Render-blocking requests

    7.5 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.

  • Use efficient cache lifetimes

    2.5 s · 861 KiB

    28 files are served with short cache lifetimes, so returning visitors download them again (861 KiB).

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 72). 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.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,260 HTML elements

    The page has 3,260 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and website-files.com and others), adding 18.2 MB and 1.7 s of main-thread time.

  • Vimeo adds 261 ms

    261 ms

    Vimeo costs a phone 261 ms of main-thread work and 12.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.

  • Reduce unused CSS

    750 ms · 161 KiB

    About 161 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.

  • website-files.com adds 270 ms

    270 ms

    website-files.com costs a phone 270 ms of main-thread work and 3.5 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.

  • Google Tag Manager adds 462 ms

    462 ms

    Google Tag Manager costs a phone 462 ms of main-thread work and 579 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.

  • Facebook adds 295 ms

    295 ms

    Facebook costs a phone 295 ms of main-thread work and 251 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 302 ms. During a long task the page ignores taps.

  • awswaf.com adds 149 ms

    149 ms

    awswaf.com costs a phone 149 ms of main-thread work and 406 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

    200 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Improve image delivery

    45 KiB

    2 images could be 45 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    20 KiB

    20 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 72 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.

  • First Contentful Paint: 13.6 s

    13.6 s

    The first text or image appears after 13.6 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 31.5 s

    31.5 s

    Your largest element takes 31.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “It's Better on the Water”.

  • Time to Interactive: 34.4 s

    34.4 s

    The page becomes fully interactive after 34.4 s. Good is under 3.8 s.

  • Speed Index: 13.6 s

    13.6 s

    Visually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 868 ms

    868 ms

    Scripts block taps and scrolling for 868 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.6 s

    2.6 s

    Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 120 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 132 ms

    132 ms

    Real visitors wait 132 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 362 ms

    362 ms

    Real visitors wait 362 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.038

    0.038

    The layout barely moves while loading (CLS 0.038, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 19.5 MB in 188 requests

    19.5 MB

    Your homepage downloads 19.5 MB in 188 requests on a phone: other files 11.9 MB (58), scripts 3.5 MB (34) and images 3.2 MB (53). Under 2 MB keeps phones on slow connections fast.

  • About 5.5 g of CO₂ per visit

    5.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.52 g of CO₂e: 661.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

6 to fixGoogle 8992
  • 42 text elements with low contrast

    42 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (24 elements)

    All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 349 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9282
  • 97 links with vague text

    97 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Title is long (93 characters)

    Your title is 93 characters, so Google will cut it off around 60: “Halifax Harbour Tours | Harbour Hopper Tours, Sailing, Private Charters & More | Ambassat…”.

  • 77 H1 headlines

    There are 77 <h1> headlines (“It's Better on the Water”, “Harbour Hopper Tours: Halifax” and “Harbour Hopper Tours: Charlottetown”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("/")”.

  • 183 internal links, 105 external

    The homepage links to 183 pages on ambassatours.com and 105 external pages.

5 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Discover Halifax's top boat tours, sailing cruises, walking tours & party cruises. Harbour Hopper, Tall Ship Silva, Peg…”.

  • Canonical URL set

    The canonical URL is https://www.ambassatours.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.ambassatours.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.ambassatours.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 (4,777 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 66 found) and read each the way a search engine does.

7 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.

  • 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

3 to fixGoogle 5888
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 1,123 words of copy

    The homepage carries about 1,123 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN OUR CREW” and “CONTACT https://www.ambassatours.com/SUBSCRIBE”.

  • 199 calls to action

    The homepage has 199 calls to action, for example “JOIN OUR CREW”, “CONTACT https://www.ambassatours.com/SUBSCRIBE” and “Online Shop”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 2 of them by other companies (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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 ambassatours.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
Webflow
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on ambassatours.com, including 23 speed issues, 4 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25