6.2 sec in total
1.1 sec
4.8 sec
333 ms
Visit lesen.net now to see the best up-to-date Lesen content for Germany and also check out these interesting facts you probably never knew about lesen.net
Lese Neues und Wissenswertes aus der Welt der Bücher und eBooks. Aktionsangebote zu eBooks + eBook Reader, Infos zum Verkauf gebrauchter Bücher & mehr.
Visit lesen.netWe analyzed Lesen.net page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lesen.net performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.1 s
75/100
25%
Value4.0 s
80/100
10%
Value1,510 ms
14/100
30%
Value0
100/100
15%
Value12.2 s
15/100
10%
1093 ms
25 ms
318 ms
216 ms
342 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 73% of them (61 requests) were addressed to the original Lesen.net, 8% (7 requests) were made to Sumome-140a.kxcdn.com and 6% (5 requests) were made to Sumome.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lesen.net.
Page size can be reduced by 974.7 kB (46%)
2.1 MB
1.1 MB
In fact, the total size of Lesen.net main page is 2.1 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. 45% of websites need less resources to load. Images take 845.2 kB which makes up the majority of the site volume.
Potential reduce by 52.0 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 52.0 kB or 78% of the original size.
Potential reduce by 23.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. Lesen images are well optimized though.
Potential reduce by 543.9 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 543.9 kB or 68% of the original size.
Potential reduce by 355.6 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. Lesen.net needs all CSS files to be minified and compressed as it can save up to 355.6 kB or 89% of the original size.
Number of requests can be reduced by 53 (64%)
83
30
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lesen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.lesen.net
1093 ms
css
25 ms
style.css
318 ms
nggallery.css
216 ms
flick.css
342 ms
www.lesen.net
541 ms
font-awesome.min.css
421 ms
css
33 ms
polls-css.css
425 ms
postratings-css.css
495 ms
twitter-feed.css
537 ms
checkbox.min.css
593 ms
tablepress-combined.min.css
635 ms
form-theme-red.min.css
639 ms
tooltip.css
709 ms
jquery.js
1064 ms
jquery-migrate.min.js
748 ms
scrollTo.js
803 ms
jquery.form.min.js
849 ms
mailchimp.js
855 ms
core.min.js
924 ms
datepicker.js
1475 ms
modernizr.min.js
1018 ms
mediaelement-and-player.min.js
1384 ms
tooltip.js
1178 ms
front.js
1139 ms
load.sumome.com
426 ms
jquery-1.10.2.min.js
1352 ms
jquery.sticky.js
1076 ms
ssba.min.js
1155 ms
polls-js.js
1192 ms
postratings-js.js
1292 ms
wp-embed.min.js
1366 ms
wp-emoji-release.min.js
1373 ms
link-indication_style.css
114 ms
ga.js
75 ms
fbds.js
268 ms
paper-bg.jpg
317 ms
logo.png
250 ms
logo-sticky.png
251 ms
drark-transp.png
251 ms
image22-300x170.jpg
251 ms
Tolino-Vision-3-Kindle-Paperwhite-3-2-300x170.jpg
298 ms
kostenlose-ebooks-shutter-300x170.jpg
441 ms
comment-icon.png
440 ms
Bildschirmfoto-2016-02-28-um-19.22.23-220x125.png
646 ms
Bildschirmfoto-2016-02-26-um-17.59.07-220x125.png
650 ms
Bildschirmfoto-2016-02-25-um-16.17.20-1-220x125.png
621 ms
Bildschirmfoto-2016-02-24-um-18.20.56-220x125.png
631 ms
Bildschirmfoto-2016-02-24-um-14.58.49-220x125.png
755 ms
Bildschirmfoto-2016-02-23-um-18.40.36-220x125.png
865 ms
Bildschirmfoto-2016-02-22-um-19.41.08-220x125.png
1046 ms
Bildschirmfoto-2016-02-19-um-22.11.43-220x125.png
1077 ms
Bildschirmfoto-2016-02-18-um-14.42.03-220x125.png
1078 ms
shutter-reading-list-220x125.jpg
910 ms
sidebar-bg.jpg
972 ms
socialRss.png
1082 ms
socialTwitter.png
1125 ms
socialFacebook.png
1255 ms
socialGoogle.png
1257 ms
socialYoutube.png
1293 ms
haymon.png
1294 ms
top_heyne.png
1294 ms
icon-forum.png
1341 ms
icon-tipps.png
1469 ms
dc.js
33 ms
rating_over.gif
1456 ms
337 ms
__utm.gif
173 ms
__utm.gif
171 ms
108 ms
service.js
12 ms
service.js
7 ms
service.js
17 ms
service.js
16 ms
load
306 ms
sumome-scrollbox-popup.css
4 ms
sme-popup.css
8 ms
sumome-welcome-popup.css
33 ms
css
34 ms
load
241 ms
load
259 ms
load
243 ms
23 ms
lesen.net accessibility score
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
Heading elements are not in a sequentially-descending order
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
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.
lesen.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
lesen.net 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 Lesen.net 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 Lesen.net 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.
lesen.net
Open Graph description is not detected on the main page of Lesen. 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: