Website review, no card needed

relaxingthai.com logo

relaxingthai.com website review

Visit site (opens in a new tab)Reviewed 12 November 202625 issues · 72 checks

This review found 25 issues worth fixing on relaxingthai.com, 5 of them high impact, across 72 checks. The most urgent: main-thread work: 4.4 s. 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

Full-page screenshot of relaxingthai.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. relaxingthai.com at 0.4 s0.4 s
  2. relaxingthai.com at 0.8 s0.8 s
  3. relaxingthai.com at 1.1 s1.1 s
  4. relaxingthai.com at 1.5 s1.5 s
  5. relaxingthai.com at 1.9 s1.9 s
  6. relaxingthai.com at 2.3 s2.3 s
  7. relaxingthai.com at 2.6 s2.6 s
  8. relaxingthai.com at 3.0 s3.0 s

Speed

6 to fix88
  • Main-thread work: 4.4 s

    A phone's processor spends 4.4 s on main-thread work while loading, 2.1 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 (chatra.io, avada.io and Clarity and others), adding 1,017 KiB and 1.2 s of main-thread time.

  • Mobile performance score: 88

    88/100

    Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

  • chatra.io adds 679 ms

    679 ms

    chatra.io costs a phone 679 ms of main-thread work and 395 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.

  • Render-blocking requests

    650 ms

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

  • avada.io adds 235 ms

    235 ms

    avada.io costs a phone 235 ms of main-thread work and 317 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.

  • Reduce unused CSS

    150 ms · 199 KiB

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

  • 8 long tasks on the main thread

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

  • Reduce unused JavaScript

    202 KiB

    About 202 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    45 KiB

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

  • Use efficient cache lifetimes

    28 KiB

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

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

    42 ms

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

Core Web Vitals

4 to fix88
  • Time to Interactive: 11.3 s

    11.3 s

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

  • Total Blocking Time: 316 ms

    316 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your 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 text “Thai Herbal Inhaler & YA-DOM – Freshness On the Go”. Most of its time is element render delay (1.1 s).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 362 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 362 requests on a phone: other files 1.2 MB (261), scripts 888 KiB (65) and images 130 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.68 g

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

1 to fixGoogle 9798
  • 17 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 35 internal links, 6 external

    The homepage links to 35 pages on relaxingthai.com and 6 external pages.

8 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Handmade Thai herbal inhalers from Austria: Relaxing Thai jar and YA-DOM stick. Natural aromas for freshness and focus …”.

  • One H1 headline

    Your main headline reads: “Thai Herbal Inhaler & YA-DOM – Freshness On the Go”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Thai Herbal Inhaler & YA-DOM Nasal Stick – Relaxing Thai”.

  • Canonical URL set

    The canonical URL is https://www.relaxingthai.com/en.

  • Structured data in place

    Structured data found: Organization, Review 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.relaxingthai.com/sitemap.xml.

AI search readiness

100
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, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (792 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.relaxingthai.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.relaxingthai.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.relaxingthai.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.relaxingthai.com/en/pages/kontakt-1, https://www.relaxingthai.com/customer_authentication/redirect, https://www.relaxingthai.com/en/policies/refund-policy, https://www.relaxingthai.com/en/policies/privacy-policy, https://www.relaxingthai.com/en/policies/terms-of-service and https://www.relaxingthai.com/en/policies/shipping-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.relaxingthai.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.relaxingthai.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.relaxingthai.com/cdn/shop/t/3/assets/tiny.content.min.css?v=427' because its M…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • 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 716 words of copy

    The homepage carries about 716 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Online shop”, “Where to buy?” and “Contact”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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

    14

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 relaxingthai.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Avada Cookie Consent · Hulk Form Builder · Chatra Live Chat Chatbot · Microsoft Clarity · Air Reviews

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on relaxingthai.com, including 10 speed issues, 1 SEO issue and 5 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