sugoimart.com website review

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

24 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Matomo, reddit and maestra-static.io and others), adding 3.5 MB and 1.6 s of main-thread time.

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

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

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

maestra-static.io costs a phone 264 ms of main-thread work and 1.9 MB 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.

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

Matomo costs a phone 391 ms of main-thread work and 62 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.

reddit costs a phone 283 ms of main-thread work and 26 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.

rise-ai.com costs a phone 143 ms of main-thread work and 589 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.

rebuyengine.com costs a phone 142 ms of main-thread work and 326 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.

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

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

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.

5 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Use code EARLYBF10 for 10% off everything”.

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

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

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

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

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

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

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

The layout shifts by 0.168 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 11.7 MB in 508 requests on a phone: images 6.3 MB (119), scripts 2.5 MB (86) and other files 1.6 MB (250). Under 2 MB keeps phones on slow connections fast.

Banner_1-80.jpg 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).

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

4 elements hidden from screen readers can still receive keyboard focus.

1 tap target is too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

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

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

Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Use code EARLYBF10 for 10% off everything”, “30 Nights of Japan Advent Calendar” and “Tokyo Choco Club: 12-Day Japanese Kit Kat Advent …”). One clear main headline is easier for people and search engines.

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

The homepage links to 315 pages on sugoimart.com and 30 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.sugoimart.com/collections/recently-added and https://www.sugoimart.com/collections/2026-advent-calendars have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sugoimart.com/products/onimusha-snack-box-limited-edition, https://www.sugoimart.com/products/30-nights-of-japan-advent-calendar-by-sugoi-mart, https://www.sugoimart.com/products/doki-doki-kit-kat-advent-calendar-by-sugoi-mart, https://www.sugoimart.com/collections/best-sellers, https://www.sugoimart.com/collections/recently-added and https://www.sugoimart.com/collections/2026-advent-calendars and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sugoimart.com/products/onimusha-snack-box-limited-edition, https://www.sugoimart.com/products/30-nights-of-japan-advent-calendar-by-sugoi-mart, https://www.sugoimart.com/products/doki-doki-kit-kat-advent-calendar-by-sugoi-mart, https://www.sugoimart.com/products/pokemon-surprise-bath-popping-ball-shining-white-snow-crystals, https://www.sugoimart.com/products/ghibli-howls-moving-castle-round-lunch-box and https://www.sugoimart.com/products/naru-top-99-uzumaki-naruto-figure and 2 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.

https://www.sugoimart.com/products/doki-doki-kit-kat-advent-calendar-by-sugoi-mart, https://www.sugoimart.com/collections/best-sellers, https://www.sugoimart.com/collections/recently-added, https://www.sugoimart.com/collections/2026-advent-calendars, https://www.sugoimart.com/products/naru-top-99-uzumaki-naruto-figure and https://www.sugoimart.com/products/shangri-la-frontier-arthur-pencilgon-figure and 1 other took over 3 s to send their HTML from our server.

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

10 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 77 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 397 words of visible text.

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

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