15.6 sec in total
3.9 sec
11.4 sec
309 ms
Visit poessl-mobile.de now to see the best up-to-date Poessl Mobile content for Germany and also check out these interesting facts you probably never knew about poessl-mobile.de
Ein Campervan von Pössl ist so vielseitig, wie das Leben selbst: Heute Alltagsauto, morgen Transporter, Büro auf Rädern und am Wochenende Urlaubsdomizil.
Visit poessl-mobile.deWe analyzed Poessl-mobile.de page load time and found that the first response time was 3.9 sec and then it took 11.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.
poessl-mobile.de performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value11.2 s
0/100
25%
Value10.2 s
8/100
10%
Value220 ms
88/100
30%
Value0.477
18/100
15%
Value8.3 s
40/100
10%
3903 ms
179 ms
205 ms
404 ms
206 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 54% of them (68 requests) were addressed to the original Poessl-mobile.de, 10% (12 requests) were made to Fonts.gstatic.com and 6% (8 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Poessl-mobile.de.
Page size can be reduced by 1.7 MB (53%)
3.3 MB
1.5 MB
In fact, the total size of Poessl-mobile.de main page is 3.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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 55.2 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 55.2 kB or 79% of the original size.
Potential reduce by 19.6 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. Poessl Mobile images are well optimized though.
Potential reduce by 790.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 790.9 kB or 69% of the original size.
Potential reduce by 873.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. Poessl-mobile.de needs all CSS files to be minified and compressed as it can save up to 873.0 kB or 86% of the original size.
Number of requests can be reduced by 83 (75%)
111
28
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poessl Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.poessl-mobile.de
3903 ms
language-selector.css
179 ms
wp-filebase.css
205 ms
styles.css
404 ms
magnific-popup.css
206 ms
settings.css
411 ms
bootstrap.min.css
580 ms
fontello.css
672 ms
prettyPhoto.css
405 ms
animation.css
610 ms
flexslider.css
501 ms
perfect-scrollbar-0.4.10.min.css
504 ms
jquery.nouislider.css
512 ms
jquery.validity.css
601 ms
style.css
1109 ms
css
24 ms
style.css
613 ms
masterslider.main.css
777 ms
custom.css
2832 ms
jquery.js
907 ms
jquery-migrate.min.js
714 ms
developer-admin.js
759 ms
magnific-popup.js
817 ms
jquery.themepunch.tools.min.js
1043 ms
jquery.themepunch.revolution.min.js
1075 ms
js
28 ms
panopress.js
918 ms
panopress.css
1004 ms
wpgmappity-post-styles.css
1022 ms
css
23 ms
platform.js
100 ms
bootstrap.min.js
1057 ms
jquery-ui.min.js
1069 ms
jquery.easing.1.3.js
1078 ms
jquery.mousewheel.min.js
1115 ms
jquery.simplr.smoothscroll.min.js
1140 ms
jquery.prettyPhoto.js
1149 ms
modernizr.js
1169 ms
wow.min.js
1169 ms
jquery.sharre.min.js
1213 ms
jquery.flexslider-min.js
1127 ms
jquery.knob.js
1133 ms
jquery.mixitup.min.js
1151 ms
masonry.min.js
1141 ms
jquery.masonry.min.js
991 ms
jquery.jplayer.min.js
1013 ms
jquery.fitvids.js
1020 ms
perfect-scrollbar-0.4.10.with-mousewheel.min.js
939 ms
jquery.nouislider.min.js
950 ms
jquery.validity.min.js
983 ms
script.js
1033 ms
wp-embed.min.js
932 ms
sitepress.js
924 ms
fts-global.js
942 ms
imagesloaded.pkgd.min.js
919 ms
masonry.pkgd.min.js
916 ms
wp-emoji-release.min.js
865 ms
ga.js
71 ms
logo_poessl.png
407 ms
de.png
408 ms
en.png
407 ms
poessl_limited_highlight.jpg
794 ms
slider_hline.jpg
794 ms
poessl_outdoor.jpg
1289 ms
safe_image.php
674 ms
12419101_738695919601248_3504855404129945291_o.jpg
745 ms
hqdefault.jpg
434 ms
hqdefault.jpg
442 ms
hqdefault.jpg
463 ms
hqdefault.jpg
462 ms
piwik.js
627 ms
admin-ajax.php
2737 ms
cb=gapi.loaded_0
77 ms
cb=gapi.loaded_1
117 ms
subscribe_embed
170 ms
__utm.gif
53 ms
menu-arrows.png
129 ms
video-play-btn.png
223 ms
small_left.png
350 ms
small_right.png
534 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
51 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
70 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
98 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
98 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
100 ms
fontello.woff
1151 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
98 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
99 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
96 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
98 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
99 ms
fontawesome-webfont.woff
607 ms
CEoUG_XKxMA
116 ms
FW0bZSblWFo
120 ms
v3VJjWMBZUA
111 ms
postmessageRelay
62 ms
DgUlHXuoV1U
83 ms
www-embed-player-vflZsBgOl.css
105 ms
www-embed-player.js
156 ms
base.js
272 ms
www-subscribe-embed-vflWJjAep.css
204 ms
photo.jpg
47 ms
www-subscribe-embed.js
208 ms
960159_400620870060287_1693673972_n.jpg
221 ms
api.js
57 ms
core:rpc:shindig.random:shindig.sha1.js
105 ms
2536007149-postmessagerelay.js
47 ms
10358569_487602464708162_7912886493970610418_n.png
375 ms
www-hitchhiker-vfluKv9vH.png
14 ms
cb=gapi.loaded_0
21 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
86 ms
ad_status.js
77 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
83 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
84 ms
cb=gapi.loaded_2
43 ms
border_3.gif
15 ms
subscribe_embed
64 ms
spacer.gif
10 ms
border_3.gif
16 ms
bubbleSprite_3.png
25 ms
bubbleDropR_3.png
39 ms
bubbleDropB_3.png
34 ms
www-subscribe-embed-card-vflqARhQ4.css
12 ms
www-subscribe-embed-card.js
13 ms
mobilenav.css
105 ms
poessl-mobile.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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
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.
poessl-mobile.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
Browser errors were logged to the console
Page has valid source maps
poessl-mobile.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Poessl-mobile.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 Poessl-mobile.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.
poessl-mobile.de
Open Graph description is not detected on the main page of Poessl Mobile. 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: