Access cr-report.telekom.com. Home | 2022 Corporate Responsibility Report

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

cr-report.telekom.com

317 ms

www.cr-report.telekom.com

523 ms

326 ms

light.css

220 ms

tgd-interactive-diagram.min.js

478 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 77% of them (17 requests) were addressed to the original Cr-report.telekom.com, 9% (2 requests) were made to Fastly.jsdelivr.net and 5% (1 request) were made to Ga.jspm.io. The less responsive or slowest element that took the longest time to load (956 ms) belongs to the original domain Cr-report.telekom.com.

Content Size

569.7 kB

After Optimization

159.2 kB

In fact, the total size of Cr-report.telekom.com main page is 569.7 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. 25% of websites need less resources to load. CSS take 324.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 69.2 kB

Original 78.4 kB
After minification 49.7 kB
After compression 9.1 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 28.6 kB, which is 37% 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 69.2 kB or 88% of the original size.

JavaScript Optimization

-31%

Potential reduce by 51.4 kB

Original 167.4 kB
After minification 167.4 kB
After compression 115.9 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 51.4 kB or 31% of the original size.

CSS Optimization

-89%

Potential reduce by 289.9 kB

Original 324.0 kB
After minification 255.6 kB
After compression 34.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. Cr-report.telekom.com needs all CSS files to be minified and compressed as it can save up to 289.9 kB or 89% of the original size.

Requests Now

After Optimization

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cr Report Telekom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts 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

[aria-*] attributes do not match their roles

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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 uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cr-report.telekom.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cr-report.telekom.com 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 Cr Report Telekom. 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: