Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ofv.no

OFV | Opplysningsrådet for veitrafikken

Page Load Speed

3.1 sec in total

First Response

816 ms

Resources Loaded

1.8 sec

Page Rendered

520 ms

About Website

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

Hjemmeside

Visit ofv.no

Key Findings

We analyzed Ofv.no page load time and found that the first response time was 816 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ofv.no performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

ofv.no

816 ms

screen.css

505 ms

js

80 ms

scrollreveal.min.js

36 ms

scrollreveal.min.js

18 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 26% of them (8 requests) were addressed to the original Ofv.no, 48% (15 requests) were made to Opplysningsraadet-for-veitrafikk-ofv.s3.amazonaws.com and 6% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (816 ms) belongs to the original domain Ofv.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.9 kB (24%)

Content Size

704.7 kB

After Optimization

535.8 kB

In fact, the total size of Ofv.no main page is 704.7 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. 35% of websites need less resources to load. Images take 498.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.3 kB

  • Original 53.3 kB
  • After minification 44.4 kB
  • After compression 11.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 8.9 kB, which is 17% 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 42.3 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 16.4 kB

  • Original 498.2 kB
  • After minification 481.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. OFV images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 16.9 kB

  • Original 46.8 kB
  • After minification 46.8 kB
  • After compression 29.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 16.9 kB or 36% of the original size.

CSS Optimization

-88%

Potential reduce by 93.3 kB

  • Original 106.4 kB
  • After minification 78.7 kB
  • After compression 13.1 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. Ofv.no needs all CSS files to be minified and compressed as it can save up to 93.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (22%)

Requests Now

27

After Optimization

21

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

Accessibility Review

ofv.no accessibility score

71

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

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

ofv.no SEO score

85

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

Image elements do not have [alt] attributes

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 Ofv.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 Ofv.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 data is detected on the main page of OFV. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: