4 sec in total
650 ms
2.5 sec
840 ms
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.atWe analyzed Build.or.at page load time and found that the first response time was 650 ms and then it took 3.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.
build.or.at performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value16.3 s
0/100
25%
Value12.6 s
3/100
10%
Value2,070 ms
7/100
30%
Value0.072
96/100
15%
Value16.4 s
5/100
10%
650 ms
136 ms
216 ms
377 ms
256 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 83% of them (38 requests) were addressed to the original Build.or.at, 9% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Build.or.at.
Page size can be reduced by 424.3 kB (31%)
1.4 MB
941.5 kB
In fact, the total size of Build.or.at 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. 45% of websites need less resources to load. Images take 825.4 kB which makes up the majority of the site volume.
Potential reduce by 34.7 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 34.7 kB or 80% of the original size.
Potential reduce by 25.5 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.
Potential reduce by 231.5 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 231.5 kB or 67% of the original size.
Potential reduce by 132.5 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. Build.or.at needs all CSS files to be minified and compressed as it can save up to 132.5 kB or 87% of the original size.
Number of requests can be reduced by 25 (61%)
41
16
The browser has sent 41 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 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
build.or.at
650 ms
style.css
136 ms
responsive.css
216 ms
build.or.at
377 ms
cli-style.css
256 ms
prettyPhoto.css
257 ms
jquery.js
327 ms
jquery-migrate.min.js
261 ms
scrollTo.js
317 ms
jquery.form.min.js
318 ms
mailchimp.js
318 ms
cookielawinfo.js
343 ms
style-custom.css
467 ms
jquery.jplayer.min.js
493 ms
jquery.omslider.min.js
491 ms
libraries.js
493 ms
jquery.isotope.min.js
494 ms
jquery.validate.min.js
497 ms
jquery.form.min.js
516 ms
jquery.hoverIntent.js
513 ms
jquery.superfish.js
516 ms
custom.js
521 ms
jquery.prettyPhoto.js
529 ms
wp-embed.min.js
880 ms
wp-emoji-release.min.js
663 ms
ga.js
46 ms
__utm.gif
254 ms
css
71 ms
css
102 ms
bg4.jpg
1176 ms
buildlogo1.png
250 ms
Foto_ber-uns_Netzwerk_GesellschafterInnen-e1386594977343-1024x524-480x328.jpg
752 ms
Prsentation1-3-480x328.jpg
321 ms
homepageslider-10-480x328.jpg
214 ms
Prsentation1-480x328.jpg
245 ms
hpsliderharmonyandcare-480x328.jpg
385 ms
li.png
386 ms
aplusb.png
387 ms
icon-facebook.png
736 ms
icon-xing.png
733 ms
icon-rss.png
736 ms
overlay.png
737 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
91 ms
wkfQbvfT_02e2IWO3yYueQ.woff
92 ms
oUan5VrEkpzIazlUe5ieaA.woff
92 ms
HkF_qI1x_noxlxhrhMQYED8E0i7KZn-EPnyo3HZu7kw.woff
93 ms
build.or.at accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
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
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
build.or.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
build.or.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
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.
build.or.at
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: