Access fefo.no. Bærekraftig og livskraftig Finnmark

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.19

64/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

www.fefo.no

455 ms

default-typography.css

101 ms

default-skip-to-links.css

199 ms

default-tabfocus-styles.css

304 ms

jquery-1.12.4.min.js

585 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 79% of them (37 requests) were addressed to the original Fefo.no, 11% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fefo.no.

Content Size

1.6 MB

After Optimization

1.4 MB

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

HTML Optimization

-75%

Potential reduce by 36.2 kB

Original 48.4 kB
After minification 44.2 kB
After compression 12.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. 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 36.2 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 23.8 kB

Original 1.3 MB
After minification 1.3 MB

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. Fefo images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 53.1 kB

Original 143.6 kB
After minification 143.5 kB
After compression 90.4 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 53.1 kB or 37% of the original size.

CSS Optimization

-41%

Potential reduce by 19.4 kB

Original 47.7 kB
After minification 47.7 kB
After compression 28.3 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. Fefo.no needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 41% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Links do not have a discernible name

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

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

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

fefo.no

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Bærekraftig og livskraftig Finnmark

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)