Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

forbruker.no

Siste nytt og forstå hvorfor | Aftenposten

Page Load Speed

16.7 sec in total

First Response

370 ms

Resources Loaded

12.4 sec

Page Rendered

3.9 sec

forbruker.no screenshot

About Website

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

Les Aftenposten for et raskt overblikk i dagens nyheter. For deg som vil forstå hvorfor ting skjer og hvordan de henger sammen. Journalistikk du kan stole på.

Visit forbruker.no

Key Findings

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

Performance Metrics

forbruker.no performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,420 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

forbruker.no

370 ms

www.aftenposten.no

703 ms

mixpanel-2.2.min.js

17 ms

analytics.js

36 ms

css

35 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Forbruker.no, 26% (46 requests) were made to Aftenposten.no and 12% (21 requests) were made to Image.snd.no. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Vertical.snd.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 917.4 kB (30%)

Content Size

3.0 MB

After Optimization

2.1 MB

In fact, the total size of Forbruker.no main page is 3.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 244.1 kB

  • Original 298.5 kB
  • After minification 294.6 kB
  • After compression 54.4 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 244.1 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 140.6 kB

  • Original 1.9 MB
  • After minification 1.8 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. Forbruker images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 315.3 kB

  • Original 516.0 kB
  • After minification 476.9 kB
  • After compression 200.7 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 315.3 kB or 61% of the original size.

CSS Optimization

-73%

Potential reduce by 217.4 kB

  • Original 298.1 kB
  • After minification 273.2 kB
  • After compression 80.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. Forbruker.no needs all CSS files to be minified and compressed as it can save up to 217.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (51%)

Requests Now

158

After Optimization

77

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

Accessibility Review

forbruker.no accessibility score

73

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

[role] values are not valid

High

[aria-*] attributes are not valid or misspelled

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

Links do not have a discernible name

Best Practices

forbruker.no best practices score

69

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

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forbruker.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Forbruker.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 Forbruker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: