vinia.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and getdeviceinf.com and others), adding 2.5 MB and 2.0 s of main-thread time.

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

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

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

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

alia-prod.com costs a phone 417 ms of main-thread work and 319 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 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Yotpo costs a phone 164 ms of main-thread work and 309 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 305 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 75 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

4 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 850 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 165 ms to 173 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 3.4 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.0 MB in 504 requests on a phone: scripts 3.3 MB (119), other files 1.4 MB (304) and images 1.2 MB (36). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (77 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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: 43 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Your title is only 19 characters: “VINIA by Bioharvest”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“THE POWER OF VINIA®” and “NOW IN A DAILY CHEW”). One clear main headline is easier for people and search engines.

The homepage links to 60 pages on vinia.com and 13 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://vinia.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://vinia.com/products/vinia-1x-dailychews, https://vinia.com/products/vinia-superfood-tea-sampler, https://vinia.com/customer_authentication/redirect, https://vinia.com/tools//recurring/get-subscription-access, https://vinia.com/pages/story and https://vinia.com/pages/affiliate have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://vinia.com/tools//recurring/get-subscription-access, whose canonical is https://vinia.com/tools/recurring/get-subscription-access. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://vinia.com/customer_authentication/redirect, https://vinia.com/pages/story and https://vinia.com/pages/affiliate have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://qr7q5b2lxd.execute-api.us-west-2.amazonaws.com/trackingPixelProcessing?url=https%3A%2F%2Fvinia.com%2F&previous_page=&event=None&order_id=None&checkout_price=None.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

The homepage carries about 1,328 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 45 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 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.