simbioplus.hu website review

12 images could be 766 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Mailchimp and others), adding 2.6 MB and 650 ms of main-thread time.

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

Shopify costs a phone 259 ms of main-thread work and 1.7 MB 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.

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

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

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

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

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

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

5 KiB could be saved by minifying CSS.

1 KiB JavaScript is shipped twice across bundles.

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 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Untitled_1400_x_1400_px_-2”.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.4 MB in 339 requests on a phone: scripts 1.7 MB (100), other files 1.3 MB (170) and images 981 KiB (20). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example Immunrendszer-Tamogato-Csomag.webp at 2,048 px wide, shown at 202 px. Resized copies would save about 769 KiB.

Copy_of_Untitled_1400_x_1400_px_1400_x_1000_px_-3.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).

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

3 images (424 KiB) 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.

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

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

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

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

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

Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.

Your title is 70 characters, so Google will cut it off around 60: “Anyatej oligoszacharidok és prebiotikus rostok a bélflóra egészségéért”.

There are 2 <h1> headlines (“Érzékeny emésztés, visszatérő panaszok? Kezdje a …” and “Egészségügyi videótár”). One clear main headline is easier for people and search engines.

Your meta description is 206 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/SimbioPlus_emblema_fekvo_color_m_szlogennel…”.

The homepage links to 115 pages on simbioplus.hu and 5 external pages.

https://simbioplus.hu/collections/osszes-termek, https://simbioplus.hu/pages/vasarloi-visszajelzesek, https://simbioplus.hu/blogs/tudasbazis, https://simbioplus.hu/pages/rolunk-irtak-osszes and https://simbioplus.hu/pages/gyakran-ismetelt-kerdesek-1 have no <h1> headline, so visitors and search engines get no clear main topic.

https://simbioplus.hu/pages/orvosok-mondjak, https://simbioplus.hu/blogs/tudasbazis, https://simbioplus.hu/products/simbioplus-enterovit and https://simbioplus.hu/products/fiber-pectin-kimeletes-rost-az-emesztesnek took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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: 123 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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 15 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.