Tools & Wizards About Us

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

tmobile.at

Handy, Internet, Festnetz, TV uvm. | Magenta

Page Load Speed

4.1 sec in total

First Response

594 ms

Resources Loaded

3.3 sec

Page Rendered

211 ms

About Website

Visit tmobile.at now to see the best up-to-date Tmobile content for Austria and also check out these interesting facts you probably never knew about tmobile.at

Entdecke unsere Magenta Angebote für Internet, Fernsehen, Mobilfunknetz uvm. Für Zuhause und Geschäftskunden. Wir sind Magenta!

Visit tmobile.at

Key Findings

We analyzed Tmobile.at page load time and found that the first response time was 594 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tmobile.at performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value6,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

tmobile.at

594 ms

www.magenta.at

798 ms

bundle.js

23 ms

gtm.js

906 ms

clientlib-base.min.c504cc427271c61fc813ac773ef02f92.css

231 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Tmobile.at, 84% (31 requests) were made to Magenta.at and 5% (2 requests) were made to Sst.magenta.at. The less responsive or slowest element that took the longest time to load (906 ms) relates to the external source Sst.magenta.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 274.1 kB (49%)

Content Size

557.0 kB

After Optimization

283.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tmobile.at main page is 557.0 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. 45% of websites need less resources to load. HTML takes 297.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 266.9 kB

  • Original 297.5 kB
  • After minification 256.8 kB
  • After compression 30.6 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 40.7 kB, which is 14% 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 266.9 kB or 90% of the original size.

Image Optimization

-19%

Potential reduce by 6.6 kB

  • Original 34.8 kB
  • After minification 28.2 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 6.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 444 B

  • Original 223.7 kB
  • After minification 223.7 kB
  • After compression 223.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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 119 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 888 B

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.at needs all CSS files to be minified and compressed as it can save up to 119 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (54%)

Requests Now

24

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

tmobile.at accessibility score

52

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

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

High

[role] values are not valid

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tmobile.at best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tmobile.at SEO score

78

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tmobile.at 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.at 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 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: