Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

nfk.no

Nordland fylkeskommune

Page Load Speed

3.8 sec in total

First Response

617 ms

Resources Loaded

2.8 sec

Page Rendered

449 ms

nfk.no screenshot

About Website

Visit nfk.no now to see the best up-to-date Nfk content for Norway and also check out these interesting facts you probably never knew about nfk.no

Velkommen til Nordland fylkeskommune. Her finner du informasjon om våre tjenester, politikk og om fylkeskommunens organisasjon og virksomheter.

Visit nfk.no

Key Findings

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

Performance Metrics

nfk.no performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

www.nfk.no

617 ms

default-typography.css

187 ms

default-skip-to-links.css

283 ms

default-tabfocus-styles.css

281 ms

jquery-1.12.4.min.js

553 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 70% of them (35 requests) were addressed to the original Nfk.no, 14% (7 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nfk.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.5 kB (31%)

Content Size

252.7 kB

After Optimization

175.2 kB

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

HTML Optimization

-77%

Potential reduce by 54.7 kB

  • Original 70.8 kB
  • After minification 66.1 kB
  • After compression 16.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.7 kB or 77% of the original size.

Image Optimization

-21%

Potential reduce by 17.9 kB

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

JavaScript Optimization

-5%

Potential reduce by 4.0 kB

  • Original 81.5 kB
  • After minification 81.4 kB
  • After compression 77.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 840 B

  • Original 14.6 kB
  • After minification 14.6 kB
  • After compression 13.8 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. Nfk.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (70%)

Requests Now

40

After Optimization

12

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

Accessibility Review

nfk.no accessibility score

91

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

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

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

SEO Factors

nfk.no SEO score

99

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

    NB

  • Encoding

    UTF-8

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