jatai.net website review

sealsubscriptions.com costs a phone 5.1 s of main-thread work and 83 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.

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

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

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

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 load with your homepage (sealsubscriptions.com, Google Tag Manager and Klaviyo and others), adding 1.5 MB and 5.8 s of main-thread time.

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

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

7 images could be 474 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 351 ms of main-thread work and 630 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.

Klaviyo costs a phone 139 ms of main-thread work and 321 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.

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

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

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

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

43 KiB could be saved by minifying JavaScript.

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

18 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20% Off All Fuji Paper - Expires November 14, 2026”.

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

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

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

Your homepage downloads 6.4 MB in 420 requests on a phone: other files 2.6 MB (238), scripts 1.8 MB (108) and images 1.6 MB (46). Under 2 MB keeps phones on slow connections fast.

Subscription-Mobile-750x600.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).

2 images are downloaded at several times the size a phone draws them, for example Feather-Styling-Razor-Standard-Blades-10pk.jpg at 901 px wide, shown at 180 px. Resized copies would save about 112 KiB.

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

Elements must only use permitted ARIA attributes: 26 elements on the page fail this check, rated serious by axe-core.

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

Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.

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

4 images have no alt text, which hurts accessibility and image search.

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

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.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 389 pages on jatai.net and 12 external pages.

The HTML your server sends has 704 of the 1,615 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

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

https://jatai.net/customer_authentication/redirect, https://jatai.net/collections/hairstylist, https://jatai.net/collections/guarded-shaving-razor, https://jatai.net/collections/guarded-shaving-razor-blades and https://jatai.net/collections/guarded-shaving-razor-kits have no meta description, so Google writes the search snippet from whatever text it finds.

https://jatai.net/pages/shipping-policy, https://jatai.net/customer_authentication/redirect, https://jatai.net/pages/academy-page, https://jatai.net/collections/subscribe-and-save, https://jatai.net/collections/hairstylist and https://jatai.net/collections/haircutting-razors-handle and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://jatai.net/pages/shipping-policy, https://jatai.net/pages/academy-page, https://jatai.net/collections/subscribe-and-save, https://jatai.net/collections/hairstylist, https://jatai.net/collections/haircutting-razors-handle and https://jatai.net/collections/haircutting-razor-blades and 8 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97271004&tm=gtm002&Ver=2&mid=f7665e94-f614-467e-b36a-9012ee210bba&bo=1&sid=e923b6f0da9911f1b78e6ff7b2ad7cfb&vid=e923cb90da9911f19dbc1710476a5eb7&vids=0&msclkid=N&gtm_t.

5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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 1,615 words of visible text.

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

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