41.6 sec in total
2.1 sec
28.2 sec
11.2 sec
Visit oehweb.at now to see the best up-to-date Oehweb content for Austria and also check out these interesting facts you probably never knew about oehweb.at
Wir sind die ÖH an der Universität Innsbruck und vertreten die Interessen aller Studierenden der Universität Innsbruck.
Visit oehweb.atWe analyzed Oehweb.at page load time and found that the first response time was 2.1 sec and then it took 39.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
oehweb.at performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value15.2 s
0/100
25%
Value11.5 s
5/100
10%
Value700 ms
42/100
30%
Value0.015
100/100
15%
Value13.9 s
10/100
10%
2087 ms
700 ms
594 ms
902 ms
592 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 79% of them (48 requests) were addressed to the original Oehweb.at, 7% (4 requests) were made to Maps.googleapis.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Google-analytics.com.
Page size can be reduced by 2.0 MB (53%)
3.8 MB
1.8 MB
In fact, the total size of Oehweb.at main page is 3.8 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. 80% 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 66.8 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 66.8 kB or 82% of the original size.
Potential reduce by 42.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. Oehweb images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 66% of the original size.
Potential reduce by 874.1 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. Oehweb.at needs all CSS files to be minified and compressed as it can save up to 874.1 kB or 87% of the original size.
Number of requests can be reduced by 44 (76%)
58
14
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oehweb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.oehweb.at
2087 ms
wp-emoji-release.min.js
700 ms
layerslider.css
594 ms
layerslider.custom.css
902 ms
css
592 ms
bbpress.css
902 ms
styles.css
593 ms
settings.css
896 ms
style.min.css
1740 ms
style.css
928 ms
font-awesome.css
928 ms
ilightbox.css
1022 ms
animations.css
1279 ms
bbpress.css
1087 ms
fusion-shortcodes.min.css
2592 ms
avada-17.css
1083 ms
wpjb-glyphs.css
1004 ms
frontend.css
2290 ms
css
3016 ms
wpcufpn_front.css
2558 ms
css
2982 ms
greensock.js
2921 ms
jquery.js
2690 ms
jquery-migrate.min.js
2689 ms
layerslider.kreaturamedia.jquery.js
2689 ms
layerslider.transitions.js
2689 ms
frontend.min.js
2978 ms
jquery.themepunch.tools.min.js
2979 ms
jquery.themepunch.revolution.min.js
2978 ms
frontend.js
2978 ms
js
2833 ms
infobox_packed.js
2886 ms
editor.js
2887 ms
jquery.form.min.js
4371 ms
scripts.js
4370 ms
comment-reply.min.js
4369 ms
main.min.js
4372 ms
js
2842 ms
maps.js
4326 ms
jquery.selectlist.pack.js
4324 ms
wp-embed.min.js
4326 ms
analytics.js
1056 ms
linkid.js
291 ms
collect
888 ms
collect
1108 ms
OeH_Logo_100x55.png
875 ms
icon2.png
906 ms
icon1.png
899 ms
icon-03.png
712 ms
4Dengg2017-205x300.jpg
899 ms
5Sparkasse2017-205x300.gif
901 ms
1BioLife2017.gif
894 ms
15032528_1232464653443134_473781582_n.jpg
834 ms
mensa_icon.jpg
835 ms
icon_rechts.png
835 ms
icomoon.ttf
1080 ms
fontawesome-webfont.woff
340 ms
common.js
50 ms
util.js
34 ms
stats.js
14 ms
analytics.js
5950 ms
oehweb.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
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.
oehweb.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
oehweb.at SEO score
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 Oehweb.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 Oehweb.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.
oehweb.at
Open Graph data is detected on the main page of Oehweb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: