Tools & Wizards About Us
hint.no screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

hint.no

Nord University

Page Load Speed

5 sec in total

First Response

354 ms

Resources Loaded

4.4 sec

Page Rendered

201 ms

hint.no screenshot

About Website

Click here to check amazing Hint content for Norway. Otherwise, check out these important facts you probably never knew about hint.no

Nord University has 1.300 employees and 11.000 students at campuses in Nordland and Trøndelag.

Visit hint.no

Key Findings

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

Performance Metrics

hint.no performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value3,870 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value31.2 s

0/100

10%

Network Requests Diagram

hint.no

354 ms

www.nord.no

550 ms

en

1064 ms

corev15.css

668 ms

main.css

533 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hint.no, 81% (69 requests) were made to Nord.no and 14% (12 requests) were made to Media.nord.no. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Nord.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (74%)

Content Size

3.7 MB

After Optimization

989.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hint.no main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 144.7 kB

  • Original 175.6 kB
  • After minification 137.7 kB
  • After compression 30.9 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 37.8 kB, which is 22% 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 144.7 kB or 82% of the original size.

Image Optimization

-14%

Potential reduce by 53.7 kB

  • Original 388.5 kB
  • After minification 334.8 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, Hint needs image optimization as it can save up to 53.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 2.1 MB

  • Original 2.6 MB
  • After minification 2.4 MB
  • After compression 552.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 2.1 MB or 79% of the original size.

CSS Optimization

-87%

Potential reduce by 494.2 kB

  • Original 565.6 kB
  • After minification 418.9 kB
  • After compression 71.4 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. Hint.no needs all CSS files to be minified and compressed as it can save up to 494.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (69%)

Requests Now

80

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hint. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hint.no

hint.no

354 ms

www.nord.no

www.nord.no

550 ms

en

en

1064 ms

corev15.css

corev15.css

668 ms

main.css

main.css

533 ms

uin.table.css

uin.table.css

275 ms

searchv15.css

searchv15.css

403 ms

init.js

init.js

663 ms

initstrings.js

initstrings.js

411 ms

strings.js

strings.js

657 ms

require.js

require.js

547 ms

require-init.js

require-init.js

549 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

707 ms

jquery-cookie-1.3.0.min.js

jquery-cookie-1.3.0.min.js

723 ms

uin.utils.js

uin.utils.js

724 ms

uin.cookieinfo.js

uin.cookieinfo.js

791 ms

tmp.js

tmp.js

795 ms

uin.responsivesetup.js

uin.responsivesetup.js

797 ms

uin.navigation.js

uin.navigation.js

799 ms

uin.accordion.js

uin.accordion.js

805 ms

uin.expandbox.js

uin.expandbox.js

812 ms

uin.popup.js

uin.popup.js

925 ms

webloggingservice.js

webloggingservice.js

928 ms

uin.accordioncopylink.js

uin.accordioncopylink.js

930 ms

uin.map.js

uin.map.js

932 ms

ie55up.js

ie55up.js

938 ms

uin.threecolumncontentcustomaction.js

uin.threecolumncontentcustomaction.js

944 ms

uin.factboxcustomaction.js

uin.factboxcustomaction.js

1054 ms

uin.accordioncustomaction.js

uin.accordioncustomaction.js

1057 ms

mavention.sharepoint.externalimagerenditionsenabler.loader.js

mavention.sharepoint.externalimagerenditionsenabler.loader.js

1067 ms

ScriptResource.axd

ScriptResource.axd

1067 ms

blank.js

blank.js

1075 ms

ScriptResource.axd

ScriptResource.axd

1076 ms

sp.init.js

sp.init.js

1188 ms

clientrenderer.js

clientrenderer.js

1193 ms

ScriptResx.ashx

ScriptResx.ashx

1206 ms

search.clientcontrols.js

search.clientcontrols.js

1331 ms

search.cbs.js

search.cbs.js

1205 ms

item_uinevent.js

item_uinevent.js

950 ms

group_content.js

group_content.js

946 ms

control_uincalendarpaging.js

control_uincalendarpaging.js

932 ms

item_uinnews.js

item_uinnews.js

951 ms

control_uinlist.js

control_uinlist.js

815 ms

ScriptResx.ashx

ScriptResx.ashx

815 ms

sp.runtime.js

sp.runtime.js

923 ms

sp.ui.dialog.js

sp.ui.dialog.js

825 ms

sp.js

sp.js

1080 ms

WebResource.axd

WebResource.axd

784 ms

NORDuniversitet-Vesteralen.jpg

NORDuniversitet-Vesteralen.jpg

624 ms

favicon.ico

favicon.ico

144 ms

spcommon.png

spcommon.png

141 ms

nordlogoen.jpg

nordlogoen.jpg

274 ms

nordlogoen.jpg

nordlogoen.jpg

407 ms

menudark.gif

menudark.gif

139 ms

LargeMap.png

LargeMap.png

138 ms

SmallMap.png

SmallMap.png

267 ms

Studiested-Bodo-Vinter.JPG

Studiested-Bodo-Vinter.JPG

623 ms

Mo-i-rana-hovedbygg.jpg

Mo-i-rana-hovedbygg.jpg

622 ms

gammelbygget_NESNA.JPG

gammelbygget_NESNA.JPG

627 ms

Sandnessjoen-3.jpg

Sandnessjoen-3.jpg

628 ms

Namsos%20fasade.JPG

Namsos%20fasade.JPG

627 ms

steinkjer_fasade.jpg

steinkjer_fasade.jpg

751 ms

levanger_hovedbygget.jpg

levanger_hovedbygget.jpg

750 ms

HiNT%20Stjordal.jpg

HiNT%20Stjordal.jpg

751 ms

Bachelor-i-historie.jpg

Bachelor-i-historie.jpg

1000 ms

Museo_Slab_500_2-webfont.woff

Museo_Slab_500_2-webfont.woff

251 ms

uin.slider.js

uin.slider.js

253 ms

StudySearchModuleViewModel.js

StudySearchModuleViewModel.js

239 ms

uin_basic_icon.woff

uin_basic_icon.woff

354 ms

knockout-3.2.0.js

knockout-3.2.0.js

371 ms

gtm.js

gtm.js

69 ms

customstrings.js

customstrings.js

329 ms

moment.js

moment.js

453 ms

uin.eventdisplaytemplatedateformat.js

uin.eventdisplaytemplatedateformat.js

328 ms

uincustomstrings.js

uincustomstrings.js

448 ms

control_searchbox_uincompact.js

control_searchbox_uincompact.js

446 ms

analytics.js

analytics.js

22 ms

core.js

core.js

540 ms

collect

collect

13 ms

slick.min.js

slick.min.js

282 ms

query

query

401 ms

GetTerms

GetTerms

448 ms

GetTerms

GetTerms

453 ms

Manet.jpg

Manet.jpg

403 ms

Adventure-knowledge-saltenfjord-rib.jpg

Adventure-knowledge-saltenfjord-rib.jpg

400 ms

Accessibility Review

hint.no accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

High

<frame> or <iframe> elements do not have a title

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

hint.no best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

hint.no SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hint.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hint.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

hint.no

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