Website review, no card needed

sellsuki.co.th logo

sellsuki.co.th website review

Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 90 checks

This review found 42 issues worth fixing on sellsuki.co.th, 17 of them high impact, across 90 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
3.1 s2.0 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
327 ms111 msMay 2Oct 17217 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026302 ms
May 9, 2026281 ms
May 16, 2026254 ms
May 23, 2026288 ms
May 30, 2026296 ms
Jun 6, 2026284 ms
Jun 13, 2026254 ms
Jun 20, 2026189 ms
Jun 27, 2026163 ms
Jul 4, 2026163 ms
Jul 11, 2026160 ms
Jul 18, 2026166 ms
Jul 25, 2026152 ms
Aug 1, 2026136 ms
Aug 8, 2026141 ms
Aug 15, 2026141 ms
Aug 22, 2026155 ms
Aug 29, 2026201 ms
Sep 5, 2026208 ms
Sep 12, 2026206 ms
Sep 19, 2026202 ms
Sep 26, 2026182 ms
Oct 3, 2026181 ms
Oct 10, 2026204 ms
Oct 17, 2026217 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 sellsuki.co.th (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sellsuki.co.th at 4.4 s4.4 s
  2. sellsuki.co.th at 8.7 s8.7 s
  3. sellsuki.co.th at 13.1 s13.1 s
  4. sellsuki.co.th at 17.5 s17.5 s
  5. sellsuki.co.th at 21.9 s21.9 s
  6. sellsuki.co.th at 26.2 s26.2 s
  7. sellsuki.co.th at 30.6 s30.6 s
  8. sellsuki.co.th at 35.0 s35.0 s

Speed

16 to fix34
  • Reduce unused JavaScript

    4.0 s · 858 KiB

    About 858 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Use efficient cache lifetimes

    2.8 s · 857 KiB

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

  • Improve image delivery

    2.5 s · 974 KiB

    4 images could be 974 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Font display

    2.7 s

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

  • Facebook adds 1.5 s

    1.5 s

    Facebook costs a phone 1.5 s of main-thread work and 261 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.

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 860 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.

  • Main-thread work: 12.8 s

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

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. 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 (Facebook, Google Tag Manager and Clarity and others), adding 1.9 MB and 3.8 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    950 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 950 ms.

  • Legacy JavaScript

    700 ms · 94 KiB

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

  • Clarity adds 526 ms

    526 ms

    Clarity costs a phone 526 ms of main-thread work and 29 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,953 HTML elements

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

  • TikTok adds 250 ms

    250 ms

    TikTok costs a phone 250 ms of main-thread work and 157 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.

  • Amazon Web Services adds 13 ms

    13 ms

    Amazon Web Services costs a phone 13 ms of main-thread work and 576 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

    79 KiB

    About 79 KiB of CSS is downloaded but never applied on this page.

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

    436 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 32.4 s

    32.4 s

    Your largest element takes 32.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “More Than a Business Partner Drive Your Business Beyond Lim…”.

  • Speed Index: 21.0 s

    21.0 s

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

  • Time to Interactive: 37.1 s

    37.1 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • Real-user INP: 229 ms

    229 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 15 images without width and height

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

7 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 725 ms

    725 ms

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

  • Tap response (INP) got 28% faster for real visitors

    -28%

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

5 to fix28
  • Page weight: 24.0 MB in 297 requests

    24.0 MB

    Your homepage downloads 24.0 MB in 297 requests on a phone: images 19.6 MB (137), media 2.2 MB (3) and scripts 1.9 MB (50). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 14.4 MB together. On a phone connection a single image that size takes seconds.

  • 11 images in older formats

    11 images (1.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image far larger than shown

    479 KiB

    1 image is downloaded at several times the size a phone draws it, for example character-bot.1bb7c5b.png at 615 px wide, shown at 52 px. Resized copies would save about 479 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (739 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.8 g of CO₂ per visit

    6.81 g

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

Accessibility

3 to fixGoogle 9596
  • 2 text elements with low contrast

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

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

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

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 264 images in the HTML carry an alt attribute.

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

SEO

2 to fixGoogle 10088
  • Title is short (19 characters)

    Your title is only 19 characters: “หน้าหลัก | Sellsuki”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 15 H1 headlines

    There are 15 <h1> headlines (“นโยบายความเป็นส่วนตัวสำหรับลูกค้า”, “การเก็บรวบรวมข้อมูลส่วนบุคคล” and “ประเภทข้อมูลส่วนบุคคลที่เก็บรวบรวม”). One clear main headline is easier for people and search engines.

  • 58 internal links, 12 external

    The homepage links to 58 pages on sellsuki.co.th and 12 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Sellsuki บริการ Solution ครบวงจรสำหรับคนทำธุรกิจออนไลน์ โฆษณาออนไลน์ วางแผนคอนเทนต์ ออกแบบเว็บไซต์ และคลังสินค้าครบวงจร”.

  • Canonical URL set

    The canonical URL is https://www.sellsuki.co.th/en.

  • Structured data in place

    Structured data found: FAQPage, LocalBusiness, Organization 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.sellsuki.co.th/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.sellsuki.co.th/llms.txt (6 KiB, 30 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 9 pages share 2 titles

    https://www.sellsuki.co.th/en and / all use the title “หน้าหลัก | Sellsuki”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    /, https://www.sellsuki.co.th/en/solutions/akita, https://www.sellsuki.co.th/en/solutions/oc2plus, https://www.sellsuki.co.th/en/about-us and https://www.sellsuki.co.th/en/blog use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.sellsuki.co.th/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    /, https://www.sellsuki.co.th/en/solutions/wizemoves/martech, https://www.sellsuki.co.th/en/solutions/wizemoves, https://www.sellsuki.co.th/en/solutions/lineagency, https://www.sellsuki.co.th/solutions/wizemoves/martech and https://www.sellsuki.co.th/solutions/wizemoves and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.sellsuki.co.th/en/solutions/wizemoves/martech, https://www.sellsuki.co.th/en/solutions/lineagency, https://www.sellsuki.co.th/en/solutions/wizemoves/business-consulting, https://www.sellsuki.co.th/en/solutions/wizemoves/online-advertising, https://www.sellsuki.co.th/en/solutions/wizemoves/edis and https://www.sellsuki.co.th/solutions/wizemoves/martech and 1 other 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 to fixGoogle 9293
  • 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”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • 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 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 348 words of copy

    The homepage carries about 348 words of visible text.

8 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Join Us”.

  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 89 customer or partner logos and 20 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 20 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Nuxt
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 42 issues on sellsuki.co.th, including 24 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

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