25 sec in total
11.3 sec
13.6 sec
155 ms
Welcome to planehopper.de homepage info - get ready to check Planehopper best content right away, or after learning these important things about planehopper.de
Visit planehopper.deWe analyzed Planehopper.de page load time and found that the first response time was 11.3 sec and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
planehopper.de performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
11293 ms
614 ms
609 ms
613 ms
590 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 92% of them (33 requests) were addressed to the original Planehopper.de, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (11.3 sec) belongs to the original domain Planehopper.de.
Page size can be reduced by 317.3 kB (31%)
1.0 MB
718.9 kB
In fact, the total size of Planehopper.de main page is 1.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. 20% of websites need less resources to load. Images take 650.4 kB which makes up the majority of the site volume.
Potential reduce by 83.4 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 83.4 kB or 83% of the original size.
Potential reduce by 26.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. Planehopper images are well optimized though.
Potential reduce by 154.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 154.0 kB or 70% of the original size.
Potential reduce by 53.8 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. Planehopper.de needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 84% of the original size.
Number of requests can be reduced by 20 (61%)
33
13
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planehopper. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
planehopper.de
11293 ms
wp-emoji-release.min.js
614 ms
styles.css
609 ms
gglcptch.css
613 ms
page-list.css
590 ms
yasr.css
297 ms
yasr-table-light.css
331 ms
style.css
832 ms
css
30 ms
jquery.js
1065 ms
jquery-migrate.min.js
741 ms
tinynav.js
772 ms
backtotop.js
798 ms
jquery.bxslider.css
707 ms
jquery.form.min.js
906 ms
scripts.js
1078 ms
jquery.rateit.min.js
990 ms
yasr-front.js
962 ms
jquery.cycle.all.min.js
1066 ms
attitude-slider-setting.js
1121 ms
wp-embed.min.js
1130 ms
jquery.bxslider.js
1393 ms
bxslider.setup.js
1408 ms
Planehopper_new_test_banner.png
835 ms
social-icons.png
497 ms
search_blue.png
458 ms
Planehopper_new_logo_1_small1.png
500 ms
loading1.gif
534 ms
Slider_banner_1.jpg
951 ms
Slider_banner_2.jpg
1210 ms
Slider_banner_31.jpg
1234 ms
arrows.simple.png
912 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
10 ms
OttjxgcoEsufOGSINYBGLZ0EAVxt0G0biEntp43Qt6E.ttf
20 ms
Planehopper_new_test_footer.png
890 ms
back-to-top.png
932 ms
planehopper.de accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
planehopper.de 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
planehopper.de SEO score
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planehopper.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Planehopper.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.
planehopper.de
Open Graph description is not detected on the main page of Planehopper. 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: