9.4 sec in total
301 ms
9 sec
112 ms
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.noWe 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.
morris.no performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value15.0 s
0/100
25%
Value8.4 s
18/100
10%
Value2,530 ms
4/100
30%
Value0.057
98/100
15%
Value18.1 s
3/100
10%
301 ms
729 ms
107 ms
917 ms
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 size can be reduced by 37.5 kB (6%)
647.6 kB
610.2 kB
In fact, the total size of Morris.no main page is 647.6 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 560.3 kB which makes up the majority of the site volume.
Potential reduce by 35.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.
Potential reduce by 1.1 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.
Potential reduce by 1.0 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.
Potential reduce by 111 B
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.
Number of requests can be reduced by 59 (83%)
71
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.
morris.no
301 ms
www.morris.no
729 ms
main-8a8d1fbbf9cf1a9fb17f.css
107 ms
index.js
917 ms
runtime~main-20e650418c7ad18c27cb.js
218 ms
4191f8ddaa79441d0dfe.js
420 ms
b1db721bd139d94860ea.js
430 ms
016bf5359060d647e3a9.js
324 ms
7ea3f799d0392ea32193.js
324 ms
2f31251325ff80d5212b.js
325 ms
25ec0e70e533e82d7277.js
323 ms
004c0faaa884a57db279.js
429 ms
69c44f41abe6cdeddfc9.js
430 ms
37c4e66b56404e309dde.js
430 ms
b930fa32aee836833906.js
535 ms
b7e71434c0745cd9513e.js
522 ms
8d85f71e1b967a8f001a.js
536 ms
49df9acbeb0ab28516bd.js
533 ms
5ff28bbbdb0f1e80aaf7.js
853 ms
6efb8ac8c6f2b5adf2d7.js
747 ms
customer.css
625 ms
css
28 ms
css
45 ms
css
49 ms
css
49 ms
gtm.js
201 ms
analytics.js
146 ms
morris_logo.png
964 ms
564d3244220de7022def.js
311 ms
58270107a79835a840c5.js
309 ms
06fe095ec8067d1c35de.js
309 ms
0bcb3dd71064f695a1fa.js
305 ms
d5f5f897411f19b88b8e.js
302 ms
75f78816840b8c1dbc23.js
305 ms
bd327d76f579e258e680.js
363 ms
56ea46958ab54c19b423.js
362 ms
4d7905e0bb4c138287d4.js
358 ms
d35fb814654c51592d61.js
355 ms
ce3f6f00de3e86c901f8.js
355 ms
d949c0249546684d3f84.js
341 ms
b9bca24a229e689b0555.js
538 ms
short-white.png
109 ms
8783d71cd8f842263aee.js
534 ms
css
71 ms
all.min.css
131 ms
session-check
474 ms
get
474 ms
5aU69_a8oxmIdGl4AQ.ttf
35 ms
5aU19_a8oxmIfMJaERySiA.ttf
43 ms
5aU19_a8oxmIfLZcERySiA.ttf
50 ms
5aU19_a8oxmIfNJdERySiA.ttf
56 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
21 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf
30 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf
21 ms
js
92 ms
fbevents.js
189 ms
VGrzl05S.js
289 ms
jsTag
462 ms
d7.js
785 ms
hotjar-1697383.js
285 ms
linkid.js
67 ms
destination
264 ms
3331.js
264 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
267 ms
S6uyw4BMUTPHjx4wWw.ttf
267 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
267 ms
collect
174 ms
collect
307 ms
1193019810769112
189 ms
fa-regular-400.woff
605 ms
fa-light-300.woff
1681 ms
fa-solid-900.woff
1681 ms
modules.ef112488b1de7ff5f962.js
202 ms
348 ms
awAddGift.js
136 ms
js
131 ms
6efb8ac8c6f2b5adf2d7.js
311 ms
bd327d76f579e258e680.js
300 ms
4191f8ddaa79441d0dfe.js
301 ms
5ff28bbbdb0f1e80aaf7.js
404 ms
56235afe1b5a988ee5e1.js
299 ms
ga-audiences
258 ms
trackingUser
1340 ms
bd327d76f579e258e680.js.map
121 ms
4191f8ddaa79441d0dfe.js.map
226 ms
6efb8ac8c6f2b5adf2d7.js.map
1143 ms
22 ms
5ff28bbbdb0f1e80aaf7.js.map
1198 ms
init
4344 ms
jquery.min.js
18 ms
getUid;c
275 ms
setup
76 ms
pageview
104 ms
morris.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
morris.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
morris.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NO
NO
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.
morris.no
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: