5.6 sec in total
444 ms
4.7 sec
505 ms
Click here to check amazing T Mobile content for Czech Republic. Otherwise, check out these important facts you probably never knew about t-mobile.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 t-mobile.czWe analyzed T-mobile.cz page load time and found that the first response time was 444 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
t-mobile.cz performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value26.3 s
0/100
25%
Value18.6 s
0/100
10%
Value5,380 ms
0/100
30%
Value0.017
100/100
15%
Value27.5 s
0/100
10%
444 ms
351 ms
694 ms
595 ms
456 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 23% of them (14 requests) were addressed to the original T-mobile.cz, 50% (30 requests) were made to Static2.t-mobile.cz and 13% (8 requests) were made to Cdn.t-mobile.cz. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.t-mobile.cz.
Page size can be reduced by 593.9 kB (42%)
1.4 MB
814.1 kB
In fact, the total size of T-mobile.cz main page is 1.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. 55% of websites need less resources to load. CSS take 636.2 kB which makes up the majority of the site volume.
Potential reduce by 147.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. This page needs HTML code to be minified as it can gain 27.0 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 147.3 kB or 81% of the original size.
Potential reduce by 1.6 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 6.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. This website has mostly compressed JavaScripts.
Potential reduce by 438.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. T-mobile.cz needs all CSS files to be minified and compressed as it can save up to 438.9 kB or 69% of the original size.
Number of requests can be reduced by 41 (79%)
52
11
The browser has sent 52 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 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
t-mobile.cz
444 ms
osobni
351 ms
custom.css
694 ms
critical.css
595 ms
cookies-blocker.min.js
456 ms
cookies-checker.min.js
460 ms
jquery-1.11.2.js
795 ms
libs.js
794 ms
barebone.jsp
1024 ms
lead-api.min.js
459 ms
vue-axios.min.js
639 ms
polyfill-functions.js
589 ms
ajaxUI.js
728 ms
main.js
729 ms
navigation.js
828 ms
custom-child.css
1482 ms
lcp-style.css
152 ms
lcp-script.js
267 ms
lcp-float-style.css
327 ms
lcp-float-script.js
299 ms
portletStore.js
701 ms
minicart.js
699 ms
ext.js
780 ms
main.js
784 ms
main.js
806 ms
main.js
807 ms
upload.js
811 ms
main.js
956 ms
main-child.js
1130 ms
useberryScript.js
403 ms
main.css
123 ms
vue.css
121 ms
main.css
119 ms
ext.css
119 ms
gtm.js
174 ms
Samsung-Galaxy-A05s-64GB-cerny-detail-big01.jpg
325 ms
Xiaomi-Redmi-13C-5G-128GB-cerny-detail-big01.jpg
385 ms
Motorola-Moto-G54-5G-Power-Edition-tmavomodry-detail-big01.jpg
385 ms
iPhone-13-SE-sedy-detail-big01.jpg
324 ms
iPhone_15_Plus_Pink-detail-big01.jpg
733 ms
teleneo-regular.woff
354 ms
teleneo-regular.woff
353 ms
teleneo-extrabold.woff
132 ms
teleneo-extrabold.woff
702 ms
main.css
134 ms
teleneo-bold.woff
220 ms
teleneo-bold.woff
461 ms
main.css
148 ms
loadNumberOfItems
193 ms
main.css
171 ms
bounce
106 ms
152 ms
osobni
171 ms
sbounce
60 ms
118 ms
available_languages.jsp
115 ms
116 ms
main.css
121 ms
main.css
120 ms
main.css
120 ms
t-mobile.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
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
<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
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
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>).
t-mobile.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
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
t-mobile.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 T-mobile.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 T-mobile.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.
t-mobile.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: