6.2 sec in total
802 ms
5.1 sec
327 ms
Visit tmobile.de now to see the best up-to-date Tmobile content for Germany and also check out these interesting facts you probably never knew about tmobile.de
Aktuelle Telekom Angebote für Mobilfunk (5G/LTE), Festnetz und Internet, TV & mehr. Alles aus einer Hand: für zuhause & unterwegs. Erleben was verbindet!
Visit tmobile.deWe analyzed Tmobile.de page load time and found that the first response time was 802 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tmobile.de performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value17.9 s
0/100
25%
Value12.1 s
3/100
10%
Value13,810 ms
0/100
30%
Value0.061
98/100
15%
Value29.3 s
0/100
10%
802 ms
210 ms
319 ms
327 ms
570 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tmobile.de, 8% (10 requests) were made to Tealium.hs.llnwd.net and 8% (10 requests) were made to Telekom.de. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source T-mobile.de.
Page size can be reduced by 914.2 kB (76%)
1.2 MB
294.8 kB
In fact, the total size of Tmobile.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. 50% of websites need less resources to load. Javascripts take 801.2 kB which makes up the majority of the site volume.
Potential reduce by 110.3 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 110.3 kB or 82% of the original size.
Potential reduce by 31.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. Obviously, Tmobile needs image optimization as it can save up to 31.4 kB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 592.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 592.5 kB or 74% of the original size.
Potential reduce by 179.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. Tmobile.de needs all CSS files to be minified and compressed as it can save up to 179.9 kB or 83% of the original size.
Number of requests can be reduced by 76 (59%)
128
52
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.t-mobile.de
802 ms
layout.css
210 ms
design.css
319 ms
content.css
327 ms
cookielib.js
570 ms
0,8033,0,00.js
360 ms
mainnav.js
343 ms
jquery-1.11.1.min.js
29 ms
tmd.jquery.scripts.js
343 ms
jquery.autocomplete.js
424 ms
jquery.cookie.js
433 ms
tablet.switch.150126.js
452 ms
homepage-fade-buehne-reiter.js
355 ms
homepage-functions-2015.js
371 ms
trustedshops.js
433 ms
utag.js
33 ms
external-script-checker.js
441 ms
frame-bg.png
114 ms
transparent.gif
116 ms
0,3465,239236,00.jpg
114 ms
0,3465,238698,00.png
323 ms
0,3465,235068,00.png
218 ms
0,3465,238338,00.png
210 ms
0,3465,230635,00.jpg
215 ms
0,3465,230616,00.jpg
220 ms
0,3465,238492,00.jpg
221 ms
0,3465,238866,00.png
321 ms
0,3465,235896,00.png
331 ms
0,3465,230674,00.png
331 ms
0,3465,233381,00.jpg
332 ms
0,3465,230654,00.png
334 ms
0,3465,235748,00.png
423 ms
0,3465,232190,00.png
429 ms
0,3465,231529,00.png
427 ms
0,3465,237402,00.png
435 ms
0,3465,231691,00.png
437 ms
0,3465,239787,00.png
436 ms
0,3465,234553,00.jpg
530 ms
0,3465,234224,00.jpg
537 ms
0,3465,234198,00.jpg
539 ms
0,3465,206399,00.png
544 ms
0,3465,206401,00.png
549 ms
0,3465,206402,00.png
550 ms
0,3465,230820,00.gif
635 ms
0,3465,221760,00.png
640 ms
t-logo.gif
644 ms
0,3465,220814,00.png
622 ms
0,3465,239508,00.jpg
734 ms
0,3465,239820,00.jpg
736 ms
0,3465,239235,00.jpg
711 ms
0,3465,239130,00.jpg
717 ms
0,3465,238825,00.jpg
726 ms
0,3465,236656,00.jpg
731 ms
X4DD2D10F6CCF0308E1701D189090920C.js
207 ms
482 ms
csg_footnote.min.js
1162 ms
0,3465,232579,00.png
748 ms
pixel.png
531 ms
0,3465,230617,00.png
728 ms
0,3465,227436,00.png
665 ms
frame-bottom.png
664 ms
t-logo-claim.gif
664 ms
client-tab-left-first.png
745 ms
client-tab-right.png
758 ms
client-tab-left.png
663 ms
search.png
665 ms
button-light-white-right.png
659 ms
button-light-white-left.png
740 ms
frame-top.png
754 ms
main-menu-left.png
759 ms
main-menu-right.png
672 ms
mainmenu-shadow.png
670 ms
0,3465,227440,00.png
752 ms
script.js
111 ms
hit.xiti
367 ms
utag.121.js
13 ms
favicon.ico
110 ms
utag.89.js
11 ms
utag.88.js
40 ms
utag.45.js
40 ms
utag.66.js
74 ms
utag.12.js
72 ms
utag.85.js
71 ms
utag.30.js
88 ms
utag.120.js
90 ms
production_sidebar.css
898 ms
wt
806 ms
production_sidebar.css
890 ms
137 ms
wt
830 ms
profiler.html
49 ms
iam.js
424 ms
58 ms
tag.js
176 ms
print.css
129 ms
main.js
11 ms
t-mobile.de.config.jsonp
15 ms
65 ms
xups.xplosion.de
522 ms
122 ms
.jsonp
210 ms
117 ms
230 ms
296 ms
pixel
101 ms
storage.min.html
447 ms
mTag.js
516 ms
tx.io
476 ms
cc
408 ms
conv
225 ms
263 ms
dc_match
23 ms
sync
12 ms
tap.php
20 ms
match
9 ms
s_match
4 ms
production_sidebar.js
433 ms
tx.io
100 ms
252 ms
350 ms
cc
100 ms
usersync
428 ms
icon-community.png
119 ms
icon-webcode.png
113 ms
icon-close.png
215 ms
icon-hotline.png
223 ms
icon-hilfe-service.png
329 ms
icon-kontakt.png
337 ms
icon-search.png
323 ms
95 ms
83 ms
style.css
45 ms
bg_nano.png
26 ms
tmobile.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
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
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
tmobile.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
tmobile.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 uses legible font sizes
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tmobile.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 Tmobile.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
tmobile.de
Open Graph description is not detected on the main page of Tmobile. 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: