Tools & Wizards About Us
auditas.de screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

auditas.de

Online Shop für Telekom Profis - Telekom Profis

Page Load Speed

3.4 sec in total

First Response

338 ms

Resources Loaded

2.8 sec

Page Rendered

202 ms

auditas.de screenshot

About Website

Click here to check amazing Auditas content. Otherwise, check out these important facts you probably never knew about auditas.de

Als Telekom Profi können Sie in unserem Online-Shop alle Telekom Produkte für ihre Bekannten, Geschäftspartner und sich selbst bestellen. Mit nur wenigen Klicks

Visit auditas.de

Key Findings

We analyzed Auditas.de page load time and found that the first response time was 338 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

auditas.de performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value3,440 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value29.4 s

0/100

10%

Network Requests Diagram

auditas.de

338 ms

index.html

540 ms

jMenu.jquery.css

103 ms

normalize.css

199 ms

standards.css

228 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Auditas.de, 89% (48 requests) were made to Telekom-profis.de and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (743 ms) relates to the external source Telekom-profis.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.3 kB (37%)

Content Size

1.4 MB

After Optimization

880.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Auditas.de 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. 60% of websites need less resources to load. Images take 760.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 22.9 kB

  • Original 29.8 kB
  • After minification 26.0 kB
  • After compression 6.9 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 3.8 kB, which is 13% 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 22.9 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 19.7 kB

  • Original 760.0 kB
  • After minification 740.3 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. Auditas images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 35.7 kB

  • Original 88.4 kB
  • After minification 88.4 kB
  • After compression 52.6 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 35.7 kB or 40% of the original size.

CSS Optimization

-84%

Potential reduce by 437.0 kB

  • Original 517.5 kB
  • After minification 481.0 kB
  • After compression 80.6 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. Auditas.de needs all CSS files to be minified and compressed as it can save up to 437.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (23%)

Requests Now

47

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

auditas.de

auditas.de

338 ms

index.html

index.html

540 ms

jMenu.jquery.css

jMenu.jquery.css

103 ms

normalize.css

normalize.css

199 ms

standards.css

standards.css

228 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

197 ms

dtag.min.js

dtag.min.js

414 ms

jquery.min.js

jquery.min.js

13 ms

jMenu.jquery.js

jMenu.jquery.js

205 ms

standard.js

standard.js

241 ms

webtrekk_v3.js

webtrekk_v3.js

297 ms

bootstrap.min.css

bootstrap.min.css

392 ms

highslide-full.js

highslide-full.js

410 ms

jquery.bxslider.css

jquery.bxslider.css

320 ms

highslide.css

highslide.css

342 ms

jquery.min.js

jquery.min.js

34 ms

bootstrap.min.js

bootstrap.min.js

392 ms

bootstrap.min.css

bootstrap.min.css

516 ms

jquery.bxslider4.min.js

jquery.bxslider4.min.js

442 ms

jquery.simpleplaceholder.js

jquery.simpleplaceholder.js

485 ms

jquery.scrollTo-1.4.3.1-min.js

jquery.scrollTo-1.4.3.1-min.js

487 ms

jquery.localscroll-1.2.7-min.js

jquery.localscroll-1.2.7-min.js

508 ms

purl.js

purl.js

509 ms

tpr.js

tpr.js

743 ms

fn3.js

fn3.js

580 ms

fnHomeModal.js

fnHomeModal.js

581 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

608 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

608 ms

portal.css

portal.css

399 ms

logo_tp-pso.gif

logo_tp-pso.gif

112 ms

logo_erleben.gif

logo_erleben.gif

111 ms

teaser_fitness_1170.jpg

teaser_fitness_1170.jpg

586 ms

teaser_fitness_720.jpg

teaser_fitness_720.jpg

586 ms

handy_bild_1231.gif

handy_bild_1231.gif

112 ms

handy_bild_1249.gif

handy_bild_1249.gif

158 ms

handy_bild_1073.gif

handy_bild_1073.gif

194 ms

handy_bild_1280.gif

handy_bild_1280.gif

204 ms

0,3465,235934,00.png

0,3465,235934,00.png

406 ms

list_dot.gif

list_dot.gif

262 ms

teaser_smarthome_770x294.jpg

teaser_smarthome_770x294.jpg

484 ms

teaser_smarthome_720x370.jpg

teaser_smarthome_720x370.jpg

416 ms

teaser_galaxyS7_Shop_Startseite_Kachel.jpg

teaser_galaxyS7_Shop_Startseite_Kachel.jpg

565 ms

teaser_galaxyA5_Shop_Startseite_Kachel.jpg

teaser_galaxyA5_Shop_Startseite_Kachel.jpg

608 ms

twitter.gif

twitter.gif

517 ms

banner-right.png

banner-right.png

584 ms

piwik.js

piwik.js

328 ms

wt

wt

542 ms

fussnoten2.html

fussnoten2.html

587 ms

handy_bild_1231.gif

handy_bild_1231.gif

528 ms

handy_bild_1249.gif

handy_bild_1249.gif

431 ms

handy_bild_1073.gif

handy_bild_1073.gif

534 ms

handy_bild_1280.gif

handy_bild_1280.gif

435 ms

piwik.js

piwik.js

540 ms

leer.gif

leer.gif

103 ms

Accessibility Review

auditas.de accessibility score

80

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

auditas.de best practices score

83

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

Page has valid source maps

SEO Factors

auditas.de SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auditas.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Auditas.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

auditas.de

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