bloomrobbins.hu website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 579 KiB and 359 ms of main-thread time.

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

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

About 37 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 170 ms. During a long task the page ignores taps.

3 KiB could be saved by minifying CSS.

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

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

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 5.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 9.7 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 255 requests on a phone: images 1.1 MB (65), other files 839 KiB (106) and scripts 639 KiB (50). Under 2 MB keeps phones on slow connections fast.

mobile-men-line-HP.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).

1 image is downloaded at several times the size a phone draws it, for example robbin-peekaboo_1.png at 351 px wide, shown at 71 px. Resized copies would save about 35 KiB.

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

Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Bloom Hair Vitaminok Az Egészséges És Hosszú Hajért – Bloom Robbins HU”.

There are 4 <h1> headlines (“”, “Újdonság: Skincare reggelire” and “Újdonság: Végreneki is”). One clear main headline is easier for people and search engines.

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

The homepage links to 252 pages on bloomrobbins.hu and 6 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.bloomrobbins.hu/pages/rolunk and https://www.bloomrobbins.hu/pages/hozzaszolasok have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bloomrobbins.hu/products/vitaminok-az-immunitas-tamogatasara-kapszulak, https://www.bloomrobbins.hu/products/vitaminok-a-stressz-ellen-ashwagandhaval-kapszulak, https://www.bloomrobbins.hu/products/alvasjavito-vitamin-gumicukor, https://www.bloomrobbins.hu/collections/all, https://www.bloomrobbins.hu/pages/penzvisszafizetesi-garancia and https://www.bloomrobbins.hu/collections/vitaminok-a-hajhoz and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.bloomrobbins.hu/products/vitaminok-a-stressz-ellen-ashwagandhaval-kapszulak and https://www.bloomrobbins.hu/products/alvasjavito-vitamin-gumicukor took over 3 s to send their HTML from our server.

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

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.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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