3.4 sec in total
212 ms
2.9 sec
290 ms
Click here to check amazing Luebbe content for Germany. Otherwise, check out these important facts you probably never knew about luebbe.de
Bastei Lübbe bietet ein umfassendes und abwechslungsreiches Angebot an Büchern, eBooks, Hörbüchern und Audio-Downloads
Visit luebbe.deWe analyzed Luebbe.de page load time and found that the first response time was 212 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.
luebbe.de performance score
name
value
score
weighting
Value3.8 s
29/100
10%
Value5.6 s
17/100
25%
Value9.4 s
12/100
10%
Value1,260 ms
19/100
30%
Value0.183
67/100
15%
Value10.6 s
23/100
10%
212 ms
410 ms
182 ms
261 ms
416 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 86% of them (67 requests) were addressed to the original Luebbe.de, 5% (4 requests) were made to Etracker.de and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Luebbe.de.
Page size can be reduced by 640.8 kB (27%)
2.3 MB
1.7 MB
In fact, the total size of Luebbe.de main page is 2.3 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.5 MB which makes up the majority of the site volume.
Potential reduce by 114.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 39.6 kB, which is 31% 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 114.8 kB or 89% of the original size.
Potential reduce by 33.4 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. Luebbe images are well optimized though.
Potential reduce by 244.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 244.0 kB or 56% of the original size.
Potential reduce by 248.7 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. Luebbe.de needs all CSS files to be minified and compressed as it can save up to 248.7 kB or 88% of the original size.
Number of requests can be reduced by 9 (13%)
71
62
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Luebbe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
luebbe.de
212 ms
www.luebbe.de
410 ms
bastei-luebbe.css
182 ms
combined.css
261 ms
e.js
416 ms
modernizr.js
274 ms
require.js
622 ms
jquery-1.8.3.min.js
761 ms
652 ms
t.js
672 ms
pbs.2.js
777 ms
analytics.js
123 ms
bastei-luebbe.svg
97 ms
c45464a188b81c78.jpg
407 ms
0247c8490471647e.jpeg
407 ms
spiegel-online.png
407 ms
spiegel-online-light.png
407 ms
a9c5e9127c444931.jpeg
563 ms
631fa7cab7cc24d7.jpeg
564 ms
96257575602ddaf4.jpeg
545 ms
3f9c6e517ba0cbb4.jpg
465 ms
554065181964b773.jpg
466 ms
b96e469af911d941.jpg
462 ms
ab6c8c589fa19f54.jpeg
632 ms
81a8fcbb032efc2e.jpeg
549 ms
e4736c61bb0df49e.jpeg
553 ms
a1e13b8f6796145a.jpeg
630 ms
36d5a1eba1f7afb1.jpeg
722 ms
451b9d063fb5e960.jpeg
640 ms
7fd69942a5ea6ebd.jpeg
657 ms
DeinSpiegel.png
740 ms
SpiegelBestseller.png
715 ms
595b77c73096c200.jpeg
797 ms
aac1be52a9e11fa0.jpeg
729 ms
f63f16413f4d47c3.jpeg
742 ms
e6ccaae8844d614f.jpeg
882 ms
e5e4d25a4fa0518b.jpg
803 ms
c4fc09600c5fa82f.png
816 ms
e4192eb05a267547.jpg
825 ms
a9cd4dd4a7edd73e.png
828 ms
payment_options.png
883 ms
UnitWeb-Light.woff
910 ms
UnitWeb-Thin.woff
941 ms
UnitWeb.woff
941 ms
UnitWeb-Bold.woff
940 ms
icons.woff
890 ms
collect
13 ms
17225506e59b81d3.jpeg
654 ms
c63bb1fc5ff26c76.jpeg
805 ms
50f8e224d806cf12.jpeg
807 ms
72b241c0e88cde14.jpeg
743 ms
9dd47f3af7ed7140.jpeg
678 ms
a3a37020acd14789.jpeg
681 ms
d55934b0f2a7768b.jpeg
764 ms
72f844f22d25fa71.jpeg
711 ms
578967ff6e1f737a.jpeg
709 ms
04655da7c4d509f7.jpeg
843 ms
90009727330c082d.jpeg
681 ms
199d99682e8e25e9.jpeg
684 ms
5ef601ee441eb467.jpeg
787 ms
cc3a7f233eba7f77.jpeg
698 ms
5e13c633e8550301.jpeg
780 ms
3272b882c895180d.jpeg
767 ms
69886fa357c35c88.jpeg
769 ms
650593ef20ef43db.jpeg
791 ms
47acb9d0eca862c8.jpeg
736 ms
vvcnt.php
534 ms
cnt_js.php
118 ms
cntcc
120 ms
18bf3ef054de4391.jpeg
704 ms
a1ea5d79083e5090.jpeg
706 ms
359a992eb2aeefac.jpeg
747 ms
ce0ac33e4f74bbdc.jpeg
742 ms
a4f88ba69ecaf061.jpeg
745 ms
23a4c88f822937ca.jpg
880 ms
dd016e9ee1926674.jpg
793 ms
e6f17575836366b9.jpg
702 ms
fb_button3_r.png
97 ms
luebbe.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
[aria-*] attributes are not valid or misspelled
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
luebbe.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
luebbe.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 Luebbe.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 Luebbe.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.
luebbe.de
Open Graph description is not detected on the main page of Luebbe. 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: