5.3 sec in total
341 ms
4.2 sec
763 ms
Click here to check amazing Pleura content. Otherwise, check out these important facts you probably never knew about pleura.de
Visit pleura.deWe analyzed Pleura.de page load time and found that the first response time was 341 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pleura.de performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.6 s
60/100
25%
Value4.2 s
78/100
10%
Value70 ms
99/100
30%
Value0.029
100/100
15%
Value4.4 s
84/100
10%
341 ms
105 ms
718 ms
194 ms
189 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 91% of them (80 requests) were addressed to the original Pleura.de, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pleura.de.
Page size can be reduced by 502.4 kB (57%)
883.2 kB
380.7 kB
In fact, the total size of Pleura.de main page is 883.2 kB. 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 308.9 kB which makes up the majority of the site volume.
Potential reduce by 135.9 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 48.0 kB, which is 33% 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 135.9 kB or 93% of the original size.
Potential reduce by 22.9 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. Pleura images are well optimized though.
Potential reduce by 179.5 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 179.5 kB or 77% of the original size.
Potential reduce by 164.0 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. Pleura.de needs all CSS files to be minified and compressed as it can save up to 164.0 kB or 85% of the original size.
Number of requests can be reduced by 25 (32%)
78
53
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pleura. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
pleura.de
341 ms
105 ms
718 ms
bootstrap.css
194 ms
jquery.fs.selecter.css
189 ms
scojs.css
192 ms
theme.css
214 ms
font-awesome.css
218 ms
refineslide.css
222 ms
refineslide-theme-dark.css
281 ms
jquery.fs.scroller.css
285 ms
jquery.fs.picker.css
294 ms
default.css
286 ms
jquery.js
384 ms
jquery.fs.selecter.js
298 ms
jquery.fs.picker.js
372 ms
jquery.fs.scroller.js
383 ms
jquery.refineslide.js
378 ms
bootstrap.js
405 ms
theme.js
412 ms
sco.modal.js
464 ms
sco.confirm.js
470 ms
sco.ajax.js
475 ms
sco.collapse.js
477 ms
sco.countdown.js
482 ms
sco.message.js
486 ms
default.js
557 ms
581 ms
css
26 ms
css
37 ms
141 ms
253 ms
140 ms
259 ms
294 ms
344 ms
444 ms
356 ms
624 ms
372 ms
433 ms
440 ms
451 ms
468 ms
531 ms
698 ms
565 ms
552 ms
789 ms
632 ms
648 ms
670 ms
851 ms
752 ms
753 ms
2436 ms
832 ms
975 ms
877 ms
924 ms
958 ms
946 ms
974 ms
1156 ms
1053 ms
927 ms
947 ms
f8OBjBbevvywgbyJOxlO7Q.ttf
29 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
31 ms
TttUCfJ272GBgSKaOaD7KqCWcynf_cDxXwCLxiixG1c.ttf
31 ms
kpI87QY2ce-mk2ZnKb-r0g.ttf
30 ms
1TiHc9yag0wq3lDO9cw0vqCWcynf_cDxXwCLxiixG1c.ttf
29 ms
glyphicons-halflings-regular.woff
945 ms
910 ms
1139 ms
898 ms
842 ms
901 ms
916 ms
1033 ms
848 ms
909 ms
952 ms
945 ms
1076 ms
966 ms
fs-selecter-arrow.png
955 ms
pleura.de 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.
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
<frame> or <iframe> elements do not have a title
pleura.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
pleura.de SEO score
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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pleura.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Pleura.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.
pleura.de
Open Graph description is not detected on the main page of Pleura. 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: