Report Summary

  • 34

    Performance

    Renders faster than
    55% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 97

    SEO

    Google-friendlier than
    92% of websites

ordnett.no

Digitale ordbøker til datamaskin, nettbrett og mobil - ordnett.no

Page Load Speed

4.2 sec in total

First Response

679 ms

Resources Loaded

3.4 sec

Page Rendered

182 ms

ordnett.no screenshot

About Website

Welcome to ordnett.no homepage info - get ready to check Ordnett best content for Norway right away, or after learning these important things about ordnett.no

Ordnett tilbyr ordbøker til mobil, nettbrett og datamaskin. Vi har ordbøker på elleve språk, og hver ordbok blir jevnlig oppdatert av vår redaksjon.

Visit ordnett.no

Key Findings

We analyzed Ordnett.no page load time and found that the first response time was 679 ms and then it took 3.5 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

ordnett.no performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

www.ordnett.no

679 ms

site.min.css

158 ms

jquery-ui-1.10.4.custom.min.css

308 ms

bruker.css

375 ms

site.min.1444737977368.js

674 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 320.4 kB (33%)

Content Size

967.2 kB

After Optimization

646.8 kB

In fact, the total size of Ordnett.no main page is 967.2 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 543.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.3 kB

  • Original 42.5 kB
  • After minification 34.8 kB
  • After compression 10.2 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 7.7 kB, which is 18% 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 32.3 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 35.7 kB

  • Original 543.0 kB
  • After minification 507.4 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. Ordnett images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 252.4 kB

  • Original 381.6 kB
  • After minification 369.5 kB
  • After compression 129.2 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 252.4 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (17%)

Requests Now

42

After Optimization

35

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

Accessibility Review

ordnett.no accessibility score

98

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 input fields do not have accessible names

Best Practices

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

Page has valid source maps

SEO Factors

ordnett.no SEO score

97

Search Engine Optimization Advices

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

    NO

  • Encoding

    UTF-8

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