7 sec in total
168 ms
6.2 sec
624 ms
Welcome to mortiis.com homepage info - get ready to check Mortiis best content for United States right away, or after learning these important things about mortiis.com
Official Mortiis Webstore.
Visit mortiis.comWe analyzed Mortiis.com page load time and found that the first response time was 168 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mortiis.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.5 s
63/100
25%
Value8.4 s
18/100
10%
Value1,380 ms
16/100
30%
Value0.004
100/100
15%
Value24.9 s
0/100
10%
168 ms
133 ms
85 ms
45 ms
50 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Mortiis.com, 46% (41 requests) were made to Static.parastorage.com and 19% (17 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Frog.wix.com.
Page size can be reduced by 2.9 MB (67%)
4.4 MB
1.5 MB
In fact, the total size of Mortiis.com main page is 4.4 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. 80% 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 3.3 MB which makes up the majority of the site volume.
Potential reduce by 104.3 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 104.3 kB or 84% of the original size.
Potential reduce by 23.7 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. Mortiis images are well optimized though.
Potential reduce by 2.5 MB
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 2.5 MB or 75% of the original size.
Potential reduce by 307.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. Mortiis.com needs all CSS files to be minified and compressed as it can save up to 307.8 kB or 82% of the original size.
Number of requests can be reduced by 56 (69%)
81
25
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mortiis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mortiis.com
168 ms
www.mortiis.com
133 ms
bt
85 ms
require.min.js
45 ms
main-r.min.js
50 ms
viewer.css
49 ms
dynamicmodel
9 ms
007527_87a7264bb1642728bd6fbfb0a343ef73_280.json.z
321 ms
007527_429b54003910c07596bc3577cfa4a8e8_284.json.z
430 ms
ugc-viewer
229 ms
bt
287 ms
skins.min.js
57 ms
components.min.js
52 ms
utils.min.js
20 ms
core.min.js
52 ms
react-with-addons.min.js
54 ms
lodash.min.js
51 ms
TweenMax.min.js
218 ms
layout.min.js
218 ms
tpa.min.js
220 ms
fonts.min.js
220 ms
animations.min.js
268 ms
swfobject.min.js
268 ms
mousetrap.min.js
277 ms
tweenEngine.min.js
275 ms
DrawSVGPlugin.min.js
278 ms
react-dom.min.js
276 ms
ScrollToPlugin.min.js
278 ms
widgets.min.js
276 ms
experiment.js
277 ms
render.min.js
277 ms
wixappsCore.min.js
299 ms
wixappsClassics.min.js
300 ms
wixappsBuilder.min.js
296 ms
zepto.min.js
296 ms
color.min.js
277 ms
react-dom-server.min.js
209 ms
bt
125 ms
dc.js
164 ms
bt
57 ms
4ac8a6ae7b8347e19c02bcb2d0a7ffad.svg
17 ms
bt
265 ms
iTunesBtn_EN.svg
153 ms
css
150 ms
index.html
143 ms
__utm.gif
102 ms
007527_8115adf97f6740909336791b40819865.png
83 ms
007527_3dffbf954efd4d549321d0c101b620af.png
83 ms
007527_4cfc17f2f20c432c98c144a352edd758.png
105 ms
007527_942a0f24158340c298498ba494430878.png
271 ms
007527_ad0dbb87a4e64d4899b40ae1c309af9a.png
265 ms
d3470ec8ca26475da4b228f0199b5d3d.png
98 ms
7177d158c36d432b93f51e54f80e2f3c.png
103 ms
af037f3cc11741d1ada5c7f70d1074bf.png
102 ms
530d907aaf7648c89c79be7eea724d9c.png
110 ms
007527_1e1c3b2d121c435395fcdea0c4cc5aaa.jpg
206 ms
007527_9c4eff0406f74d8384ec91c837df3d6b.jpg
267 ms
007527_0b021c0fb17a4ae9b8047ece5c2b20a7.png
205 ms
007527_30cc7847468e430881e29829959d123ff000.jpg
205 ms
bt
1927 ms
bt
4967 ms
fade_line.png
87 ms
lib.css
71 ms
app.css
79 ms
wix.min.js
85 ms
lib.js
109 ms
app.js
84 ms
templates.js
82 ms
like.php
419 ms
ga-audiences
331 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
292 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
380 ms
lF4BYh5xCPU
437 ms
widget_en.json
70 ms
angular-locale_en.js
69 ms
peiIL5ExGnk
308 ms
CyruGbLQaSs
344 ms
events.json
67 ms
loading-spinning-bubbles.svg
39 ms
ugc-viewer
57 ms
AAAAGZgAAAAAGXwABAAAAAAAAAAAAAAAAAAAABwQAAAAAAAAAAAAAAAIAAAAEAABkBAABQgZmABEAAAAAAAoAFAAeAHAAlgRGAAEAAAAHAtYAJQAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQAHAAAAAQAAAAAAAgAHAGAAAQAAAAAAAwAHADYAAQAAAAAABAAHAHUAAQAAAAAABQALABUAAQAAAAAABgAHAEsAAQAAAAAACgAaAIoAAwABBAkAAQAOAAcAAwABBAkAAgAOAGcAAwABBAkAAwAOAD0AAwABBAkABAAOAHwAAwABBAkABQAWACAAAwABBAkABgAOAFIAAwABBAkACgA0AKRiaXQtd2l4AGIAaQB0AC0AdwBpAHhWZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADBiaXQtd2l4AGIAaQB0AC0AdwBpAHhiaXQtd2l4AGIAaQB0AC0AdwBpAHhSZWd1bGFyAFIAZQBnAHUAbABhAHJiaXQtd2l4AGIAaQB0AC0AdwBpAHhGb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
1 ms
fy8tT2klpgR.js
134 ms
LVx-xkvaJ0b.png
150 ms
007527_30cc7847468e430881e29829959d123ff000.jpg
55 ms
www-embed-player-vflRGs1ko.css
303 ms
www-embed-player.js
423 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
56 ms
ad_status.js
284 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
415 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
494 ms
mortiis.com accessibility score
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
mortiis.com 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
Page has valid source maps
mortiis.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mortiis.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mortiis.com 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.
mortiis.com
Open Graph description is not detected on the main page of Mortiis. 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: