5 sec in total
337 ms
4.4 sec
237 ms
Visit sum.uio.no now to see the best up-to-date Sum Uio content for Norway and also check out these interesting facts you probably never knew about sum.uio.no
Visit sum.uio.noWe analyzed Sum.uio.no page load time and found that the first response time was 337 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.
sum.uio.no performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value12.7 s
0/100
25%
Value8.2 s
20/100
10%
Value300 ms
78/100
30%
Value0.381
27/100
15%
Value8.3 s
39/100
10%
337 ms
1746 ms
113 ms
218 ms
326 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 91% of them (53 requests) were addressed to the original Sum.uio.no, 5% (3 requests) were made to Vrtx.uio.no and 3% (2 requests) were made to W3prod-ipproxy.uio.no. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Sum.uio.no.
Page size can be reduced by 831.8 kB (75%)
1.1 MB
270.6 kB
In fact, the total size of Sum.uio.no main page is 1.1 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. 30% of websites need less resources to load. CSS take 599.9 kB which makes up the majority of the site volume.
Potential reduce by 36.6 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.6 kB, which is 34% 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 36.6 kB or 85% of the original size.
Potential reduce by 21.3 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, Sum Uio needs image optimization as it can save up to 21.3 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 528.9 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. Sum.uio.no needs all CSS files to be minified and compressed as it can save up to 528.9 kB or 88% of the original size.
Number of requests can be reduced by 31 (56%)
55
24
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sum 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.
sum.uio.no
337 ms
www.sum.uio.no
1746 ms
style2.css
113 ms
logos.css
218 ms
responsive.css
326 ms
tabletfix-jquery-responsive-libs.js
337 ms
uioGa.js
434 ms
customTracker.js
335 ms
frontpage-override-new.css
220 ms
view-dropdown.js
334 ms
ie10-backsteps-fix.js
225 ms
uio.js
431 ms
urchin.js
331 ms
image-listing-component.css
230 ms
jquery-ui-1.10.3.custom.min.css
324 ms
view-dropdown.css
329 ms
style3.css
591 ms
analytics.js
323 ms
bullet-li-grey.png
114 ms
head-black-gradient.png
252 ms
head-breadcrumb-grey-gradient.png
259 ms
head-breadcrumb-arrow-grey.gif
117 ms
faculty.png
256 ms
form-input-blackbg.png
116 ms
button-small-search-right-blackbg.png
362 ms
button-small-search-left-blackbg.png
373 ms
faculty-small.png
373 ms
form-input.png
359 ms
button-small-search-right.png
509 ms
button-small-search-left.png
539 ms
student2.jpg
826 ms
box-header-black-gradient.png
468 ms
forum-for-forside.jpg
863 ms
fao-90x90.jpg
642 ms
malawi-road.jpg
726 ms
line-dotted-grey-white-bg.png
617 ms
arrow-small-red.gif
660 ms
forumfordevstudies.gif
729 ms
line-dotted.gif
726 ms
events-calendar-listing-day-block-bg.png
745 ms
newsletter.jpg
956 ms
social-list-facebook.png
952 ms
social-list-twitter.png
984 ms
breadcrumb-uio-symbol.png
854 ms
breadcrumb-arrow-grey.png
903 ms
uio-sickle-small.png
1091 ms
dropdown-toggle-white-bg.png
954 ms
dropdown-white-bg.png
999 ms
jquery.autocomplete.js
1016 ms
__utm.gif
995 ms
info-link-close.png
1002 ms
collect
329 ms
collect
326 ms
forumfordevstudies.gif
549 ms
autocomplete-emner.js
117 ms
autocomplete-main.js
112 ms
autocomplete-personer.js
112 ms
print.css
256 ms
sum.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
sum.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
sum.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 Sum.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 Sum.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.
sum.uio.no
Open Graph description is not detected on the main page of Sum 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: