2.8 sec in total
347 ms
2.2 sec
253 ms
Welcome to 24.de homepage info - get ready to check 24 best content for Germany right away, or after learning these important things about 24.de
CHECK24 - Das Vergleichsportal: Sparen Sie mit den Vergleichsrechnern für Versicherungen, Kredite, Energie, DSL, Reisen, Flüge und mehr.
Visit 24.deWe analyzed 24.de page load time and found that the first response time was 347 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
24.de performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value6.0 s
12/100
25%
Value4.1 s
78/100
10%
Value420 ms
65/100
30%
Value0
100/100
15%
Value8.5 s
38/100
10%
347 ms
340 ms
198 ms
390 ms
200 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 24.de, 51% (28 requests) were made to Check24.de and 18% (10 requests) were made to Preisvergleich.check24.de. The less responsive or slowest element that took the longest time to load (953 ms) relates to the external source Urlaub.check24.de.
Page size can be reduced by 1.1 MB (44%)
2.6 MB
1.4 MB
In fact, the total size of 24.de main page is 2.6 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 161.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. 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 161.9 kB or 82% of the original size.
Potential reduce by 101.5 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. 24 images are well optimized though.
Potential reduce by 402.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 402.0 kB or 68% of the original size.
Potential reduce by 450.9 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. 24.de needs all CSS files to be minified and compressed as it can save up to 450.9 kB or 86% of the original size.
Number of requests can be reduced by 14 (29%)
48
34
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
24.de
347 ms
www.check24.de
340 ms
layout.min.css
198 ms
content.min.css
390 ms
calendar.min.css
200 ms
rsnpau.min.css
293 ms
tuevsued.png
193 ms
tv_button_grey.png
200 ms
avm-fritzfon-c4_300x300.jpg
200 ms
samsung-ue43j5550_300x300.jpg
355 ms
sony-hdr-as200v_300x300.jpg
200 ms
motorola-moto-g-2-gen-lte_300x300.jpg
199 ms
bosch-mum-54720-styline-colour-deep-red_300x300.jpg
199 ms
steba-fg-70_300x300.jpg
355 ms
braun-facespa-832n-pure-beauty-gesichtsepilierer-und-reinigungsbuerste_300x300.jpg
281 ms
akg-acoustics-k-44_300x300.jpg
354 ms
samsung-bd-j4500_300x300.jpg
355 ms
makita-bo3711_300x300.jpg
621 ms
airport.png
194 ms
arrow_back.png
193 ms
iam.js
192 ms
ext.min.js
386 ms
check24.min.js
198 ms
calendar.min.js
348 ms
check24.content.min.js
380 ms
check24.rsnpau.min.js
449 ms
c24-sprite.png
297 ms
siegel_carousel.png
584 ms
tx.io
334 ms
analytics.js
6 ms
fontawesome-webfont.woff
347 ms
collect
14 ms
collect
241 ms
gpt.js
143 ms
get
501 ms
teaser-bg-package-holding.jpg
953 ms
select-arrows.png
699 ms
1px.gif
697 ms
c24-sprite.png
108 ms
slide_home.jpg
397 ms
slide_home_easter.jpg
205 ms
slide_home.jpg
202 ms
c24-persons.png
206 ms
slide_home.jpg
318 ms
slide_home.jpg
299 ms
nummerschild_kfz.png
303 ms
slide_home.jpg
403 ms
selectArrow.png
397 ms
calendar.png
402 ms
badges.woff
761 ms
iconfont.woff
784 ms
pubads_impl_82.js
9 ms
ads
70 ms
container.html
15 ms
tx.io
98 ms
24.de 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
24.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
24.de 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
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 24.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 24.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.
24.de
Open Graph description is not detected on the main page of 24. 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: