5.1 sec in total
362 ms
4.2 sec
592 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 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.
build.or.at performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value15.0 s
0/100
25%
Value17.9 s
0/100
10%
Value2,960 ms
3/100
30%
Value0.063
97/100
15%
Value17.0 s
4/100
10%
362 ms
681 ms
544 ms
554 ms
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 size can be reduced by 259.3 kB (42%)
616.2 kB
356.9 kB
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.
Potential reduce by 259.3 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.
Potential reduce by 39 B
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.
Number of requests can be reduced by 78 (70%)
112
34
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.
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
block-style.css
350 ms
styles.css
423 ms
team.min.css
533 ms
genericons.css
599 ms
bg-show-hide.css
539 ms
style.min.css
560 ms
rss-retriever.css
648 ms
cff-style.min.css
660 ms
style.min.css
655 ms
ctl-common-styles.min.css
677 ms
frontend.css
674 ms
be.css
837 ms
animations.min.css
760 ms
fontawesome.css
773 ms
jplayer.blue.monday.min.css
778 ms
responsive.css
797 ms
borlabs-cookie-1-de.css
806 ms
js_composer.min.css
1013 ms
style.css
779 ms
jquery.min.js
788 ms
jquery-migrate.min.js
804 ms
jquery.easy-ticker.min.js
805 ms
script.min.js
835 ms
frontend.js
888 ms
borlabs-cookie-config-de.json.js
971 ms
borlabs-cookie-prioritize.min.js
894 ms
borlabs-cookie.min.js
893 ms
omgf-stylesheet-123.css
895 ms
animate.min.css
972 ms
glightbox.min.css
973 ms
all.min.css
974 ms
v4-shims.min.css
975 ms
swiper.min.css
974 ms
aos.css
899 ms
ctl-vertical-timeline.min.css
824 ms
post-2.css
802 ms
dashicons.min.css
800 ms
display-structure.css
798 ms
rs6.css
789 ms
team.min.js
785 ms
cv.js
1179 ms
cvpro.min.js
1139 ms
rbtools.min.js
1095 ms
rs6.min.js
1090 ms
effect.min.js
1074 ms
effect-slide.min.js
1064 ms
effect-highlight.min.js
1062 ms
effect-fold.min.js
977 ms
effect-blind.min.js
963 ms
bg-show-hide.js
963 ms
core.min.js
944 ms
tabs.min.js
934 ms
debouncedresize.min.js
878 ms
magnificpopup.min.js
859 ms
menu.js
846 ms
visible.min.js
829 ms
animations.min.js
829 ms
jplayer.min.js
817 ms
enllax.min.js
764 ms
translate3d.js
683 ms
scripts.js
659 ms
revolution.addon.typewriter.min.js
1337 ms
js_composer_front.min.js
725 ms
vc-waypoints.min.js
957 ms
jquery.glightbox.min.js
690 ms
swiper.min.js
958 ms
aos.js
684 ms
ctl-common.js
952 ms
ctl-vertical.js
953 ms
waypoints.min.js
896 ms
chart.min.js
895 ms
countdown.min.js
898 ms
wACeNpjYGBgZACCyzpaHiD6SsBNAyhtCAA5XgXOAA==
1 ms
underscore.min.js
817 ms
backbone.min.js
822 ms
front-end-deps.js
826 ms
front-end.js
824 ms
lazyload.min.js
447 ms
PT_Sans-Web-Regular.ttf
708 ms
PT_Sans-Web-Bold.ttf
865 ms
icons.woff
706 ms
Genericons.svg
703 ms
dummy.png
703 ms
team-hg.jpg
803 ms
BUILD_logo_4c_NEG.png
288 ms
build-gruenderzentrum-logo-sticky.png
129 ms
build-gruenderzentrum-logo.png
130 ms
circle.svg
255 ms
team.jpg
287 ms
build-icon-bulb.png
208 ms
build-icon-arrow.png
267 ms
build-icon-rockets.png
266 ms
build-icon-b.png
329 ms
build-icon-thumbs.png
365 ms
presenter-black.svg
233 ms
whistle-black.svg
230 ms
communities-black.svg
232 ms
mentor-black.svg
233 ms
piggy-bank-black.svg
232 ms
round-table-black.svg
233 ms
big-data-black.svg
352 ms
working.svg
352 ms
fh-kaernten-logo.png
394 ms
tu-graz.png
395 ms
klagenfurt-logo.png
417 ms
UNI_LOGO_positiv_2021.jpg
417 ms
stadt-villach.png
443 ms
babeg-logo.png
467 ms
KWF_FE_white_300px.png
504 ms
carinthia-location-hellblau-white.svg
519 ms
de.png
528 ms
en.png
532 ms
bct-google-recaptcha-main.png
551 ms
whistle-black.svg
373 ms
presenter-black.svg
389 ms
communities-black.svg
412 ms
piggy-bank-black.svg
422 ms
mentor-black.svg
427 ms
round-table-black.svg
436 ms
big-data-black.svg
364 ms
working.svg
421 ms
build.or.at 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
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
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
Page has valid source maps
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: