4.4 sec in total
333 ms
3.8 sec
224 ms
Click here to check amazing Sv Uio content for Norway. Otherwise, check out these important facts you probably never knew about sv.uio.no
Vil du lære mer om samfunnet og forholdet mellom mennesker? Studér ved den ledende samfunnsvitenskapelige utdannings- og forskningsinstitusjonen i Norge.
Visit sv.uio.noWe analyzed Sv.uio.no page load time and found that the first response time was 333 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sv.uio.no performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value6.2 s
11/100
25%
Value6.8 s
34/100
10%
Value170 ms
93/100
30%
Value0.367
29/100
15%
Value5.4 s
71/100
10%
333 ms
937 ms
367 ms
221 ms
432 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Sv.uio.no, 5% (3 requests) were made to Vrtx.uio.no and 5% (3 requests) were made to W3prod-ipproxy.uio.no. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Sv.uio.no.
Page size can be reduced by 865.2 kB (69%)
1.2 MB
380.3 kB
In fact, the total size of Sv.uio.no 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. 15% of websites need less resources to load. CSS take 610.1 kB which makes up the majority of the site volume.
Potential reduce by 40.0 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 14.9 kB, which is 31% 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 40.0 kB or 85% of the original size.
Potential reduce by 42.0 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. Obviously, Sv Uio needs image optimization as it can save up to 42.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 244.9 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 244.9 kB or 73% of the original size.
Potential reduce by 538.3 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. Sv.uio.no needs all CSS files to be minified and compressed as it can save up to 538.3 kB or 88% of the original size.
Number of requests can be reduced by 33 (58%)
57
24
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sv Uio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
sv.uio.no
333 ms
www.sv.uio.no
937 ms
style2.css
367 ms
logos.css
221 ms
responsive.css
432 ms
tabletfix-jquery-responsive-libs.js
337 ms
uioGa.js
441 ms
customTracker.js
334 ms
frontpage-override-new.css
216 ms
view-dropdown.js
229 ms
ie10-backsteps-fix.js
366 ms
uio.js
341 ms
urchin.js
452 ms
image-listing-component.css
119 ms
jquery-ui-1.10.3.custom.min.css
115 ms
view-dropdown.css
177 ms
style3.css
312 ms
analytics.js
323 ms
bullet-li-grey.png
112 ms
head-black-gradient.png
223 ms
head-breadcrumb-grey-gradient.png
218 ms
head-breadcrumb-arrow-grey.gif
109 ms
faculty.png
256 ms
form-input-blackbg.png
108 ms
button-small-search-right-blackbg.png
360 ms
button-small-search-left-blackbg.png
359 ms
faculty-small.png
371 ms
form-input.png
335 ms
button-small-search-right.png
445 ms
button-small-search-left.png
982 ms
button-small-left.png
586 ms
button-small-right.png
574 ms
arrow-big-red.gif
467 ms
box-header-black-gradient.png
483 ms
man-bottle-660.jpg
1776 ms
panorama-holmenkollen-90.jpg
835 ms
fn-90px.jpg
752 ms
line-dotted-grey-white-bg.png
684 ms
arrow-small-red.gif
695 ms
line-dotted.gif
772 ms
events-calendar-listing-day-block-bg.png
784 ms
social-list-twitter.png
995 ms
social-list-facebook.png
1026 ms
social-list-youtube.png
1043 ms
breadcrumb-uio-symbol.png
923 ms
breadcrumb-arrow-grey.png
1032 ms
uio-sickle-small.png
1214 ms
dropdown-toggle-white-bg.png
1096 ms
dropdown-white-bg.png
1130 ms
jquery.autocomplete.js
1247 ms
__utm.gif
1111 ms
info-link-close.png
1169 ms
collect
336 ms
collect
336 ms
collect
336 ms
autocomplete-emner.js
117 ms
autocomplete-main.js
114 ms
autocomplete-personer.js
120 ms
print.css
117 ms
sv.uio.no accessibility score
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
sv.uio.no 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
Browser errors were logged to the console
sv.uio.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sv.uio.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Sv.uio.no 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.
sv.uio.no
Open Graph description is not detected on the main page of Sv Uio. 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: