Report Summary

  • 1

    Performance

    Renders faster than
    29% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    62% of websites

t-mobile.sk

Mobilné telefóny, Paušály, Magio Internet a Televízia - Telekom

Page Load Speed

13.7 sec in total

First Response

643 ms

Resources Loaded

12.8 sec

Page Rendered

273 ms

t-mobile.sk screenshot

About Website

Welcome to t-mobile.sk homepage info - get ready to check T Mobile best content for United States right away, or after learning these important things about t-mobile.sk

Mobilné telefóny, Paušály, Magio Internet a Televízia od spoločnosti Telekom

Visit t-mobile.sk

Key Findings

We analyzed T-mobile.sk page load time and found that the first response time was 643 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

t-mobile.sk performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value4,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.953

3/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

www.telekom.sk

643 ms

main.css

143 ms

main.css

260 ms

barebone.jsp

2537 ms

main.css

619 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original T-mobile.sk, 3% (3 requests) were made to Google-analytics.com and 3% (3 requests) were made to Sk.hit.gemius.pl. The less responsive or slowest element that took the longest time to load (9.3 sec) relates to the external source Telekom.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 901.1 kB (65%)

Content Size

1.4 MB

After Optimization

484.3 kB

In fact, the total size of T-mobile.sk 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. 35% of websites need less resources to load. CSS take 657.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 52.6 kB

  • Original 67.1 kB
  • After minification 67.0 kB
  • After compression 14.5 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 52.6 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 25.3 kB

  • Original 268.9 kB
  • After minification 243.7 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.

JavaScript Optimization

-69%

Potential reduce by 271.6 kB

  • Original 391.5 kB
  • After minification 357.6 kB
  • After compression 120.0 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 271.6 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 551.7 kB

  • Original 657.7 kB
  • After minification 656.4 kB
  • After compression 106.1 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.sk needs all CSS files to be minified and compressed as it can save up to 551.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (55%)

Requests Now

80

After Optimization

36

The browser has sent 80 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 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

t-mobile.sk accessibility score

71

Accessibility Issues

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

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

SEO Factors

t-mobile.sk SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SK

  • Language Claimed

    SK

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise T-mobile.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that T-mobile.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.

Social Sharing Optimization

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: