5.8 sec in total
103 ms
4.4 sec
1.3 sec
Visit cr-report.telekom.com now to see the best up-to-date Cr Report Telekom content for Germany and also check out these interesting facts you probably never knew about cr-report.telekom.com
Telekom has provided extensive information to its stakeholders and the general public about its objectives, its activities and the progress made in the relevant economic
Visit cr-report.telekom.comWe analyzed Cr-report.telekom.com page load time and found that the first response time was 103 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cr-report.telekom.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value20.6 s
0/100
25%
Value23.8 s
0/100
10%
Value35,040 ms
0/100
30%
Value0.337
33/100
15%
Value42.7 s
0/100
10%
103 ms
485 ms
200 ms
204 ms
203 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 96% of them (101 requests) were addressed to the original Cr-report.telekom.com, 3% (3 requests) were made to Wtpx-telekom.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cr-report.telekom.com.
Page size can be reduced by 934.0 kB (40%)
2.3 MB
1.4 MB
In fact, the total size of Cr-report.telekom.com main page is 2.3 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 12.3 kB, which is 17% 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 60.5 kB or 83% of the original size.
Potential reduce by 7.8 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. Cr Report Telekom images are well optimized though.
Potential reduce by 527.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 527.0 kB or 69% of the original size.
Potential reduce by 338.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. Cr-report.telekom.com needs all CSS files to be minified and compressed as it can save up to 338.7 kB or 80% of the original size.
Number of requests can be reduced by 75 (73%)
103
28
The browser has sent 103 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 64 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
103 ms
485 ms
css_MPmViSoIx90K1xImMaCe-ONnwobGcjKIeXSMCaNNR7A.css
200 ms
css_yX3LiAZ1oGag59T59sJ_Vxy3-lRKQ0_XX_E0IAD6XDY.css
204 ms
css_4-1CHh7dtra3SMwGd42Iy5tv43i2h_TTbDpGyrF4RA0.css
203 ms
css_HXR9EeVRUAi2REIbvOmzYs3iQNCaYYCj4E5SGoZCkI0.css
402 ms
css_jVbKt1wEH3JGDbwIinbE5NoFRS7rkeqrIiNdOEORM3I.css
503 ms
jquery.min.js
823 ms
jquery-migrate-1.2.1.min.js
9 ms
jquery.once.js
300 ms
drupal.js
305 ms
jquery.ui.core.min.js
304 ms
jquery.ui.widget.min.js
403 ms
jquery.ui.button.min.js
405 ms
jquery.ui.mouse.min.js
406 ms
jquery.ui.draggable.min.js
518 ms
jquery.ui.position.min.js
518 ms
jquery.ui.resizable.min.js
519 ms
jquery.ui.dialog.min.js
518 ms
jquery.ui.tabs.min.js
604 ms
jquery.ui.tooltip.min.js
604 ms
jquery.ui.accordion.min.js
606 ms
jquery.ba-bbq.js
609 ms
ajax.js
613 ms
jquery_update.js
704 ms
admin_devel.js
705 ms
drupal_trs_extended.js
707 ms
highcharts.js
1032 ms
highcharts-more.js
716 ms
exporting.js
806 ms
jquery.colorbox-min.js
808 ms
colorbox.js
808 ms
favorite_node.js
856 ms
panels.js
907 ms
progress.js
909 ms
recherche_tool_comments.js
910 ms
recherche_tool_editor.js
919 ms
recherche_tool_export.js
918 ms
recherche_tool_overlay.js
920 ms
shortcuts.js
819 ms
recherche_tool_tasks.js
815 ms
detectmobilebrowser.min.js
824 ms
jquery.mobile.custom.min.js
728 ms
modernizr.custom.63629.js
816 ms
dti.js
814 ms
dtg.js
824 ms
respond.min.js
751 ms
bootstrap-sprockets.js
747 ms
bootstrap.min.js
748 ms
jquery.ba-resize.min.js
703 ms
jquery.smooth-scroll.min.js
704 ms
jquery.vide.min.js
714 ms
fixto.min.js
714 ms
isotope.pkgd.min.js
730 ms
viewport-units-buggyfill.js
719 ms
jquery.zoom.min.js
720 ms
jquery.cookie.js
720 ms
waypoints.js
725 ms
jquery.matchHeight.min.js
720 ms
json2html.min.js
645 ms
jquery.json2html.min.js
718 ms
stakeholder-erwartungen.min.js
717 ms
materiality-matrizen.min.js
710 ms
jquery.socialshareprivacy.min.js
629 ms
plugins.min.js
625 ms
swfobject.js
643 ms
scripts.min.js
670 ms
landingpage.min.js
669 ms
waypoints.min.js
622 ms
jquery.stellar.js
627 ms
logo.png
103 ms
search_icon.png
103 ms
navi_arrow.png
104 ms
philipp_riederle_0257.jpg
502 ms
dark-gradient-50.png
104 ms
Testimony_Underline.png
105 ms
arrow_blue_down.png
204 ms
wtid.js
359 ms
ipa.php
362 ms
TeleGroteskNormal.woff
481 ms
TeleGroteskHalbfett.woff
405 ms
glyphicons-halflings-regular.woff
281 ms
TeleGroteskFett.woff
406 ms
startsite-story-tempid-1
272 ms
dcs.gif
120 ms
raute_1l_small.jpg
304 ms
raute_1r_small.jpg
202 ms
raute_2l_small.jpg
203 ms
raute_2r_small.jpg
204 ms
raute_3l_small.jpg
302 ms
raute_3r_small.jpg
202 ms
hoettges_neu.jpg
1205 ms
map_germany.png
304 ms
map_lines.png
305 ms
arrow-right-white.png
306 ms
cybersecurity_small.jpg
703 ms
flip_edge_2.png
405 ms
2Flip_MagentaMOOC.jpg
804 ms
flip_sozialtarife.jpg
504 ms
medienpaedagogik.jpg
806 ms
ichkannwas.jpg
1005 ms
story_digitale_sicherheit.jpg
1006 ms
van_abel_small.jpg
804 ms
geiger_small.jpg
905 ms
css_-wVm8uRP2MF6QcTrjGXgLh8bFoCkLgE4zuebBOWFem4.css
105 ms
cr-report.telekom.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cr-report.telekom.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
cr-report.telekom.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
cr-report.telekom.com
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: