opositiv.com website review

Shopify costs a phone 3.3 s of main-thread work and 2.4 MB 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.

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

Google Tag Manager costs a phone 2.4 s of main-thread work and 724 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.

17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 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 (Shopify, Google Tag Manager and Facebook and others), adding 3.9 MB and 8.1 s of main-thread time.

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

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

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

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

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

TikTok costs a phone 533 ms of main-thread work and 157 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.

Snapchat costs a phone 371 ms of main-thread work and 54 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.

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

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

23 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.

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

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

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

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

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

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

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 201 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 424 requests on a phone: scripts 2.7 MB (160), images 1.3 MB (93) and fonts 597 KiB (7). Under 2 MB keeps phones on slow connections fast.

8 images (1.1 MB) are 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.

spinner-20_-off.png 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 1.43 g of CO₂e: 171.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Some list items are not inside a list.

Links must have discernible text: 8 elements on the page fail this check, rated serious by axe-core.

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

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.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 67 pages on opositiv.com and 2 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://opositiv.com/collections/shop-all, https://opositiv.com/collections/shop-bundles and https://opositiv.com/collections/shop-all/best-seller all use the title “Shop All | O Positiv”, 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://opositiv.com/collections/shop-all, https://opositiv.com/collections/shop-bundles, https://opositiv.com/collections/shop-all/best-seller, https://opositiv.com/pages/state-of-vagina, https://opositiv.com/pages/clinical-network and https://opositiv.com/pages/medical-board and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://opositiv.com/products/uro-vaginal-probiotic-capsule, whose canonical is https://opositiv.com/products/uro-vaginal-probiotic-capsules. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://opositiv.com/collections/shop-all, https://opositiv.com/collections/shop-bundles, https://opositiv.com/collections/shop-all/best-seller, https://opositiv.com/pages/state-of-vagina, https://opositiv.com/blogs/blog and https://opositiv.com/pages/medical-board and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17549654&tm=gtm002&Ver=2&mid=3790be75-d4bf-4992-acaf-1640124600ea&bo=1&sid=9a8b4080d96911f1ad176d8b77c91339&vid=9a8b7b70d96911f1ad8db5bc2baaf83b&vids=1&msclkid=N&pi=91.

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

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

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1113530301.1793918297&gtm=45He6b40v9193309333za200zd919330…”.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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