Website review, no card needed
opendestinations.com website review
Visit site (opens in a new tab)Reviewed 9 November 202619 issues · 71 checks
This review found 19 issues worth fixing on opendestinations.com, 9 of them high impact, across 71 checks. The most urgent: render-blocking requests. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 7.8 s |
| May 30, 2026 | 8.2 s |
| Jun 6, 2026 | 7.9 s |
| Jun 13, 2026 | 7.9 s |
| Jun 20, 2026 | 8.4 s |
| Jun 27, 2026 | 8.5 s |
| Jul 4, 2026 | 8.9 s |
| Jul 11, 2026 | 8.8 s |
| Jul 18, 2026 | 8.2 s |
| Jul 25, 2026 | 7.7 s |
| Aug 1, 2026 | 7.5 s |
| Aug 8, 2026 | 7.2 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 7.7 s |
| Aug 29, 2026 | 7.8 s |
| Sep 5, 2026 | 7.8 s |
| Sep 12, 2026 | 7.9 s |
| Sep 19, 2026 | 7.7 s |
| Sep 26, 2026 | 8.0 s |
| Oct 3, 2026 | 7.8 s |
| Oct 10, 2026 | 7.8 s |
| Oct 17, 2026 | 8.0 s |
| Oct 24, 2026 | 7.8 s |
| Oct 31, 2026 | 8.0 s |
| Nov 7, 2026 | 7.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 158 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 209 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 182 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 193 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 2026 | 214 ms |
| Nov 7, 2026 | 187 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
1.6 s
3.1 s
4.7 s
6.2 s
7.8 s
9.3 s
10.9 s
12.4 s
Speed
Render-blocking requests
12.1 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.1 s.
Use efficient cache lifetimes
1.7 s · 391 KiB63 files are served with short cache lifetimes, so returning visitors download them again (391 KiB).
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Hubspot and Google/Doubleclick Ads and others), adding 314 KiB and 260 ms of main-thread time.
Reduce unused JavaScript
172 KiBAbout 172 KiB of JavaScript is downloaded but never used on this page.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 143 ms. During a long task the page ignores taps.
Improve image delivery
6 KiB1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 736 ms of it running JavaScript. That is comfortably low.
Server response: 434 ms
434 msYour server sent the HTML in 434 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: 8.7 s
8.7 sReal visitors wait 8.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.8 s
6.8 sReal visitors see the first content after 6.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.3 s
5.3 sReal visitors wait 5.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 19.1 s
19.1 sVisually, the page fills in at 19.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 215 ms
215 msReal visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 158 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 5.2 s
5.2 sThe page becomes fully interactive after 5.2 s. Good is under 3.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Open Destinations”. Most of its time is resource load delay (9.0 s).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 7.8 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 96 ms
96 msScripts block the page for only 96 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Images and page weight
About 0.2 g of CO₂ per visit
0.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.23 g of CO₂e: 27.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 816 KiB in 76 requests
816 KiBYour homepage downloads 816 KiB in 76 requests on a phone: scripts 537 KiB (26), images 165 KiB (17) and stylesheets 50 KiB (26). That is a lean page.
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 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (29 characters)
Your title is only 29 characters: “Home Page - Open Destinations”. Between 30 and 65 characters leaves room to say what you do and for whom.
63 internal links, 0 external
The homepage links to 63 pages on opendestinations.com and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “SaaS travel technology for Tour Operators, DMCs & Rail Companies managing complex, multi-day travel”.
Canonical URL set
The canonical URL is https://www.opendestinations.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://www.opendestinations.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.opendestinations.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.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,252 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.opendestinations.com/partners-and-supplier-integrations, https://www.opendestinations.com/ai-product-assistant, https://www.opendestinations.com/business-support-services, https://www.opendestinations.com/news-and-insights and https://www.opendestinations.com/about have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.opendestinations.com/destination-management-companies and https://www.opendestinations.com/rail-companies use the same meta description. A description written for each page earns more clicks.
10 pages slow to respond
https://www.opendestinations.com/mobile-apps, https://www.opendestinations.com/rail-studio, https://www.opendestinations.com/ai-product-assistant, https://www.opendestinations.com/financial-administration-and-support, https://www.opendestinations.com/contract-management-and-product-loading and https://www.opendestinations.com/customer-services and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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.
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
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,047 words of copy
The homepage carries about 1,047 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: “Talk to an Expert ➔”.
5 calls to action
The homepage has 5 calls to action, for example “Get in touch”, “Talk to an Expert ➔” and “Talk to an expert ➔”.
Social proof on the page
Social proof on the homepage: 15 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 6 of them by other companies (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: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 opendestinations.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
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on opendestinations.com, including 12 speed issues, 2 SEO issues and 1 conversion gap. 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.