2.4 sec in total
57 ms
2.3 sec
67 ms
Welcome to exmortis.com homepage info - get ready to check Ex Mortis best content right away, or after learning these important things about exmortis.com
Ex Mortis Stalkarounds and professional blood and makeup effects products from Wayne Toth
Visit exmortis.comWe analyzed Exmortis.com page load time and found that the first response time was 57 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
exmortis.com performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value6.2 s
11/100
25%
Value5.9 s
48/100
10%
Value1,910 ms
8/100
30%
Value0
100/100
15%
Value17.6 s
4/100
10%
57 ms
59 ms
53 ms
1214 ms
51 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Exmortis.com, 32% (21 requests) were made to Static.wixstatic.com and 24% (16 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 206.6 kB (25%)
816.5 kB
609.9 kB
In fact, the total size of Exmortis.com main page is 816.5 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. 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 406.0 kB which makes up the majority of the site volume.
Potential reduce by 199.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 199.8 kB or 72% of the original size.
Potential reduce by 0 B
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. Ex Mortis images are well optimized though.
Potential reduce by 6.8 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 0 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. Exmortis.com has all CSS files already compressed.
Number of requests can be reduced by 16 (36%)
45
29
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ex Mortis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.exmortis.com
57 ms
minified.js
59 ms
focus-within-polyfill.js
53 ms
polyfill.min.js
1214 ms
thunderbolt-commons.90d0afc1.bundle.min.js
51 ms
main.63955c57.bundle.min.js
54 ms
main.renderer.1d21f023.bundle.min.js
52 ms
lodash.min.js
89 ms
react.production.min.js
89 ms
react-dom.production.min.js
91 ms
siteTags.bundle.min.js
90 ms
wix-perf-measure.umd.min.js
91 ms
6d590b_9f0dca0682b081b166a156c701823022.jpg
519 ms
6d590b_8fda227db5e85f6f1cfae06a16c3b476.gif
544 ms
6d590b_cae3b57ad7dc665b794865e8e3ebcd56.gif
546 ms
6d590b_2a8990a8407951d3781be64628241b17.gif
546 ms
6d590b_630e24264a327d529294c9592480e7fe.gif
557 ms
6d590b_00c75ffd9ce667a3e11608e4ca7db0f6.gif
557 ms
6d590b_1a37e7b2c1ebb86f27ae90aecd03fd53.gif
557 ms
6d590b_bb4f4e5b98c94a5690f1e2781b0f7b89~mv2.gif
561 ms
6d590b_29ec4883eabd7ef2fe30b51ac753985d.gif
565 ms
6d590b_3a477d5da13a28461972346fdee16392.gif
557 ms
6d590b_fe6a55ba7833acb7230ea6af3d6eb71b.gif
562 ms
6d590b_6c78d7191abc4a24bf6ebae2d2f05b34.gif
563 ms
6d590b_e9e54f87187319a236e993ce1efd2259.gif
562 ms
6d590b_bf1e43199fcde56bdc8d83beb65d531d.gif
566 ms
6d590b_6eca495668eddcddcdacc4c25017f087.gif
569 ms
6d590b_6f32032fc95a49abd3d5eb3b9505e474.gif
570 ms
6d590b_3faeba09cf1fcdd9ebc1a350a0b45f92.jpg
834 ms
6d590b_527acc8989ede97ae708aad5dea6e4f0.gif
579 ms
41d000_a96fb6a28b0bcbed15a5429475ea4d9a.png
681 ms
41d000_7c43da1d6220284c7b8ad8a66bd03db8.png
680 ms
6d590b_f96042cf43a1a697842a0a0c0ca32fcc.gif
584 ms
Qh-9U7qUcs4
149 ms
bundle.min.js
48 ms
297 ms
294 ms
291 ms
289 ms
289 ms
285 ms
409 ms
405 ms
408 ms
406 ms
400 ms
www-player.css
11 ms
www-embed-player.js
27 ms
base.js
55 ms
ad_status.js
172 ms
jBgyfngz26SfxQlNiQ6GVTB7xNcGg8C7SFNQ47_uFL0.js
127 ms
embed.js
38 ms
KFOmCnqEu92Fr1Mu4mxM.woff
49 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
60 ms
id
19 ms
Create
112 ms
GenerateIT
16 ms
qoe
9 ms
log_event
0 ms
deprecation-en.v5.html
5 ms
bolt-performance
18 ms
deprecation-style.v5.css
4 ms
right-arrow.svg
14 ms
WixMadeforDisplay_W_Bd.woff
8 ms
WixMadeforText_W_Bd.woff
10 ms
WixMadeforText_W_Rg.woff
10 ms
exmortis.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
Buttons do not have an accessible name
Links do not have a discernible name
exmortis.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
exmortis.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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exmortis.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Exmortis.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.
exmortis.com
Open Graph data is detected on the main page of Ex Mortis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: