Tools & Wizards About Us
statskog.no screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

statskog.no

Vi sikrer fellesskapets verdier for framtida | Statskog

Page Load Speed

3.3 sec in total

First Response

312 ms

Resources Loaded

2.9 sec

Page Rendered

152 ms

statskog.no screenshot

About Website

Click here to check amazing Statskog content for Norway. Otherwise, check out these important facts you probably never knew about statskog.no

Vi sikrer fellesskapets verdier for framtida

Visit statskog.no

Key Findings

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

statskog.no performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.173

69/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

www.statskog.no

312 ms

forsiden.aspx

230 ms

controls.css

260 ms

controls.css

234 ms

Menu.css

226 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 84% of them (57 requests) were addressed to the original Statskog.no, 3% (2 requests) were made to S7.addthis.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Statskog.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (70%)

Content Size

2.7 MB

After Optimization

806.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Statskog.no main page is 2.7 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. 55% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 89.1 kB

  • Original 122.7 kB
  • After minification 115.6 kB
  • After compression 33.7 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 89.1 kB or 73% of the original size.

Image Optimization

-22%

Potential reduce by 77.5 kB

  • Original 350.2 kB
  • After minification 272.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. Obviously, Statskog needs image optimization as it can save up to 77.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 1.4 MB

  • Original 1.9 MB
  • After minification 1.8 MB
  • After compression 453.8 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 1.4 MB or 75% of the original size.

CSS Optimization

-88%

Potential reduce by 346.1 kB

  • Original 392.8 kB
  • After minification 267.3 kB
  • After compression 46.7 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. Statskog.no needs all CSS files to be minified and compressed as it can save up to 346.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (58%)

Requests Now

65

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Statskog. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.statskog.no

www.statskog.no

312 ms

forsiden.aspx

forsiden.aspx

230 ms

controls.css

controls.css

260 ms

controls.css

controls.css

234 ms

Menu.css

Menu.css

226 ms

search.css

search.css

250 ms

corev4.css

corev4.css

381 ms

css

css

75 ms

statskog.css

statskog.css

252 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

668 ms

WebResource.axd

WebResource.axd

338 ms

blank.js

blank.js

353 ms

addthis_widget.js

addthis_widget.js

17 ms

init.js

init.js

252 ms

ScriptResource.axd

ScriptResource.axd

229 ms

ScriptResource.axd

ScriptResource.axd

110 ms

dc.js

dc.js

37 ms

bakgrunn.jpg

bakgrunn.jpg

249 ms

fgimg.png

fgimg.png

148 ms

logo.png

logo.png

145 ms

knapp_sok.jpg

knapp_sok.jpg

146 ms

logo_liten.jpg

logo_liten.jpg

146 ms

Forsidekart.jpg

Forsidekart.jpg

166 ms

473_Valsjoehytta_maaneskinn_Torkel_Skoglund.JPG

473_Valsjoehytta_maaneskinn_Torkel_Skoglund.JPG

366 ms

135_Rev_istockphoto_KaidoKarner.jpg.jpg

135_Rev_istockphoto_KaidoKarner.jpg.jpg

238 ms

201_Skjervkoia_ivar_rustad.JPG

201_Skjervkoia_ivar_rustad.JPG

365 ms

Fiske_Istockph_joss_135pxl.jpg

Fiske_Istockph_joss_135pxl.jpg

255 ms

201_Rago1_Jim_Kristensen.jpg

201_Rago1_Jim_Kristensen.jpg

268 ms

FR.LIV%20Staupaadalsbu%20Beiarn.jpg

FR.LIV%20Staupaadalsbu%20Beiarn.jpg

366 ms

135_Skog_Steinar_Johansen.jpg

135_Skog_Steinar_Johansen.jpg

379 ms

135_Skog_loekemyrodden_Thomas_Xavier_Floyd.jpg

135_Skog_loekemyrodden_Thomas_Xavier_Floyd.jpg

381 ms

CRPERSPC.GIF

CRPERSPC.GIF

399 ms

annonse_inatur.jpg

annonse_inatur.jpg

448 ms

annonse_godtur.jpg

annonse_godtur.jpg

464 ms

annonse_rypeprosjektet.jpg

annonse_rypeprosjektet.jpg

466 ms

rammeTV.gif

rammeTV.gif

468 ms

rammeTM.gif

rammeTM.gif

474 ms

rammeTH.gif

rammeTH.gif

509 ms

rammeM922.gif

rammeM922.gif

544 ms

bgximg.png

bgximg.png

561 ms

line_dot.jpg

line_dot.jpg

564 ms

__utm.gif

__utm.gif

52 ms

dott.gif

dott.gif

552 ms

flickr.png

flickr.png

557 ms

facebook_svart.png

facebook_svart.png

602 ms

twitter.png

twitter.png

622 ms

youtube.png

youtube.png

633 ms

fossekall.png

fossekall.png

641 ms

EjsrzDkQUQCDwsBtLpcVQaCWcynf_cDxXwCLxiixG1c.ttf

EjsrzDkQUQCDwsBtLpcVQaCWcynf_cDxXwCLxiixG1c.ttf

89 ms

line_hel.jpg

line_hel.jpg

614 ms

rammeBV.gif

rammeBV.gif

618 ms

rammeBM.gif

rammeBM.gif

671 ms

rammeBH.gif

rammeBH.gif

678 ms

forsiden.aspx

forsiden.aspx

1048 ms

300lo.json

300lo.json

36 ms

all.js&version=v2.0

all.js&version=v2.0

188 ms

core.js

core.js

788 ms

sp.core.js

sp.core.js

683 ms

ScriptResx.ashx

ScriptResx.ashx

687 ms

cui.js

cui.js

880 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

29 ms

185 ms

xd_arbiter.php

xd_arbiter.php

63 ms

xd_arbiter.php

xd_arbiter.php

123 ms

sp.ui.dialog.js

sp.ui.dialog.js

148 ms

search.js

search.js

131 ms

sp.runtime.js

sp.runtime.js

133 ms

sp.js

sp.js

291 ms

Accessibility Review

statskog.no accessibility score

85

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes are not valid or misspelled

Best Practices

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

SEO Factors

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

    NB

  • Encoding

    UTF-8

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

statskog.no

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