6.6 sec in total
406 ms
5.8 sec
299 ms
Click here to check amazing Klarmobil content for Germany. Otherwise, check out these important facts you probably never knew about klarmobil.de
Entdecke die neusten Smartphones, günstige Handytarife und das beste Zubehör bei klarmobil.de. Jetzt zum günstigen Mobilfunk-Discounter wechseln.
Visit klarmobil.deWe analyzed Klarmobil.de page load time and found that the first response time was 406 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
klarmobil.de performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value7.2 s
5/100
25%
Value6.0 s
47/100
10%
Value0 ms
100/100
30%
Value0.056
98/100
15%
Value2.0 s
99/100
10%
406 ms
1233 ms
225 ms
363 ms
375 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 38% of them (56 requests) were addressed to the original Klarmobil.de, 8% (12 requests) were made to Eu-sonar.sociomantic.com and 5% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Klarmobil.de.
Page size can be reduced by 418.8 kB (35%)
1.2 MB
792.4 kB
In fact, the total size of Klarmobil.de main page is 1.2 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 621.0 kB which makes up the majority of the site volume.
Potential reduce by 97.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 97.2 kB or 86% of the original size.
Potential reduce by 6.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. Klarmobil images are well optimized though.
Potential reduce by 177.2 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 177.2 kB or 56% of the original size.
Potential reduce by 138.3 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. Klarmobil.de needs all CSS files to be minified and compressed as it can save up to 138.3 kB or 87% of the original size.
Number of requests can be reduced by 81 (63%)
128
47
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Klarmobil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
klarmobil.de
406 ms
www.klarmobil.de
1233 ms
foundation.min.css
225 ms
klarmobil.pcss
363 ms
adt-q1.css
375 ms
custom.js
347 ms
epcd.min.js
441 ms
jquery-1.11.1.min.js
554 ms
foundation.min.js
563 ms
modernizr.min.js
417 ms
klarmobil.pjs
501 ms
plain
631 ms
like.php
178 ms
beton_teaser.png
179 ms
kmheader_menu.png
180 ms
klarmobil_logo_header.png
179 ms
kmpfeil.psvg
241 ms
kmbutton.psvg
243 ms
hover_asf.png
256 ms
hover_smf.png
260 ms
hover_hst.png
278 ms
hover_sst.png
281 ms
hover_handy.png
323 ms
hover_tablet.png
364 ms
hover_bestand.png
371 ms
hover_weiteres.png
377 ms
hover_faq.png
396 ms
hover_kontakt.png
400 ms
hover_prepaid.png
432 ms
kmloading.gif
576 ms
kmicon_social.png
490 ms
q1-2016_galaxyprime.png
605 ms
q1-2016_galaxys5mini.png
612 ms
teaser_kwk40.png
516 ms
widgets.js
159 ms
KMContentkacheliGrill.jpg
1049 ms
q1-2016_startbg2.jpg
846 ms
q1-2016_simon.png
788 ms
tarifcol_katpfeil_blue.png
615 ms
q1-2016_tv.png
680 ms
kmpfeil.psvg
742 ms
kmpfeil.psvg
807 ms
kmbutton.psvg
856 ms
kmpfeil.psvg
915 ms
kmbutton.psvg
980 ms
tarifcol_katpfeil.png
980 ms
kmbutton.psvg
1041 ms
kmbutton.psvg
1098 ms
FagoWeb-Bold.woff
1200 ms
FagoWeb.woff
1040 ms
FagoWeb-Black.woff
1057 ms
vpc6VNjRPXV.js
498 ms
LVx-xkvaJ0b.png
564 ms
FagoGrunge-Regular.woff
1090 ms
kmpfeil.psvg
1049 ms
kmbutton.psvg
1112 ms
analytics.js
41 ms
plusone.js
62 ms
459 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
4 ms
kmicon_legal.png
1051 ms
socialbar.svg
1073 ms
linkid.js
10 ms
ec.js
10 ms
follow_button.6a78875565a912489e9aef879c881358.de.html
16 ms
collect
14 ms
collect
82 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
27 ms
fastbutton
97 ms
postmessageRelay
69 ms
ga-audiences
39 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
15 ms
api.js
45 ms
core:rpc:shindig.random:shindig.sha1.js
76 ms
2536007149-postmessagerelay.js
48 ms
jot
109 ms
piwik.php
622 ms
q1-siegel-small.png
712 ms
q1-siegel.png
716 ms
q1-2016_startbg.jpg
845 ms
q1-2016_simon2.png
863 ms
tarifcol_katpfeil_orange.png
768 ms
q1-2016_tv2.png
790 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
34 ms
112 ms
vpc6VNjRPXV.js
204 ms
109 ms
conversion.js
60 ms
39 ms
17 ms
track
106 ms
ld.js
79 ms
track
370 ms
iframe
453 ms
klarmobil-de
417 ms
24 ms
p-68ma6a_JX8tpW.gif
57 ms
fbds.js
296 ms
32 ms
pixel
47 ms
event
76 ms
1x1.gif
396 ms
event
358 ms
4 ms
tagging
88 ms
view
100 ms
iframe
295 ms
UserMatch.ashx
105 ms
sync.cgi
587 ms
rum
190 ms
u.php
98 ms
serve
198 ms
usersync
174 ms
Pug
171 ms
tap.php
36 ms
210 ms
info.php
511 ms
tg-03.yieldpartners.com
529 ms
1x1.gif
113 ms
74 ms
match
128 ms
match
39 ms
rum
49 ms
match
115 ms
match
212 ms
match
273 ms
pixel
23 ms
yieldlabRedirect
261 ms
improveDigitalRedirect
277 ms
rubiconRedirect
286 ms
match
268 ms
sd
40 ms
match
270 ms
adxSyncDone
261 ms
cm.gif
4 ms
mapuser
100 ms
match
96 ms
match
203 ms
adscaleSyncDone
258 ms
tap.php
25 ms
match
18 ms
tap.php
18 ms
match
97 ms
match
96 ms
dis.aspx
363 ms
3 ms
klarmobil.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-*] attributes do not match their roles
[role]s are not contained by their required parent element
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
Links do not have a discernible name
klarmobil.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
klarmobil.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 doesn't use legible font sizes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Klarmobil.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 Klarmobil.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.
klarmobil.de
Open Graph data is detected on the main page of Klarmobil. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: