7.2 sec in total
395 ms
6.6 sec
196 ms
Visit blackleaf.de now to see the best up-to-date Black Leaf content for Germany and also check out these interesting facts you probably never knew about blackleaf.de
In Weed We Trust ? Smoking Paraphernalia seit 1988: Bongs, Pfeifen, Vaporizer, Grinder, Dabbing Zubeh�r, Paper&Filter, Lifestyle ? Jetzt neu:…
Visit blackleaf.deWe analyzed Blackleaf.de page load time and found that the first response time was 395 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
blackleaf.de performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value8.6 s
1/100
25%
Value11.5 s
5/100
10%
Value3,090 ms
2/100
30%
Value0.775
5/100
15%
Value17.2 s
4/100
10%
395 ms
4457 ms
191 ms
208 ms
286 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 73% of them (51 requests) were addressed to the original Blackleaf.de, 14% (10 requests) were made to Static.xx.fbcdn.net and 9% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Blackleaf.de.
Page size can be reduced by 552.3 kB (28%)
2.0 MB
1.4 MB
In fact, the total size of Blackleaf.de main page is 2.0 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 39.8 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 19.8 kB, which is 45% 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.8 kB or 90% of the original size.
Potential reduce by 129.1 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. Black Leaf images are well optimized though.
Potential reduce by 274.0 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 274.0 kB or 78% of the original size.
Potential reduce by 109.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. Blackleaf.de needs all CSS files to be minified and compressed as it can save up to 109.3 kB or 85% of the original size.
Number of requests can be reduced by 34 (50%)
68
34
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Black Leaf. 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 from 5 to 1 for CSS and as a result speed up the page load time.
blackleaf.de
395 ms
www.blackleaf.de
4457 ms
styles.css
191 ms
widgets.css
208 ms
prototype.js
286 ms
ccard.js
206 ms
validation.js
209 ms
builder.js
208 ms
effects.js
304 ms
dragdrop.js
305 ms
controls.js
306 ms
slider.js
307 ms
js.js
308 ms
form.js
379 ms
menu.js
380 ms
translate.js
382 ms
cookies.js
383 ms
reflection.js
384 ms
dropdown_menu.js
386 ms
inside_bg.jpg
377 ms
inside_search_ok.gif
96 ms
angebot.jpg
281 ms
neuheiten.jpg
663 ms
handpfeife.jpg
376 ms
dreh-accessories.jpg
663 ms
verbrauchsmaterialien.jpg
468 ms
vaporizer.jpg
466 ms
bongs.jpg
663 ms
bongzubehoer%20anbauteile.jpg
562 ms
bewaren.jpg
661 ms
lifestyl%20geschenke.jpg
661 ms
bearbeiten.jpg
758 ms
innovationen.jpg
1112 ms
waagen.jpg
1207 ms
literatur%20medien.jpg
842 ms
reinigen.jpg
940 ms
bong%20shishataschen.jpg
855 ms
DEABanner.jpg
944 ms
ga.js
12 ms
inside_page_bg.gif
930 ms
inside_header.jpg
1030 ms
inside_flag_de.gif
1024 ms
inside_flag_en.gif
1029 ms
inside_header_trenner.gif
1031 ms
inside_input_text_bg.gif
1117 ms
inside_top_navi.gif
1116 ms
inside_header_menu_dot.gif
1118 ms
inside_warenkorb_bg.gif
1119 ms
inside_social_bg.gif
1191 ms
inside_twitter.gif
1204 ms
inside_face.gif
1208 ms
__utm.gif
12 ms
likebox.php
319 ms
hDvwL1_H7g-.css
89 ms
56WNbrUYLbL.css
108 ms
q68gy-v_YMF.js
145 ms
FJmpeSpHpjS.js
173 ms
0wM5s1Khldu.js
163 ms
1bNoFZUdlYZ.js
139 ms
10269553_694394257284353_3198324229716647883_n.jpg
170 ms
1069424_551022424954871_1296351408_n.jpg
80 ms
12803204_1537115306583530_2683301347874801844_n.jpg
92 ms
10703814_1561866157380188_9172920133101052745_n.jpg
89 ms
17962_101055356594943_4647732_n.jpg
88 ms
12742264_1137796502920195_2058600227928834084_n.jpg
91 ms
wL6VQj7Ab77.png
25 ms
s7jcwEQH7Sx.png
26 ms
I6-MnjEovm5.js
22 ms
pQrUxxo5oQp.js
24 ms
print.css
95 ms
blackleaf.de 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
button, link, and menuitem elements do not have accessible names.
[role]s are not contained by their required parent element
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible 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.
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>).
blackleaf.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
blackleaf.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blackleaf.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Blackleaf.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.
blackleaf.de
Open Graph description is not detected on the main page of Black Leaf. 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: