Tools & Wizards About Us
ntnu.no screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

ntnu.no

NTNU: Norges teknisk-naturvitenskapelige universitet - NTNU

Page Load Speed

5.4 sec in total

First Response

357 ms

Resources Loaded

3.5 sec

Page Rendered

1.6 sec

ntnu.no screenshot

About Website

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.no

Key Findings

We analyzed Ntnu.no page load time and found that the first response time was 357 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ntnu.no performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

ntnu.no

357 ms

www.ntnu.no

918 ms

css

34 ms

script.js

785 ms

lodash.js

504 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 90% of them (46 requests) were addressed to the original Ntnu.no, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Umami.it.ntnu.no. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ntnu.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.0 kB (6%)

Content Size

4.7 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ntnu.no main page is 4.7 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. 50% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 92.9 kB

  • Original 109.2 kB
  • After minification 95.5 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 13.6 kB, which is 12% 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 92.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 127.4 kB

  • Original 4.2 MB
  • After minification 4.0 MB

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. NTNU images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 75.7 kB

  • Original 453.3 kB
  • After minification 453.3 kB
  • After compression 377.6 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 75.7 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (63%)

Requests Now

43

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 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 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ntnu.no

ntnu.no

357 ms

www.ntnu.no

www.ntnu.no

918 ms

css

css

34 ms

script.js

script.js

785 ms

lodash.js

lodash.js

504 ms

util.js

util.js

357 ms

clay.css

clay.css

725 ms

main.css

main.css

484 ms

combo

combo

365 ms

js_loader_modules

js_loader_modules

784 ms

js_loader_config

js_loader_config

474 ms

combo

combo

863 ms

combo

combo

782 ms

combo

combo

835 ms

config.js

config.js

618 ms

loader.3.js

loader.3.js

836 ms

js_bundle_config

js_bundle_config

858 ms

main.css

main.css

855 ms

combo

combo

852 ms

combo

combo

853 ms

kindly-chat.js

kindly-chat.js

36 ms

main.js

main.js

959 ms

jquery.tablesorter.js

jquery.tablesorter.js

960 ms

jquery.slider.js

jquery.slider.js

959 ms

logo_ntnu.svg

logo_ntnu.svg

125 ms

711d8423-b999-4ad5-34de-fd615c60df93

711d8423-b999-4ad5-34de-fd615c60df93

475 ms

a52b8106-e22a-e70f-f186-0a1f74364d77

a52b8106-e22a-e70f-f186-0a1f74364d77

356 ms

2a6b15c7-af10-3fe9-f701-3e8882700676

2a6b15c7-af10-3fe9-f701-3e8882700676

367 ms

feadb25b-129a-0d4b-0907-c9790608fca4

feadb25b-129a-0d4b-0907-c9790608fca4

241 ms

df32956f-328e-4ef3-6843-960a8f4461b2

df32956f-328e-4ef3-6843-960a8f4461b2

246 ms

adecfcf3-634a-79d4-2cee-89bf07c64a37

adecfcf3-634a-79d4-2cee-89bf07c64a37

1008 ms

0ac0fb92-a7e2-a915-5ff7-24a4ec336d8e

0ac0fb92-a7e2-a915-5ff7-24a4ec336d8e

368 ms

e85c9992-8d1e-bd7e-ec26-12d9e19acf85

e85c9992-8d1e-bd7e-ec26-12d9e19acf85

372 ms

55f0a6cd-cf84-9e94-79c0-82bfb59f7a2d

55f0a6cd-cf84-9e94-79c0-82bfb59f7a2d

508 ms

logo_ntnu_tag_norsk.svg

logo_ntnu_tag_norsk.svg

485 ms

font

font

48 ms

fa-light-300.woff

fa-light-300.woff

435 ms

fa-regular-400.woff

fa-regular-400.woff

450 ms

fa-solid-900.woff

fa-solid-900.woff

542 ms

547 ms

fa-brands-400.woff

fa-brands-400.woff

532 ms

fa-brands6-400.ttf

fa-brands6-400.ttf

519 ms

siteanalyze_6000120.js

siteanalyze_6000120.js

36 ms

181 ms

187 ms

189 ms

154 ms

120 ms

bx_loader.gif

bx_loader.gif

142 ms

controls.png

controls.png

142 ms

124 ms

Accessibility Review

ntnu.no accessibility score

100

Accessibility Issues

Best Practices

ntnu.no best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ntnu.no SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NB

  • Encoding

    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.

Social Sharing Optimization

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: