Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

morningstar.no

Beste fond | Spare i fond | Sparing og investering | Morningstar

Page Load Speed

4 sec in total

First Response

539 ms

Resources Loaded

2.1 sec

Page Rendered

1.4 sec

morningstar.no screenshot

About Website

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

Norske Fondskurser, faktaark, investeringsanalyse, råd og porteføljeverktøy for norske fond og pensjonsfond

Visit morningstar.no

Key Findings

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

Performance Metrics

morningstar.no performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.307

38/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

539 ms

gtm.js

87 ms

cookieConsent.min.css

77 ms

mds.css

48 ms

autocomplete.css

86 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 16% of them (17 requests) were addressed to the original Morningstar.no, 51% (55 requests) were made to Euim.mstar.com and 12% (13 requests) were made to Morningstar.co.uk. The less responsive or slowest element that took the longest time to load (539 ms) belongs to the original domain Morningstar.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.7 kB (11%)

Content Size

2.3 MB

After Optimization

2.1 MB

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

HTML Optimization

-74%

Potential reduce by 129.4 kB

  • Original 175.2 kB
  • After minification 167.6 kB
  • After compression 45.8 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 129.4 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 26.4 kB

  • Original 1.1 MB
  • After minification 1.1 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. Morningstar images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 86.8 kB

  • Original 948.1 kB
  • After minification 947.4 kB
  • After compression 861.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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 8.1 kB

  • Original 92.8 kB
  • After minification 92.3 kB
  • After compression 84.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. Morningstar.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 80 (79%)

Requests Now

101

After Optimization

21

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

Accessibility Review

morningstar.no accessibility score

85

Accessibility Issues

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

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

morningstar.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

morningstar.no SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Morningstar.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 Morningstar.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 Morningstar. 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: