5.2 sec in total
529 ms
4.4 sec
220 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 529 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
morris.no performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value16.5 s
0/100
25%
Value11.5 s
5/100
10%
Value4,950 ms
0/100
30%
Value1.382
0/100
15%
Value19.5 s
2/100
10%
529 ms
1290 ms
419 ms
1239 ms
1045 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 71% of them (34 requests) were addressed to the original Morris.no, 13% (6 requests) were made to Use.typekit.net and 6% (3 requests) were made to Track.adform.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Morris.no.
Page size can be reduced by 486.8 kB (48%)
1.0 MB
536.9 kB
In fact, the total size of Morris.no main page is 1.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. 50% of websites need less resources to load. Images take 471.9 kB which makes up the majority of the site volume.
Potential reduce by 55.9 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 55.9 kB or 81% of the original size.
Potential reduce by 105.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 105.9 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 266.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 266.0 kB or 65% of the original size.
Potential reduce by 59.0 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 needs all CSS files to be minified and compressed as it can save up to 59.0 kB or 81% of the original size.
Number of requests can be reduced by 8 (19%)
42
34
The browser has sent 42 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 9 to 1 for JavaScripts and as a result speed up the page load time.
morris.no
529 ms
www.morris.no
1290 ms
combined.compressed.css
419 ms
mjm8zck.js
1239 ms
combined.compressed.js
1045 ms
p13n.js
6 ms
5
93 ms
carousel_morris_v5_always-ready.gif
441 ms
298054C41S-1_image_view_1_200.png
228 ms
298040C9S-1_image_view_1_200.png
109 ms
298084C40S-1_image_view_1_200.png
392 ms
294700C9S-1_image_view_1_200.png
393 ms
297370C10S-1_image_view_1_200.png
423 ms
600kr.png
227 ms
299389C40S472_image_view_1_200.png
432 ms
296959C40S-1_image_view_1_200.png
332 ms
300kr.png
436 ms
299389C62S882_image_view_1_200.png
491 ms
2in1.png
492 ms
298238C40S-1_image_view_1_200.png
634 ms
298237C10S-1_image_view_1_200.png
536 ms
298238C97S-1_image_view_1_200.png
542 ms
298237C40S-1_image_view_1_200.png
547 ms
p.gif
71 ms
gtm.js
54 ms
popup_close_sprite.png
565 ms
logo_retina.png
566 ms
header_search_icon_sprite_retina.png
615 ms
minibasket_icon_sprite_retina.png
622 ms
carousel_navigation_sprite.png
630 ms
torazb2LEK_cmFZj-Afb5AsYBuncak58TWPb5y7E0G6ffw7EggM9eMI6MK6f5Mb.eot
39 ms
TXR_PWrBZuHlXYyj29ekBXOvijNSnFxxWvYGGGBqth3ffwhEggM9eMI6MK6f5MS.eot
80 ms
vDiDS_l522I9ShH0uMmHH3C1aAvuad6M9huWZvcNZ4qffVeuggM9eMI6MK6f5Mw.eot
92 ms
_q8oVjCLk0qUUOcbreNqbWXHQKl2TH_0wjYKoy6M7wbffwkEggM9eMI6MK6f5Mj.eot
92 ms
promotion_copyright.png
626 ms
input_text.png
624 ms
CC_ViewScaledImage-Start;pgid=nFXmdG94gj1SRpJGCmdHyU7h0000YtU6i45k;sid=PKu70CmDCb-00n9WBMCttjcv0GekbcVPIxZXHDY-
1309 ms
CC_ViewScaledImage-Start;pgid=nFXmdG94gj1SRpJGCmdHyU7h0000YtU6i45k;sid=PKu70CmDCb-00n9WBMCttjcv0GekbcVPIxZXHDY-
986 ms
CC_ViewScaledImage-Start;pgid=nFXmdG94gj1SRpJGCmdHyU7h0000YtU6i45k;sid=PKu70CmDCb-00n9WBMCttjcv0GekbcVPIxZXHDY-
687 ms
p13n_generated.js
78 ms
analytics.js
6 ms
trackpoint
481 ms
236 ms
130 ms
298238C10S-1_image_view_1_200.png
111 ms
276926C10S-1_image_view_1_200.png
108 ms
285320C40S-1_image_view_1_200.png
109 ms
295745C10S-1_image_view_1_200.png
112 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
User Experience
Impact
Issue
Serves images with low resolution
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NO
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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 description is not detected on the main page of Morris. 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: