vivaia.jp website review

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and shulex-voc.com and others), adding 2.1 MB and 1.9 s of main-thread time.

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

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

About 629 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.

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

Google Tag Manager costs a phone 578 ms of main-thread work and 494 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 440 ms of main-thread work and 757 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.

shulex-voc.com costs a phone 292 ms of main-thread work and 466 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.

Facebook costs a phone 255 ms of main-thread work and 230 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.

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

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

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

6 KiB could be saved by minifying CSS.

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.

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.

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Floraが主役の季節へ”.

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

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

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

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

The first text or image appears after 2.1 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 270 ms to 253 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 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 234 requests on a phone: scripts 1.9 MB (115), fonts 1.0 MB (44) and images 288 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image (33 KiB) is 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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

21 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 23 characters: “VIVAIA日本唯一の正規販売 | 公式サイト”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 107 pages on vivaia.jp and 1 external page.

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.

https://vivaia.jp/products/boots-flora-oatmilkwoolwaterproof and https://vivaia.jp/products/boots-flora-blackwoolwaterproof all use the title “[Flora] 日本限定 ラウンドトゥ 防水加工 ラグソール ショートブーツ | VIVAIA”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://vivaia.jp/pages/vivaia-news, https://vivaia.jp/pages/vivaia-x-futakotamagawa-store and https://vivaia.jp/pages/natural-time have no meta description, so Google writes the search snippet from whatever text it finds.

https://vivaia.jp/products/boots-flora-oatmilkwoolwaterproof and https://vivaia.jp/products/boots-flora-blackwoolwaterproof use the same meta description. A description written for each page earns more clicks.

https://vivaia.jp/pages/long-boots-winter, https://vivaia.jp/pages/vivaia-news, https://vivaia.jp/pages/vivaia-x-futakotamagawa-store and https://vivaia.jp/collections/bestseller have no <h1> headline, so visitors and search engines get no clear main topic.

https://vivaia.jp/products/boots-flora-oatmilkwoolwaterproof, https://vivaia.jp/pages/long-boots-winter, https://vivaia.jp/pages/vivaia-x-futakotamagawa-store, https://vivaia.jp/collections/bestseller, https://vivaia.jp/products/boots-flora-blackwoolwaterproof and https://vivaia.jp/products/boots-filipa-blackwool 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.

https://vivaia.jp/pages/vivaia-x-futakotamagawa-store, https://vivaia.jp/products/flats-moxa-lttaupeblack and https://vivaia.jp/products/flats-margotwalkerwaterproof-black took over 3 s to send their HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

The homepage has only about 89 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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