Website review, no card needed

sneakbast.com logo

sneakbast.com website review

Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 76 checks

This review found 33 issues worth fixing on sneakbast.com, 7 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
1.5 s1.2 sAug 22Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
138 ms103 msAug 22Oct 31134 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026107 ms
Aug 29, 2026112 ms
Sep 5, 2026115 ms
Sep 12, 2026118 ms
Sep 19, 2026126 ms
Sep 26, 2026130 ms
Oct 3, 2026132 ms
Oct 10, 2026133 ms
Oct 17, 2026134 ms
Oct 24, 2026133 ms
Oct 31, 2026134 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 sneakbast.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sneakbast.com at 0.6 s0.6 s
  2. sneakbast.com at 1.2 s1.2 s
  3. sneakbast.com at 1.8 s1.8 s
  4. sneakbast.com at 2.4 s2.4 s
  5. sneakbast.com at 3.0 s3.0 s
  6. sneakbast.com at 3.6 s3.6 s
  7. sneakbast.com at 4.2 s4.2 s
  8. sneakbast.com at 4.8 s4.8 s

Speed

6 to fix80
  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    850 ms

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

  • Reduce unused JavaScript

    500 ms · 96 KiB

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

  • Improve image delivery

    300 ms · 209 KiB

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

  • Reduce unused CSS

    300 ms · 57 KiB

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

  • 1,631 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Clarity, Shopify and Klaviyo and others), adding 507 KiB and 219 ms of main-thread time.

  • Use efficient cache lifetimes

    169 KiB

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

  • Legacy JavaScript

    100 ms · 30 KiB

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

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 721 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

5 to fix100
  • 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: 5.3 s

    5.3 s

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

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • Real-user TTFB: 846 ms

    846 ms

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

  • Time to Interactive: 6.3 s

    6.3 s

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

8 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 134 ms

    134 ms

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

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

    1.3 s

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • 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).

  • Total Blocking Time: 37 ms

    37 ms

    Scripts block the page for only 37 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 2.0 MB in 166 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 166 requests on a phone: other files 764 KiB (92), images 690 KiB (17) and scripts 443 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Suroya_mobile.png 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).

  • 3 images in older formats

    3 images (151 KiB) 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.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9495
  • Positive tabindex

    3 elements have a tabindex above 0, which scrambles the keyboard order.

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

  • 60 form fields without a label

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Meta description is short (55 characters)

    Your meta description is only 55 characters: “SUYORA姿勢サポート子供用枕。鼻呼吸を促し、いびきを軽減。小児矯正歯科専門医と共同開発。90日間返金保証。”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 33 internal links, 0 external

    The homepage links to 33 pages on sneakbast.com and 0 external pages.

6 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “https://suyora.com/pages/yurika-hirao – SUYORA”.

  • Canonical URL set

    The canonical URL is https://suyora.com/.

  • Structured data in place

    Structured data found: 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://suyora.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

6 to fix38
  • 1 linked page is broken

    Your homepage links to https://suyora.com/apps/track123, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 12 pages without a meta description

    https://suyora.com/collections/%E4%BA%BA%E6%B0%97%E5%95%86%E5%93%81, https://suyora.com/pages/la-science-derriere-suyora, https://suyora.com/products/marcomp-stirnband, https://suyora.com/pages/contact, https://suyora.com/customer_authentication/redirect and https://suyora.com/collections/all and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://suyora.com/collections/%E4%BA%BA%E6%B0%97%E5%95%86%E5%93%81, whose canonical is https://suyora.com/collections/%e4%ba%ba%e6%b0%97%e5%95%86%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://suyora.com/pages/contact and https://suyora.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://suyora.com/collections/%E4%BA%BA%E6%B0%97%E5%95%86%E5%93%81, https://suyora.com/pages/la-science-derriere-suyora, https://suyora.com/products/kids-pillow, https://suyora.com/products/marcomp-stirnband, https://suyora.com/pages/contact and https://suyora.com/collections/all and 7 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.

  • 15 internal pages checked

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

1 checks passed
  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 3 small tap targets

    3 of 11 tappable elements near the top of the page are 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

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

  • Thin social proof

    Social proof on the homepage: a star rating. 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.

  • Only about 39 words

    The homepage has only about 39 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
  • 3 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Klaviyo, Meta Pixel, Microsoft Clarity and TikTok Pixel (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.

  • 13 cookies set on arrival

    13

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 sneakbast.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

Kaching Bundles · Wisereviews Reviews Importer · Microsoft Clarity · Klaviyo Email Marketing Sms · Countdown Timer

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

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 33 issues on sneakbast.com, including 11 speed issues, 2 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

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