haribo.com website review

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

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

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

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

About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

29 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

1 long task block the main thread while loading, the longest for 98 ms. During a long task the page ignores taps.

3 third-party services load with your homepage (piwik.pro, cookiebot.eu and Monotype), adding 208 KiB and 73 ms of main-thread time.

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bag of HARIBO Goldbears and fruit gums on golden background”.

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

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

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

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

1 image (63 KiB) is 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.

3 images further down the page (84 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 0.29 g of CO₂e: 34.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 23 characters: “HARIBO of America, Inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 68 pages on haribo.com and 4 external pages.

There is no https://www.haribo.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.haribo.com/en-us/preview/72844 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.haribo.com/en-us/career and https://www.haribo.com/en-us/career/working-at-haribo all use the title “Working at HARIBO”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.haribo.com/en-us/ideas and https://www.haribo.com/en-us/retail-stores have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.haribo.com/en-us/products, https://www.haribo.com/en-us/news, https://www.haribo.com/en-us/ideas, https://www.haribo.com/en-us/career, https://www.haribo.com/en-us/about-us/quality and https://www.haribo.com/en-us/about-us/production and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.haribo.com/en-us/preview/72844 took over 3 s to send its HTML from our server.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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.

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

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.