Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

build.or.at

build! Gründerzentrum

Page Load Speed

5.1 sec in total

First Response

362 ms

Resources Loaded

4.2 sec

Page Rendered

592 ms

About Website

Visit build.or.at now to see the best up-to-date Build content for Austria and also check out these interesting facts you probably never knew about build.or.at

Das build! Gründerzentrum Kärnten fördert innovative Unternehmensgründungen und unterstützt die Gründer*innen auf dem zur Selbstständigkeit.

Visit build.or.at

Key Findings

We analyzed Build.or.at page load time and found that the first response time was 362 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

build.or.at performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

build.or.at

362 ms

build.or.at

681 ms

ae7e54f8_ai1ec_parsed_css.css

544 ms

cv.css

554 ms

cvpro.min.css

448 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 99% of them (125 requests) were addressed to the original Build.or.at, 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Build.or.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 259.3 kB (42%)

Content Size

616.2 kB

After Optimization

356.9 kB

  • HTML
  • Images

In fact, the total size of Build.or.at main page is 616.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 316.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 259.3 kB

  • Original 316.4 kB
  • After minification 313.6 kB
  • After compression 57.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. 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 259.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 39 B

  • Original 299.8 kB
  • After minification 299.7 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. Build images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 78 (70%)

Requests Now

112

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

build.or.at accessibility score

79

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

build.or.at best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

build.or.at SEO score

84

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

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 uses 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 Build.or.at 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 Build.or.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

Open Graph data is detected on the main page of Build. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: