44 sec in total
1.4 sec
42.3 sec
202 ms
Welcome to t-mobile.cp.sk homepage info - get ready to check T Mobile CP best content for Slovakia right away, or after learning these important things about t-mobile.cp.sk
CP umožňuje vyhľadanie spojení v cestovných poriadkoch vlakov, autobusov, MHD a lietadiel. Vyhľadáva spojenia rôznych dopravcov a zobrazuje aktuálne polohy vlakov a autobusov. Pre vyhľadané spojenie j...
Visit t-mobile.cp.skWe analyzed T-mobile.cp.sk page load time and found that the first response time was 1.4 sec and then it took 42.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
t-mobile.cp.sk performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value13.4 s
0/100
25%
Value14.8 s
1/100
10%
Value3,440 ms
2/100
30%
Value0.098
90/100
15%
Value24.4 s
0/100
10%
1449 ms
611 ms
574 ms
533 ms
408 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original T-mobile.cp.sk, 53% (37 requests) were made to Cp.atlas.sk and 10% (7 requests) were made to Bbnaut.ibillboard.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Static.mediacentrum.sk.
Page size can be reduced by 424.2 kB (69%)
616.5 kB
192.4 kB
In fact, the total size of T-mobile.cp.sk main page is 616.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 507.3 kB which makes up the majority of the site volume.
Potential reduce by 24.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 24.2 kB or 70% of the original size.
Potential reduce by 5.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. Obviously, T Mobile CP needs image optimization as it can save up to 5.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 351.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 351.3 kB or 69% of the original size.
Potential reduce by 43.7 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.cp.sk needs all CSS files to be minified and compressed as it can save up to 43.7 kB or 78% of the original size.
Number of requests can be reduced by 44 (71%)
62
18
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of T Mobile CP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
t-mobile.cp.sk
1449 ms
cp.atlas.sk
611 ms
574 ms
IdosResource.ashx
533 ms
IdosResource.ashx
408 ms
IdosResource.ashx
546 ms
IdosResource.ashx
544 ms
IdosResource.ashx
283 ms
IdosResource.ashx
690 ms
IdosResource.ashx
530 ms
IdosResource.ashx
542 ms
cookieconsent.min.js
19991 ms
conversion.js
41 ms
IdosResource.ashx
254 ms
IdosResource.ashx
272 ms
bb_one2n.js
234 ms
bb_one2n.113.65.77.1.js
586 ms
IdosResource.ashx
132 ms
cp2.gif
163 ms
atlas_logo2.png
162 ms
logo-cpsk.gif
162 ms
btn-help.png
160 ms
btn-info.png
161 ms
_VlakBusSk_0.png
157 ms
empty.png
297 ms
btn-up.png
297 ms
btn-down.png
298 ms
btn-calendar.png
300 ms
142 ms
19959 ms
header-link.png
262 ms
header_atlas_repeat.png
262 ms
bg-tab-active.png
389 ms
bg-tab.png
390 ms
bg-tab-inactive.png
391 ms
bg-tab-inactive-orange.png
404 ms
ico-news.png
405 ms
ico-help.png
403 ms
btn-sprites.png
567 ms
btn-jr-select.png
568 ms
all-sprites.gif
581 ms
bg-btn-search.png
584 ms
bg-content-footer.png
584 ms
ajax-loader.gif
583 ms
h.php
912 ms
xgemius.js
422 ms
analytics.js
106 ms
bbnaut-lib-1.7.5.min.js
409 ms
82 ms
collect
26 ms
407 ms
fpdata.js
180 ms
lsget.html
308 ms
creative-lib-1.02.23.min.js
612 ms
in-page-script-1.02.js
396 ms
xgde.js
1385 ms
rexdot.js
273 ms
co
266 ms
CP_roaming_banner_300x300.jpg
547 ms
xgde.html
233 ms
gemius.js
119 ms
fpdata.js
116 ms
et2
232 ms
redot.js
122 ms
inscreen_lib.js
242 ms
ca2
0 ms
PremiumDsp
375 ms
BBID-01-01348383267152385
378 ms
BBID-01-01348383267152385
375 ms
ca2
275 ms
t-mobile.cp.sk accessibility score
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
<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.
t-mobile.cp.sk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
t-mobile.cp.sk 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
SK
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise T-mobile.cp.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that T-mobile.cp.sk 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.cp.sk
Open Graph description is not detected on the main page of T Mobile CP. 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: