shingetsu3gin.com website review

The page goes through 3 redirects before it starts loading, costing about 4.4 s. Link and advertise the final URL directly.

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

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

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

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

5 third-party services load with your homepage (Google CDN, Shopify and Other Google APIs/SDKs and others), adding 2.0 MB and 121 ms of main-thread time.

The HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Shopify costs a phone 23 ms of main-thread work and 1.3 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.

Other Google APIs/SDKs costs a phone 21 ms of main-thread work and 506 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.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unparalleled smoothness for pure enjoyment. For sipping on …”.

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

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

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

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

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

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.

Your homepage downloads 3.6 MB in 291 requests on a phone: images 1.4 MB (14), other files 1.2 MB (127) and scripts 698 KiB (86). Under 2 MB keeps phones on slow connections fast.

Screenshot_2024-11-25_at_12.53.17_PM_0bb0866d-67e8-46f5-b0cb 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).

1 image is downloaded at several times the size a phone draws it, for example Product-Transparent-3.png at 1,145 px wide, shown at 300 px. Resized copies would save about 86 KiB.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 10 characters: “Shingetsu3”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Unparalleled smoothness for pure enjoyment.”). One clear main headline is easier for people and search engines.

The homepage links to 13 pages on shingetsu3gin.com and 7 external pages.

https://shingetsu3gin.com/policies/shipping-policy, https://shingetsu3gin.com/pages/contact and https://shingetsu3gin.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 718 words of visible text.

Before a visitor clicks anything, the page loads Meta 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.

Opening the homepage sets 8 cookies, 2 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.