5.4 sec in total
867 ms
4.4 sec
186 ms
Click here to check amazing T Mobile content for Czech Republic. Otherwise, check out these important facts you probably never knew about tmobile.cz
U nás pořídíte tarifní řešení pro celou domácnost - neomezené volání, mobilní data, domácí internet i digitální TV. Výhodně v Magentě 1.
Visit tmobile.czWe analyzed Tmobile.cz page load time and found that the first response time was 867 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tmobile.cz performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value14.3 s
0/100
25%
Value12.9 s
3/100
10%
Value2,640 ms
4/100
30%
Value2.471
0/100
15%
Value16.7 s
5/100
10%
867 ms
825 ms
846 ms
881 ms
739 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tmobile.cz, 32% (22 requests) were made to T-mobile.cz and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static2.t-mobile.cz.
Page size can be reduced by 1.2 MB (61%)
2.0 MB
752.9 kB
In fact, the total size of Tmobile.cz main page is 2.0 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. 45% of websites need less resources to load. Javascripts take 870.7 kB which makes up the majority of the site volume.
Potential reduce by 160.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 160.2 kB or 67% of the original size.
Potential reduce by 10.0 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. T Mobile images are well optimized though.
Potential reduce by 558.3 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 558.3 kB or 64% of the original size.
Potential reduce by 470.4 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.cz needs all CSS files to be minified and compressed as it can save up to 470.4 kB or 84% of the original size.
Number of requests can be reduced by 36 (61%)
59
23
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of T 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 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
osobni
867 ms
jquery-1.11.2.js
825 ms
libs.js
846 ms
aui.css
881 ms
main.css
739 ms
ext.css
632 ms
main.css
745 ms
main.css
747 ms
barebone.jsp
1191 ms
main.js
901 ms
navigation.js
900 ms
custom.css
1044 ms
5a0f0b27-f95c-47c2-a490-d1a27282681d.js
216 ms
minicart.js
232 ms
ext.js
860 ms
main.js
874 ms
integration
338 ms
bootstrap.js
228 ms
logo.svg
167 ms
46408833-7c2a-4b95-97f7-651bd363e171.js
166 ms
gtm.js
245 ms
tele-groteskeenor-webfont.woff
143 ms
tele-groteskeehal-webfont.woff
142 ms
tele-groteskeefet-webfont.woff
141 ms
269 ms
sprite.svg
845 ms
webtrends.js
267 ms
stylesheets
262 ms
osobni
298 ms
osobni
254 ms
94 ms
pixel
83 ms
icons.woff
222 ms
pixel
90 ms
645 ms
retargeting
931 ms
conversion_async.js
653 ms
gfk_telekom_onexit.js
620 ms
fbevents.js
803 ms
analytics.js
649 ms
cm
820 ms
javascripts
548 ms
521 ms
wtid.js
643 ms
osobni
650 ms
4aca31b2-4c70-4729-a352-bd4e5a892a9a.jpg
931 ms
ChatSettings
176 ms
available_languages.jsp
224 ms
138 ms
28 ms
ec.js
12 ms
33 ms
collect
24 ms
collect
80 ms
osobni
178 ms
5903100b-e0fd-4b5b-9709-f7dea9772840.jpg
223 ms
120 ms
139 ms
0222fda5-f33c-4d29-9297-68c7600427b7.jpg
798 ms
3fbebfc7-df80-4cef-b7e0-deea32c5ca3e.jpg
115 ms
ee1332e1-7194-4410-b54e-42d49f89ffac.jpg
162 ms
219f3858-df01-45f7-a651-91958d3ea0d6.jpg
382 ms
osobni
232 ms
77af6aa0-82d4-4934-8ae8-d92fb2d5df8e.jpg
215 ms
bulk
280 ms
osobni
140 ms
jsonp
100 ms
bulk
223 ms
tmobile.cz 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
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
Form elements do not have associated labels
Links do not have a discernible name
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>).
tmobile.cz 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
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
tmobile.cz 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
Tap targets are not sized appropriately
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tmobile.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Tmobile.cz 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.
tmobile.cz
Open Graph description is not detected on the main page of T 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: