outo.co website review

A phone's processor spends 8.4 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Clarity, Google Tag Manager and Shopify and others), adding 1.7 MB and 1.7 s of main-thread time.

About 726 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 54 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

About 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

Clarity costs a phone 685 ms of main-thread work and 30 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.

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

Shopify costs a phone 265 ms of main-thread work and 715 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.

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

2 images could be 196 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DSC_0679.jpg”.

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 382 requests on a phone: scripts 1.8 MB (98), other files 1.4 MB (257) and images 826 KiB (18). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

3 images have no alt text, which hurts accessibility and image search.

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

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“” and “越南泰國峇里島Outo 讓你說走就走”). One clear main headline is easier for people and search engines.

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 95 pages on outo.co and 5 external pages.

https://www.outo.co/collections/%E6%B5%B7%E5%A4%96%E8%A1%8C%E7%A8%8B%E5%8A%A0%E8%B3%BC%E9%A0%85%E7%9B%AE, https://www.outo.co/collections/10-%E4%BA%BA%E4%BB%A5%E4%B8%8A%E5%A4%A7%E5%9C%98 and https://www.outo.co/collections/%E5%B0%8F%E7%90%89%E7%90%83%E5%8A%A0%E8%B3%BC use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.outo.co/collections/%E6%B5%B7%E5%A4%96%E8%A1%8C%E7%A8%8B%E5%8A%A0%E8%B3%BC%E9%A0%85%E7%9B%AE, whose canonical is https://www.outo.co/collections/%e6%b5%b7%e5%a4%96%e8%a1%8c%e7%a8%8b%e5%8a%a0%e8%b3%bc%e9%a0%85%e7%9b%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.outo.co/collections/all-journeys has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.outo.co/pages/vietnam-travel, https://www.outo.co/pages/thailand-travel, https://www.outo.co/pages/bali-travel, https://www.outo.co/pages/family-friendly-travel, https://www.outo.co/pages/honeymoon-travel and https://www.outo.co/pages/group-travel and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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.

Opening the homepage sets 25 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.