veimia.com website review

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

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

8 third-party services load with your homepage (Shopify, Clarity and Smart Insight Tracking and others), adding 1.0 MB and 1.0 s of main-thread time.

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

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

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

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

About 375 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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 61.2 MB in 335 requests on a phone: media 55.6 MB (21), fonts 2.0 MB (1) and images 1.4 MB (58). Under 2 MB keeps phones on slow connections fast.

2_6e6f2201-e783-4f04-9b6a-dd1e92e05553.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 17.35 g of CO₂e: 2081.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

20 buttons have no accessible name, so screen readers announce just “button”.

44 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings skip levels (h1 → h4 and h3 → h6), 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.

Your <h1> is empty.

The homepage links to 351 pages on veimia.com and 11 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.veimia.com/collections/pull-on-bras has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.veimia.com/collections/%E3%83%96%E3%83%A9, whose canonical is https://www.veimia.com/collections/%e3%83%96%e3%83%a9. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.veimia.com/collections/%E3%83%96%E3%83%A9, https://www.veimia.com/collections/%E5%B0%8F%E3%81%95%E3%81%8F%E8%A6%8B%E3%81%9B%E3%82%8B%E3%83%96%E3%83%A9, https://www.veimia.com/collections/%E5%A4%A7%E3%81%8D%E3%81%84%E3%82%B5%E3%82%A4%E3%82%BA%E3%83%96%E3%83%A9, https://www.veimia.com/collections/kyouseibura, https://www.veimia.com/collections/supportive-bras and https://www.veimia.com/collections/pull-on-bras and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.veimia.com/collections/%E3%83%81%E3%83%A5%E3%83%BC%E3%83%96%E3%83%88%E3%83%83%E3%83%97%E5%9E%8B, https://www.veimia.com/collections/maeakibura, https://www.veimia.com/collections/%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%84%E3%83%96%E3%83%A9, https://www.veimia.com/collections/jyutugobura and https://www.veimia.com/collections/%E6%8E%88%E4%B9%B3%E3%83%96%E3%83%A9 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.veimia.com/collections/%E3%83%8A%E3%82%A4%E3%83%88%E3%83%96%E3%83%A9, https://www.veimia.com/collections/%E3%83%81%E3%83%A5%E3%83%BC%E3%83%96%E3%83%88%E3%83%83%E3%83%97%E5%9E%8B, https://www.veimia.com/collections/%E3%83%AC%E3%83%BC%E3%82%B9%E3%83%96%E3%83%A9, https://www.veimia.com/collections/maeakibura, https://www.veimia.com/collections/jyutugobura and https://www.veimia.com/collections/%E6%8E%88%E4%B9%B3%E3%83%96%E3%83%A9 took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://www.veimia.com/.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

The homepage has only about 211 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.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager 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 28 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.