trywellbe.rs website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Convert Insights and posthog.com and others), adding 1.2 MB and 582 ms of main-thread time.

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

Klaviyo costs a phone 135 ms of main-thread work and 330 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 17 ms of main-thread work and 362 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 28 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.

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

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

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

Your largest element takes 8.3 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 20.2 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.8 MB in 238 requests on a phone: scripts 1.4 MB (71), images 1.2 MB (45) and other files 816 KiB (98). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example 4-de_1_a3e4a14c-2356-44e8-afc0-1f6ce011b4b4.jpg at 1,620 px wide, shown at 358 px. Resized copies would save about 466 KiB.

3 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

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

Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

Your title is 86 characters, so Google will cut it off around 60: “Beauty kolagen sa vitaminom C, cinkom, hijaluronskom kiselinom, biotin – wellbe serbia”.

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

The homepage links to 29 pages on trywellbe.rs and 4 external pages.

https://trywellbe.rs/products/wellbe-x-seka-aleksic declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://trywellbe.rs/products/wellbe-x-seka-aleksic all use the title “Beauty kolagen sa vitaminom C, cinkom, hijaluronskom kiselinom, bioti…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://trywellbe.rs/collections/svi-proizvodi, https://trywellbe.rs/pages/o-nama, https://trywellbe.rs/pages/contact, https://trywellbe.rs/pages/zajedno-uz-njih-wellbe-rs-institut-za-onkologiju-i-radiologiju-srbije and https://trywellbe.rs/pages/obrazac-za-reklamaciju have no meta description, so Google writes the search snippet from whatever text it finds.

https://trywellbe.rs/products/beauty-kollagen-wildberry-mit-rejuva-complex%C2%AE-formel and https://trywellbe.rs/products/wellbe-x-seka-aleksic use the same meta description. A description written for each page earns more clicks.

https://trywellbe.rs/collections/svi-proizvodi, https://trywellbe.rs/pages/o-nama and https://trywellbe.rs/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

Large scripts ship without source maps.

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.

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

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

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