3.5 sec in total
262 ms
2.9 sec
357 ms
Welcome to janluehn.com homepage info - get ready to check Jan Luehn best content right away, or after learning these important things about janluehn.com
Visit janluehn.comWe analyzed Janluehn.com page load time and found that the first response time was 262 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
janluehn.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value8.9 s
1/100
25%
Value14.9 s
1/100
10%
Value100 ms
98/100
30%
Value0.324
35/100
15%
Value15.1 s
7/100
10%
262 ms
364 ms
113 ms
189 ms
191 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 92% of them (68 requests) were addressed to the original Janluehn.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to External.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Janluehn.com.
Page size can be reduced by 343.9 kB (11%)
3.2 MB
2.9 MB
In fact, the total size of Janluehn.com main page is 3.2 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. 65% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 44.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. 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 44.7 kB or 82% of the original size.
Potential reduce by 61.5 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. Jan Luehn images are well optimized though.
Potential reduce by 170.2 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.2 kB or 73% of the original size.
Potential reduce by 67.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. Janluehn.com needs all CSS files to be minified and compressed as it can save up to 67.5 kB or 80% of the original size.
Number of requests can be reduced by 36 (50%)
72
36
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jan Luehn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
janluehn.com
262 ms
www.janluehn.com
364 ms
system.base.css
113 ms
system.menus.css
189 ms
system.messages.css
191 ms
system.theme.css
203 ms
adaptive-image.css
205 ms
columns_filter.css
221 ms
comment.css
220 ms
date.css
281 ms
datepicker.1.7.css
285 ms
field.css
302 ms
node.css
305 ms
search.css
327 ms
user.css
330 ms
views.css
373 ms
ckeditor.css
379 ms
colorbox.css
402 ms
ctools.css
406 ms
jquery.fancybox.css
436 ms
jquery.fancybox-thumbs.css
440 ms
flexslider_img.css
465 ms
flexslider.css
474 ms
nice_menus.css
502 ms
my_nice_menus.css
507 ms
meanmenu.min.css
543 ms
MyFontsWebfontsKit.css
550 ms
style.css
557 ms
mobile.css
568 ms
tablet.css
602 ms
desktop.css
609 ms
jquery.min.js
27 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
652 ms
js_lXXd2rvZxrSqHvR17dXYesdMZcg3Zqw7vaBlOSiY5XE.js
660 ms
js_eBIdnSBFGVjZQ0GLfoF36HCclpzHOxYjarZ8WcmRCxQ.js
650 ms
js_WeJtBlZXOq-Mx01vDKI1rhiuMNwQ0lsHVffd582CpY8.js
673 ms
js_-33OgANzklsVx9k4vC9HG9tJ4777leeLWH6QoiuaDO0.js
703 ms
js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js
758 ms
2996b5
20 ms
analytics.js
8 ms
collect
63 ms
safe_image.php
304 ms
logo.png
151 ms
slider1.jpg
893 ms
slider2.jpg
832 ms
slider3.jpg
1045 ms
slider5.jpg
939 ms
slider6.jpg
969 ms
sidebar.png
218 ms
0038jan_luehn_mariobok.de_.jpg
651 ms
bok_6522.jpg
869 ms
911pw_cayenne_001_5.jpg
1034 ms
0003jan_luehn_20.11.2015.jpg
1086 ms
0064jan_luehn_20.11.2015.jpg
1094 ms
bok_8303.jpeg
1031 ms
ooxnwdt-zste3qdbqbvpxkxjvxax5zjyui6w7aqtue8sti0avmkxgc5telfvo8kjwolxcpqcayxnnxlsmaogbw.jpeg
1157 ms
img_4888.jpg
1216 ms
2007feb3b.jpg
1136 ms
bok_4773.jpg
1153 ms
adf_6289.jpg
1300 ms
IMG_8862%20tk.jpg
1288 ms
11169986_1596019377344613_7743909270784776779_n.jpg
1235 ms
dsc_0666.jpg
1370 ms
2011_61-2.jpg
1247 ms
2015-11-18_17.44.17.jpg
1305 ms
mb1_8112.jpg
1438 ms
facebook.png
1344 ms
instagram.png
1388 ms
safe_image.php
488 ms
2996B5_B_0.woff
1278 ms
2996B5_5_0.woff
1268 ms
2996B5_8_0.woff
1307 ms
2996B5_A_0.woff
1348 ms
flexslider-icon.woff
1360 ms
janluehn.com 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
Links do not have a discernible name
janluehn.com 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
General
Impact
Issue
Detected JavaScript libraries
janluehn.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Janluehn.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 Janluehn.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.
janluehn.com
Open Graph description is not detected on the main page of Jan Luehn. 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: