Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

hist.no

NTNU: Norges teknisk-naturvitenskapelige universitet - NTNU

Page Load Speed

3.6 sec in total

First Response

500 ms

Resources Loaded

2.9 sec

Page Rendered

148 ms

About Website

Visit hist.no now to see the best up-to-date Hist content for Norway and also check out these interesting facts you probably never knew about hist.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 hist.no

Key Findings

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

Performance Metrics

hist.no performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

hist.no

500 ms

hist.css

442 ms

hist.js

711 ms

swfobject.js

366 ms

aksessmultimedia.jjs

266 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 88% of them (44 requests) were addressed to the original Hist.no, 6% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Hist.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.0 kB (25%)

Content Size

303.4 kB

After Optimization

227.4 kB

In fact, the total size of Hist.no main page is 303.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 201.7 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 36.6 kB

  • Original 41.7 kB
  • After minification 22.3 kB
  • After compression 5.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 19.4 kB, which is 46% 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 88% of the original size.

Image Optimization

-7%

Potential reduce by 13.6 kB

  • Original 201.7 kB
  • After minification 188.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. Hist images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 25.3 kB

  • Original 59.2 kB
  • After minification 58.1 kB
  • After compression 33.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 25.3 kB or 43% of the original size.

CSS Optimization

-55%

Potential reduce by 463 B

  • Original 846 B
  • After minification 665 B
  • After compression 383 B

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. Hist.no needs all CSS files to be minified and compressed as it can save up to 463 B or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (33%)

Requests Now

49

After Optimization

33

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hist. 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 as a result speed up the page load time.

Accessibility Review

hist.no accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

hist.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

hist.no SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hist.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 Hist.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

Open Graph description is not detected on the main page of Hist. 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: