6.2 sec in total
523 ms
5.4 sec
255 ms
Click here to check amazing NTNU content for Norway. Otherwise, check out these important facts you probably never knew about ntnu.no
Norges teknisk-naturvitenskapelige universitet. Campuser i Trondheim, Gjøvik og Ålesund. NTNU har 40000 studenter og hovedansvar for den høyere teknologiutdanningen i Norge.
Visit ntnu.noWe analyzed Ntnu.no page load time and found that the first response time was 523 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ntnu.no performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value16.4 s
0/100
25%
Value14.4 s
1/100
10%
Value1,110 ms
23/100
30%
Value0.089
92/100
15%
Value16.3 s
5/100
10%
523 ms
1045 ms
368 ms
909 ms
547 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 66% of them (37 requests) were addressed to the original Ntnu.no, 11% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ntnu.no.
Page size can be reduced by 1.7 MB (74%)
2.3 MB
597.7 kB
In fact, the total size of Ntnu.no main page is 2.3 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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 48.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 48.7 kB or 80% of the original size.
Potential reduce by 5.1 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, NTNU needs image optimization as it can save up to 5.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 985.0 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 985.0 kB or 70% of the original size.
Potential reduce by 655.6 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. Ntnu.no needs all CSS files to be minified and compressed as it can save up to 655.6 kB or 83% of the original size.
Number of requests can be reduced by 27 (59%)
46
19
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NTNU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
ntnu.no
523 ms
www.ntnu.no
1045 ms
aui.css
368 ms
main.css
909 ms
main.css
547 ms
miniCalender.css
736 ms
chosen.css
751 ms
jquery-ui.css
753 ms
main.css
543 ms
barebone.jsp
2487 ms
main.css
906 ms
font-awesome.min.css
6 ms
css
26 ms
jquery.min.js
32 ms
underscore-min.js
917 ms
jquerySlider.js
934 ms
jQerySlider.css
931 ms
jquery.tablesorter.js
1088 ms
moment.min.js
1085 ms
allDev.js
1098 ms
main.js
1111 ms
ntnu_init_javascript.js
1117 ms
soundmanager2-nodebug-jsmin.js
1268 ms
en_UK.png
197 ms
b8d8408a-33c0-429b-bc35-ad85b76da0f7
885 ms
1a9c7fb0-e352-4666-bc33-d5e7680fba52
1079 ms
a245bfba-ac77-46e0-ad43-74b687417e6d
699 ms
88b75e66-1bc8-42bd-9d73-752b9ae46eeb
374 ms
a89180a9-fbb6-464a-943e-406d83661dad
713 ms
479fd341-2d11-40d1-8a6c-15a0f426380b
385 ms
42c6777c-162c-4b79-bb03-3ab359bb8ff3
720 ms
4d8ab939-a831-4dfa-8bf5-da92d2ca000d
563 ms
b1269b1b-1a91-4870-95e4-aa442b488c28
744 ms
54b5c673-66be-4329-a320-162eb56d8897
1051 ms
bec65999-32f3-4357-8bf7-6362694c3795
1078 ms
7c70a179-3c0b-45b0-8e17-27552f9eb7ab
905 ms
8874ab1c-8441-4b30-8bb2-42d5d1a8da25
928 ms
1049 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
20 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
19 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
20 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
20 ms
logo_ntnu.svg
1071 ms
PiolGPHu6Po
92 ms
fontawesome-webfont.woff
38 ms
analytics.js
25 ms
collect
16 ms
www-embed-player-vflZsBgOl.css
36 ms
www-embed-player.js
64 ms
base.js
103 ms
ga-audiences
122 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
45 ms
ad_status.js
49 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
35 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
37 ms
179 ms
ntnu.no accessibility score
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
ntnu.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
Missing source maps for large first-party JavaScript
ntnu.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
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ntnu.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that Ntnu.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.
ntnu.no
Open Graph description is not detected on the main page of NTNU. 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: