Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

fug.no

FUG - Et nasjonalt utvalg for foreldre med barn i skolen

Page Load Speed

4.4 sec in total

First Response

445 ms

Resources Loaded

3.7 sec

Page Rendered

266 ms

fug.no screenshot

About Website

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

FUG (foreldreutvalget for grunnopplæringen) veileder foreldre og skoleansatte i spørsmål om skolehverdagen. Se mer.

Visit fug.no

Key Findings

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

Performance Metrics

fug.no performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

fug.no

445 ms

www.fug.no

994 ms

jquery.mmenu.all.css

213 ms

21358.css

220 ms

21353.css

223 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 33% of them (20 requests) were addressed to the original Fug.no, 33% (20 requests) were made to Img2.custompublish.com and 13% (8 requests) were made to Speech.leseweb.dk. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain Fug.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.6 kB (62%)

Content Size

906.1 kB

After Optimization

340.6 kB

In fact, the total size of Fug.no main page is 906.1 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. 65% of websites need less resources to load. Javascripts take 417.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.0 kB

  • Original 35.2 kB
  • After minification 31.5 kB
  • After compression 8.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 27.0 kB or 77% of the original size.

Image Optimization

-20%

Potential reduce by 33.8 kB

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

JavaScript Optimization

-64%

Potential reduce by 266.9 kB

  • Original 417.2 kB
  • After minification 411.5 kB
  • After compression 150.3 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 266.9 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 237.8 kB

  • Original 284.2 kB
  • After minification 276.3 kB
  • After compression 46.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. Fug.no needs all CSS files to be minified and compressed as it can save up to 237.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (52%)

Requests Now

56

After Optimization

27

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

Accessibility Review

fug.no accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

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

fug.no SEO score

100

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

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 Fug.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 Fug.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 FUG. 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: