Access handys.t-mobile.at. Handy, Internet, Festnetz, TV uvm.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.909

3/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

handys.t-mobile.at

742 ms

www.t-mobile.at

524 ms

j.php

16 ms

tmobile.buorg.js

257 ms

jquery-1.11.1.min.js

513 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Handys.t-mobile.at, 62% (56 requests) were made to T-mobile.at and 7% (6 requests) were made to Server.lon.liveperson.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source T-mobile.at.

Content Size

2.8 MB

After Optimization

1.2 MB

In fact, the total size of Handys.t-mobile.at main page is 2.8 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. 50% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 276.5 kB

Original 520.3 kB
After minification 517.7 kB
After compression 243.8 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 276.5 kB or 53% of the original size.

Image Optimization

-9%

Potential reduce by 25.2 kB

Original 267.4 kB
After minification 242.1 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. Handy S T Mobile images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 1.1 MB

Original 1.8 MB
After minification 1.7 MB
After compression 674.5 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 1.1 MB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 138.1 kB

Original 159.8 kB
After minification 120.6 kB
After compression 21.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. Handys.t-mobile.at needs all CSS files to be minified and compressed as it can save up to 138.1 kB or 86% of the original size.

Requests Now

After Optimization

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Handy S 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 37 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

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] values are not valid

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

DE
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Handys.t-mobile.at can be misinterpreted by Google and other search engines. Our service has detected that German 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 Handys.t-mobile.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

handys.t-mobile.at

Open Graph description is not detected on the main page of Handy S 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Handy, Internet, Festnetz, TV uvm. | Magenta

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

handys.t-mobile.at

www.t-mobile.at

j.php

tmobile.buorg.js

jquery-1.11.1.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

handys.t-mobile.at

www.t-mobile.at

j.php

tmobile.buorg.js

jquery-1.11.1.min.js

jquery-migrate-1.2.1.min.js

tmobile.core.js

tmobile.overlay.js

tmobile.tgate-auth.js

font_s.css

font-awesome.min.css

tmobile.core.css

tmobile.overlay.css

tmobile.tgate-auth.css

tmobile.content.css

tmobile.teasertracking.js

jquery.fittext.js

tmobile.startseite-fittext.js

tmobile.startseite.css

tmobile.startseite.brand.css

tmobile.startseite.js

ld.js

v.gif

jquery.autoellipsis.js

tmobile.badnet.js

le-mtagconfig.js

loginsidebar_close.png

spinner.gif

74x36_x2_tma_logo.png

19x19_x2_nav_close.png

135x10_tmobile_claim.png

15x15_x2_icons_produkte.png

220x60_quicklinks_consumer_smartphones.png

220x60_quicklinks_consumer_internet.png

220x60_quicklinks_consumer_angebote.png

15x15_x2_icons_service.png

220x60_quicklinks_consumer_fragen.png

220x60_quicklinks_consumer_rechnung.png

15x15_x2_icons_myt.png

220x60_quicklinks_servicebereich.png

220x60_quicklinks_consumer_vertrag.png

220x60_quicklinks_consumer_freieinheiten.png

15x15_x2_icons_login.png