13.2 sec in total
368 ms
12.5 sec
312 ms
Click here to check amazing Carthago content for Germany. Otherwise, check out these important facts you probably never knew about carthago.com
Carthago | Das Reisemobil. Integrierte und teilingetrierte Wohnmobile auf unserer Website entdecken oder direkt eine Probefahrt vereinbaren ➤ Los geht's!
Visit carthago.comWe analyzed Carthago.com page load time and found that the first response time was 368 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
carthago.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.4 s
0/100
25%
Value8.4 s
19/100
10%
Value180 ms
91/100
30%
Value1.004
2/100
15%
Value13.7 s
11/100
10%
368 ms
909 ms
292 ms
307 ms
319 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 89% of them (92 requests) were addressed to the original Carthago.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (8.8 sec) belongs to the original domain Carthago.com.
Page size can be reduced by 304.3 kB (13%)
2.4 MB
2.0 MB
In fact, the total size of Carthago.com main page is 2.4 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 91.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 91.4 kB or 86% of the original size.
Potential reduce by 62.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. Carthago images are well optimized though.
Potential reduce by 150.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 150.5 kB or 60% of the original size.
Potential reduce by 64 B
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. Carthago.com needs all CSS files to be minified and compressed as it can save up to 64 B or 26% of the original size.
Number of requests can be reduced by 45 (46%)
97
52
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carthago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
carthago.com
368 ms
909 ms
stylesheet_db7bfb3ca9-898887a459d933c4e1e82b8c0c490b80.css
292 ms
jquery.ui.theme-a0e9bd4cdd6de6eca2b60cb0267e4e49.css
307 ms
jquery.ui.datepicker-ba31235edc2b1e7ac37b02d74d7e5a96.css
319 ms
bootstrap.min.css
432 ms
carthago.css
299 ms
flexinav.css
301 ms
scrollbars.css
973 ms
font-awesome.css
962 ms
css
30 ms
_template.css
473 ms
accordion.css
466 ms
fahrzeugdaten.css
485 ms
chrisw.css
968 ms
rwd.css
625 ms
sidebar.css
631 ms
magnific-popup.css
1174 ms
jquery.min.js
66 ms
bootstrap.min.js
790 ms
docs.min.js
797 ms
flexinav_plugins-min.js
957 ms
flexinav.js
962 ms
forms.js
1119 ms
navigation.js
1122 ms
magnific-popup.js
1138 ms
jquery.cycle2.min.js
1396 ms
settings.css
1400 ms
ModellberaterSuche.js
1296 ms
jquery.ui.datepicker.min-0babd9b75261a9ef1097905460d93757.js
1700 ms
jquery.validationEngine-en-a95bf442fa6b4988dd8fd9ee40b34aec.js
1720 ms
tabs-d4dbd2f31b4ff42648d20c64b41063c6.js
1224 ms
form-daf7a74b81e94ff3904b72b4962162bb.js
1382 ms
powermail_frontend-7b02c0d125965488354b5f49955415d9.js
1393 ms
gtm.js
87 ms
logo.png
293 ms
arrow_searchopen.png
166 ms
de.png
191 ms
en.png
228 ms
fr.png
329 ms
it.png
355 ms
nl.png
391 ms
se.png
485 ms
fi.png
499 ms
arrow_languageopen.png
519 ms
2015_tourer-T145H_vV-dyn_250_131.png
1181 ms
nav-2015_tourer-T145H_vV-dyn_250_131.png
1070 ms
2015_compactline-143_vV-dyn_250_131.png
1201 ms
2015_tourer-sport-142_vv-dyn_250_131.png
1005 ms
2015_tourer-143i_vV-dyn_250_131.png
1531 ms
2015_c-line-4.9_vV-dyn_250_131.png
1455 ms
c-line-XL_vV-dyn.png
1813 ms
nav-2015_HL-59LE_vV-dyn-dh.png
1749 ms
e-line-58XL_vV-dyn.png
2672 ms
2015_s-plus-55XL_vV-dyn_250_131.png
2046 ms
2015_HL-59LE_vV-dyn_250_131.png
2302 ms
csm_2015_tourer-T145H_vV-dyn_250_131_244eff6abd.png
2634 ms
csm_platzhalter_ccd56824ff.png
1913 ms
csm_csm_Reisemobil_des_Jahres_Logo_2016_3de220a606.png
1977 ms
csm_2015_c-line-T_4.9_dyn_250_8c539f9f84.png
2593 ms
csm_platzhalter_fb17434012.png
2141 ms
csm_csm_Reisemobil_des_Jahres_Logo_2016_1d45b86e26.png
2210 ms
csm_2015_compactline-143_vV-dyn_250_131_806d748cee.png
2692 ms
csm_2015_tourer-sport-142_vv-dyn_250_131_8b777bc55b.png
3020 ms
csm_2015_tourer-148i_vV-dyn_250_131_43dfe6fce1.png
3148 ms
csm_2015_c-line-4.9_vV-dyn_250_131_3559616085.png
3532 ms
csm_c-line-XL_vV-dyn_71429a27e2.png
3907 ms
csm_2015_e-line-50_vV-dyn_250_131_89d68cc89b.png
3726 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
29 ms
hotjar-120806.js
94 ms
fontawesome-webfont.woff
3178 ms
csm_e-line-58XL_vV-dyn_b9595a41af.png
4439 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
29 ms
csm_2015_s-plus-55XL_vV-dyn_250_131_c7250a870a.png
3851 ms
csm_2015_HL-59LE_vV-dyn_250_131_7e2f9c3fd8.png
3961 ms
grafik_neufahrzeugfinder.png
3542 ms
Siegerparade_2015_slider_carthago_03.jpg
5295 ms
welle.png
3642 ms
Slider_Wintertreffen_2016_03.jpg
7364 ms
gif.png
3772 ms
analytics.js
85 ms
2015_carthago_dna_2.jpg
7897 ms
collect
27 ms
arrow_slider_left.png
3829 ms
arrow_slider_right.png
3853 ms
carthago_city_1600_650.jpg
8758 ms
collect
53 ms
ga-audiences
40 ms
visit-data
204 ms
c-tourer-I-144-LE_Sitzgruppe-von-oben_teaser.jpg
3640 ms
e-line_Fahraufnahme_200_151.jpg
4989 ms
harry_wijnvoord_film.jpg
4901 ms
carthago_kataloge_2016.jpg
5080 ms
modellberater.png
4769 ms
neufahrzeugfinder.png
4716 ms
probefahrt.png
4639 ms
servicetermin.png
4597 ms
katalogbestellung.png
4530 ms
Carthago_Wintertreffen.jpg
5680 ms
2016_Carthago-gewinnt-Innovationspreis.jpg
6336 ms
carthago_cmt_2016_01.jpg
5972 ms
facebook.png
5620 ms
youtube.png
5600 ms
carthago.com accessibility score
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
carthago.com 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
carthago.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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 Carthago.com 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 Carthago.com 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.
carthago.com
Open Graph description is not detected on the main page of Carthago. 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: