5.2 sec in total
815 ms
4.1 sec
334 ms
Click here to check amazing Olerum content for Germany. Otherwise, check out these important facts you probably never knew about olerum.de
Pflanzen in bester Qualität ♥ Beste Gewächshäuser ★ Sinnvolles Gartenzubehör ♥ Saatgut, Blumenerde, Dünger, etc. ✓ Jetzt online im Pflanzenshop kaufen!
Visit olerum.deWe analyzed Olerum.de page load time and found that the first response time was 815 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
olerum.de performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value14.0 s
0/100
25%
Value13.8 s
1/100
10%
Value11,000 ms
0/100
30%
Value0.206
60/100
15%
Value22.3 s
1/100
10%
815 ms
237 ms
54 ms
99 ms
256 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 79% of them (92 requests) were addressed to the original Olerum.de, 8% (9 requests) were made to Google.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Olerum.de.
Page size can be reduced by 500.6 kB (29%)
1.7 MB
1.2 MB
In fact, the total size of Olerum.de main page is 1.7 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 96.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 96.5 kB or 80% of the original size.
Potential reduce by 28.3 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. Olerum images are well optimized though.
Potential reduce by 170.4 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 170.4 kB or 56% of the original size.
Potential reduce by 205.5 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. Olerum.de needs all CSS files to be minified and compressed as it can save up to 205.5 kB or 83% of the original size.
Number of requests can be reduced by 44 (39%)
114
70
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olerum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
olerum.de
815 ms
thickbox.css
237 ms
jquery.min.js
54 ms
plusone.js
99 ms
gartencentersuche.js
256 ms
thickbox-compressed.js
256 ms
generic.css
257 ms
slider.css
254 ms
thumbnail-slider.js
256 ms
tooltip.js
414 ms
tooltip.css
323 ms
dcverticalmegamenu.css
332 ms
jquery.min.js
60 ms
jquery.hoverIntent.minified.js
329 ms
jquery.dcverticalmegamenu.1.3.js
332 ms
stylesheet_2015.css
525 ms
master_slave.css
428 ms
main.js
1106 ms
slider.js
1011 ms
service.js
1013 ms
cb=gapi.loaded_0
17 ms
bg.jpg
201 ms
bg_green.png
162 ms
blind.png
159 ms
comodo.png
164 ms
topheader_streifen.gif
163 ms
paypal.png
163 ms
dhl.png
188 ms
gls-logo.png
207 ms
sofortueberweisung.png
210 ms
vdg_logo.png
230 ms
premium.png
209 ms
oase_partner.png
281 ms
40_euro_gratis_versand.png
323 ms
arrow_left.png
308 ms
arrow_right.png
324 ms
Header-Fruehlingsflirt.jpg
866 ms
Header-Gemuesespass.jpg
688 ms
olerum.png
373 ms
GW.jpg
807 ms
online-shop.png
404 ms
graines_dor.png
398 ms
zahlarten.gif
401 ms
arrow_left.png
464 ms
arrow_right.png
490 ms
ACD_logo_Q.jpg
495 ms
biocontrollogo.jpg
500 ms
Bayer.png
557 ms
baza.jpg
582 ms
BroilKing.jpg
589 ms
image001.png
596 ms
1-Logo_Jiffy.jpg
649 ms
dhg.png
675 ms
fruxLogo50mm.png
684 ms
elhologo.png
694 ms
emiko-logo1.jpg
740 ms
emsa.png
755 ms
cse.js
142 ms
analytics.js
17 ms
X783A65DC2E149E7DAFD13F0488E684EC.js
491 ms
ga.js
34 ms
collect
85 ms
__utm.gif
24 ms
collect
103 ms
quedlinburger.jpg
621 ms
gilde.jpg
623 ms
GreenLifeLogo.jpg
630 ms
logo_grillson.jpg
675 ms
logo_haeberli.jpg
700 ms
jsapi
23 ms
collect
83 ms
1-LogoHSgrn2Kopie.jpg
687 ms
default+de.css
5 ms
default+de.I.js
13 ms
hoefats_aufschwarz.jpg
681 ms
Kientzler_Logo.jpg
685 ms
labio.png
722 ms
laverda.jpg
747 ms
default.css
78 ms
lechuza.png
732 ms
async-ads.js
52 ms
google_custom_search_watermark.gif
27 ms
small-logo.png
18 ms
search_box_icon.png
19 ms
clear.gif
18 ms
link.png
19 ms
nav_logo114.png
14 ms
villa_mellerud.png
690 ms
neudorff.png
653 ms
1-OASE_Logo.jpg
663 ms
verband_deutscher_gartencenter.jpg
698 ms
roesle_logo_1888.png
676 ms
SERAMIS_LOGOClaim.jpg
657 ms
stabtrend.png
661 ms
takagi-logo.jpg
666 ms
staudenring.png
618 ms
weber.png
625 ms
wolf-garten.png
645 ms
bg_topmenu.png
649 ms
bg_cart_login.png
601 ms
arrow_cart.gif
581 ms
logos1.gif
590 ms
logos3.gif
610 ms
facebook.png
582 ms
twitter.png
568 ms
googleplus.png
567 ms
footer_end.png
573 ms
loadingAnimation.gif
581 ms
arrow_white.png
557 ms
style.css
4 ms
closeBtn.gif
558 ms
teaser_shadow_arrow.png
96 ms
teaser_saatgut.jpg
556 ms
teaser_vogelfutter.jpg
732 ms
teaser_kartoffeln.jpg
919 ms
teaser_knolle.jpg
555 ms
badge_compressed.png
3 ms
olerum.de accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
olerum.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
olerum.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olerum.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Olerum.de 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.
olerum.de
Open Graph description is not detected on the main page of Olerum. 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: