Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

morris.no

Kofferter, vesker, hansker, lommebøker og tilbehør | Morris

Page Load Speed

9.4 sec in total

First Response

301 ms

Resources Loaded

9 sec

Page Rendered

112 ms

About Website

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

Kjøp kofferter, vesker, hansker, lommebøker, reisetilbehør og annet tilbehør online på Morris eller i din nærmeste butikk. Finn din koffert eller veske her!

Visit morris.no

Key Findings

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

Performance Metrics

morris.no performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

morris.no

301 ms

www.morris.no

729 ms

main-8a8d1fbbf9cf1a9fb17f.css

107 ms

index.js

917 ms

runtime~main-20e650418c7ad18c27cb.js

218 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 48% of them (45 requests) were addressed to the original Morris.no, 11% (10 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Core.helloretail.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.2 kB (6%)

Content Size

648.3 kB

After Optimization

610.2 kB

In fact, the total size of Morris.no main page is 648.3 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. 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. Javascripts take 561.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.2 kB

  • Original 43.4 kB
  • After minification 43.4 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 35.2 kB or 81% of the original size.

Image Optimization

-19%

Potential reduce by 1.1 kB

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

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 561.0 kB
  • After minification 561.0 kB
  • After compression 559.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

-0%

Potential reduce by 111 B

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 37.8 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. Morris.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 59 (83%)

Requests Now

71

After Optimization

12

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

Accessibility Review

morris.no accessibility score

90

Accessibility Issues

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.

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

morris.no best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

morris.no SEO score

87

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

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

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Morris.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 Morris.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 Morris. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: