5.2 sec in total
287 ms
4.7 sec
170 ms
Click here to check amazing HARIBO content for Germany. Otherwise, check out these important facts you probably never knew about haribo.com
You can find HARIBO in more than 100 countries around the world! Here you’ll find information about the company, international job offers and contacts for…
Visit haribo.comWe analyzed Haribo.com page load time and found that the first response time was 287 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
haribo.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value7.1 s
5/100
25%
Value7.7 s
25/100
10%
Value1,300 ms
18/100
30%
Value0.008
100/100
15%
Value10.0 s
26/100
10%
287 ms
831 ms
615 ms
387 ms
388 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 93% of them (70 requests) were addressed to the original Haribo.com, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to 4368278.fls.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Haribo.com.
Page size can be reduced by 1.1 MB (31%)
3.6 MB
2.5 MB
In fact, the total size of Haribo.com main page is 3.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 39.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 9.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.7 kB or 81% of the original size.
Potential reduce by 58.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. HARIBO images are well optimized though.
Potential reduce by 878.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 878.8 kB or 71% of the original size.
Potential reduce by 147.3 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Haribo.com needs all CSS files to be minified and compressed as it can save up to 147.3 kB or 84% of the original size.
Number of requests can be reduced by 43 (62%)
69
26
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HARIBO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
haribo.com
287 ms
home.html
831 ms
website-min.css
615 ms
layout.css
387 ms
layout.css
388 ms
swfobject.js
490 ms
modernizr.js
490 ms
function.js
409 ms
easeljs-0.7.1.min.js
585 ms
tweenjs-0.5.1.min.js
486 ms
preloadjs-0.4.1.min.js
522 ms
TweenMax.min.js
705 ms
app.js
926 ms
b797e71e732a4a7bb2b51d1b140ea096.js
605 ms
yui-min.js
972 ms
core-min.js
625 ms
website-min.js
771 ms
Component.js
702 ms
Controller.js
723 ms
HbTopTeaser.js
797 ms
ToggleTopTeaserComponent.js
800 ms
HbSocialMediaNews.js
821 ms
TeaserSlideshowComponent.js
867 ms
ToggleSocialMediaNewsComponent.js
892 ms
Controller.js
896 ms
logo.png
384 ms
clear.gif
478 ms
loupe.png
485 ms
01-happy-cola_230_120_0_0_7771.jpg
552 ms
02-twin-cherries_230_120_0_0_7771.jpg
486 ms
03-peaches_230_120_0_0_7771.jpg
486 ms
04a-raspberries_230_120_0_0_7771.jpg
527 ms
TOP-TEASER-smurfs_230_120_0_0_7771.jpg
612 ms
facebook-9327f1b8c1b321329cdc948cb295ae2f_0_115_170_0_831.jpg
546 ms
instagram-f06e2d38d332f6a8e1d66ca5aa3c4183_0_115_170_0_831.jpg
579 ms
TOP-TEASER-sghettis_230_120_0_0_7771.jpg
676 ms
activityi;src=4368278;type=2014W-;cat=Harib-;ord=14567537563150281622074.5444
73 ms
gtm.js
119 ms
background.png
618 ms
spacer.gif
633 ms
select-dynamic.png
639 ms
select.png
668 ms
world.png
701 ms
language-selection.png
720 ms
sprite-flag.png
1012 ms
search-field.png
735 ms
search-button.png
764 ms
transparent.gif
766 ms
vag-bold-european.ttf
945 ms
vag-bold.woff
774 ms
analytics.js
47 ms
collect
25 ms
collect
42 ms
home.html
629 ms
transparent.gif
464 ms
teaser-background-white.png
467 ms
facebook.png
525 ms
instagram.png
561 ms
background.gif
564 ms
footer-social-icon-facebook.png
642 ms
fruitbar.png
660 ms
btn_prev.png
649 ms
btn_next.png
673 ms
goldbear.png
784 ms
vag-light-european.ttf
945 ms
vag-light.woff
670 ms
preloader.gif
695 ms
HARIBO-GOLD-BEARS_USA.jpg
511 ms
10-teaser-desktop--startseite-top-products_01.jpg
560 ms
Startpage_Teaser_Locator.jpg
596 ms
Startpage_Teaser_Info.jpg
605 ms
Startpage_Teaser_Facebook.jpg
540 ms
Startpage_Teaser_Production.jpg
1326 ms
bullet_active.png
609 ms
bullet.png
636 ms
haribo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
haribo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
haribo.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haribo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Haribo.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
haribo.com
Open Graph description is not detected on the main page of HARIBO. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: