Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

e24.no

E24 - Norges største næringslivsavis

Page Load Speed

6.9 sec in total

First Response

527 ms

Resources Loaded

5.3 sec

Page Rendered

1.1 sec

e24.no screenshot

About Website

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

E24 er Norges største og viktigste avis for nyheter om økonomi og næringsliv. E24 er første ute med de viktigste nyhetene, gir deg kommentarer og analyse og setter dagsorden med sakene norsk næringsli...

Visit e24.no

Key Findings

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

Performance Metrics

e24.no performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

e24.no

527 ms

host.js

334 ms

style.css

964 ms

ccr4zex.js

138 ms

xtcore.js

407 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 16% of them (17 requests) were addressed to the original E24.no, 15% (16 requests) were made to Use.typekit.net and 10% (11 requests) were made to E24-3.vgc.no. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Imbo.vgc.no.

Page Optimization Overview & Recommendations

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

Content Size

3.6 MB

After Optimization

1.8 MB

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

HTML Optimization

-85%

Potential reduce by 294.6 kB

  • Original 346.0 kB
  • After minification 306.9 kB
  • After compression 51.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. This page needs HTML code to be minified as it can gain 39.1 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 294.6 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 33.2 kB

  • Original 944.8 kB
  • After minification 911.5 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. E24 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 496.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.0 MB or 67% of the original size.

CSS Optimization

-64%

Potential reduce by 528.1 kB

  • Original 828.5 kB
  • After minification 818.4 kB
  • After compression 300.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. E24.no needs all CSS files to be minified and compressed as it can save up to 528.1 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (47%)

Requests Now

91

After Optimization

48

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

Accessibility Review

e24.no accessibility score

60

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

[aria-*] attributes do not match their roles

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

e24.no best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

e24.no SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 E24.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 E24.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 E24. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: