Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

atp.ag

Integrale Planung – Integrale Planung ATP architekten ingenieure

Page Load Speed

4 sec in total

First Response

303 ms

Resources Loaded

3.4 sec

Page Rendered

242 ms

atp.ag screenshot

About Website

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

Ohne Integrale Planung kein nachhaltiges Gebäude, das Ergebnis der Integralen Planung von ATP ist ein optimales Gebäude im Sinne der Zielsetzungen des Bauherrn und der Nutzer.

Visit atp.ag

Key Findings

We analyzed Atp.ag page load time and found that the first response time was 303 ms and then it took 3.7 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

atp.ag performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.144

77/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

atp.ag

303 ms

atp.ag

381 ms

www.atp.ag

253 ms

www.atp.ag

375 ms

538 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 64% of them (36 requests) were addressed to the original Atp.ag, 11% (6 requests) were made to Static.clickskeks.at and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Atp.ag.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.6 kB (8%)

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of Atp.ag main page is 1.2 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 797.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 96.3 kB

  • Original 115.8 kB
  • After minification 95.8 kB
  • After compression 19.4 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 20.0 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 96.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 96 B

  • Original 797.7 kB
  • After minification 797.6 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. ATP images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 130 B

  • Original 201.9 kB
  • After minification 201.9 kB
  • After compression 201.8 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

-0%

Potential reduce by 15 B

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 37.9 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. Atp.ag has all CSS files already compressed.

Requests Breakdown

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

Requests Now

47

After Optimization

24

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ATP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

atp.ag accessibility score

84

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

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

atp.ag 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

atp.ag SEO score

68

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

High

Document doesn't have a valid hreflang

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 Atp.ag 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 Atp.ag 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 ATP. 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: