Website review, no card needed
jungsaemmool-th.com website review
Visit site (opens in a new tab)Reviewed 11 November 202641 issues · 89 checks
This review found 41 issues worth fixing on jungsaemmool-th.com, 15 of them high impact, across 89 checks. The most urgent: shopify adds 1.6 s. 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
77C- #61,211 of 108,869 reviewed websitesbeats 39%
- #39,746 of 61,767 online storesbeats 31%
- #37,869 of 56,365 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 122 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 151 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 157 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 154 ms |
| Nov 7, 2026 | 151 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.7 s
3.3 s
5.0 s
6.7 s
8.4 s
10.0 s
11.7 s
13.4 s
Speed
Shopify adds 1.6 s
1.6 sShopify costs a phone 1.6 s of main-thread work and 566 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.3 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.2 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
450 ms · 380 KiBAbout 380 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
600 ms · 96 KiBAbout 96 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.
Google Tag Manager adds 310 ms
310 msGoogle Tag Manager costs a phone 310 ms of main-thread work and 304 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,742 HTML elements
The page has 2,742 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
124 KiB17 files are served with short cache lifetimes, so returning visitors download them again (124 KiB).
Improve image delivery
82 KiB6 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
15 KiB15 KiB JavaScript is shipped twice across bundles.
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: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 611 ms
611 msScripts block taps and scrolling for 611 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 122 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
8 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 478 ms
478 msReal visitors wait 478 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 12.1 MB in 422 requests
12.1 MBYour homepage downloads 12.1 MB in 422 requests on a phone: media 8.2 MB (2), other files 1.4 MB (268) and scripts 1.2 MB (76). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mobile-JSM-720x900px4_a7a2e20e-9415-407f-80b1-7ae3d024f6b0.j is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.4 g of CO₂ per visit
3.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.43 g of CO₂e: 411.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “JUNGSAEMMOOL Official Thailand Store | Professional beauty – JUNG SAEM MOOL Beauty Thaila…”.
4 H1 headlines
There are 4 <h1> headlines (“”, “” and “ลงชื่อเข้าใช้”). One clear main headline is easier for people and search engines.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
151 internal links, 17 external
The homepage links to 151 pages on jungsaemmool-th.com and 17 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://jungsaemmool-th.com/.
Structured data in place
Structured data found: Organization.
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://jungsaemmool-th.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
llms.txt published
The site publishes https://jungsaemmool-th.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a meta description
https://jungsaemmool-th.com/pages/review-and-referral, https://jungsaemmool-th.com/collections/jungsaemmool, https://jungsaemmool-th.com/collections/base-makeup, https://jungsaemmool-th.com/collections/tools-accessories and https://jungsaemmool-th.com/collections/bestsellers use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://jungsaemmool-th.com/pages/review-and-referral, https://jungsaemmool-th.com/collections/jungsaemmool, https://jungsaemmool-th.com/collections/skincare-1, https://jungsaemmool-th.com/collections/base-makeup, https://jungsaemmool-th.com/collections/eye-makeup and https://jungsaemmool-th.com/collections/lip-makeup and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://jungsaemmool-th.com/products/jungsaemmool-masterclass-radiant-cushion-8800332432829, https://jungsaemmool-th.com/products/jungsaemmool-masterclass-powder-foundation-8800332432904 and https://jungsaemmool-th.com/products/jungsaemmool-artist-eyelash-black-serum-8809826712683 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.
7 pages slow to respond
https://jungsaemmool-th.com/collections/tools-accessories, https://jungsaemmool-th.com/collections/bestsellers, https://jungsaemmool-th.com/products/jungsaemmool-masterclass-radiant-cushion-8800332432829, https://jungsaemmool-th.com/products/jungsaemmool-masterclass-powder-foundation-8800332432904, https://jungsaemmool-th.com/products/jungsaemmool-skin-nuder-foundation-8809467636270 and https://jungsaemmool-th.com/products/jungsaemmool-essential-mool-cream-light-8809467637994 and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 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.
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
61 of 63 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 123 words
The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
19 short forms
19 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 5 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.
40 other companies contacted
Loading the homepage contacts 40 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 jungsaemmool-th.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Judge Me Reviews · Pagefly Ai Page Builder · Littledata The Data Layer · Oxi Social Login Wishlist · Twilio Segment By Littledata · Microsoft Clarity · Langify · Swym Wishlist Plus
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar | Segment | 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 41 issues on jungsaemmool-th.com, including 17 speed issues, 4 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.