7.9 sec in total
1.1 sec
5.5 sec
1.3 sec
Click here to check amazing Mortal Royale content. Otherwise, check out these important facts you probably never knew about mortalroyale.com
Become whoever you want in Mortal Online 2, the most immersive first person sandbox mmorpg of all time, Thousands of players in one world.
Visit mortalroyale.comWe analyzed Mortalroyale.com page load time and found that the first response time was 1.1 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mortalroyale.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value12.5 s
0/100
25%
Value10.6 s
7/100
10%
Value1,670 ms
11/100
30%
Value0.007
100/100
15%
Value33.4 s
0/100
10%
1144 ms
395 ms
581 ms
306 ms
461 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mortalroyale.com, 27% (35 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Tags.srv.stackadapt.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Mortalonline2.com.
Page size can be reduced by 174.5 kB (3%)
5.1 MB
4.9 MB
In fact, the total size of Mortalroyale.com main page is 5.1 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 168.4 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 168.4 kB or 85% of the original size.
Potential reduce by 23 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. Mortal Royale images are well optimized though.
Potential reduce by 298 B
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 5.9 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. Mortalroyale.com has all CSS files already compressed.
Number of requests can be reduced by 74 (82%)
90
16
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mortal Royale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
www.mortalonline2.com
1144 ms
wp-emoji-release.min.js
395 ms
style.min.css
581 ms
common-style.css
306 ms
style-index.css
461 ms
classic-themes.min.css
332 ms
styles.css
365 ms
cookie-law-info-public.css
597 ms
cookie-law-info-gdpr.css
779 ms
sbttb-fonts.css
632 ms
smooth-back-to-top-button.css
655 ms
style.min.css
725 ms
style.min.css
924 ms
header-footer-elementor.css
886 ms
elementor-icons.min.css
925 ms
custom-frontend.min.css
927 ms
swiper.min.css
1107 ms
post-8.css
899 ms
custom-pro-frontend.min.css
2515 ms
all.min.css
1248 ms
v4-shims.min.css
1198 ms
post-3040.css
933 ms
frontend.css
1218 ms
post-4578.css
1349 ms
cms-navigation-base.css
1370 ms
cms-navigation.css
1521 ms
style.min.css
1565 ms
theme.min.css
1585 ms
post-3059.css
1687 ms
post-4261.css
1660 ms
css
37 ms
fontawesome.min.css
1793 ms
solid.min.css
1852 ms
brands.min.css
1874 ms
language-cookie.js
1926 ms
jquery.min.js
1962 ms
jquery-migrate.min.js
2058 ms
cookie-law-info-table.css
2120 ms
animations.min.css
1921 ms
cookie-law-info-public.js
1988 ms
v4-shims.min.js
1897 ms
lazysizes.min.js
1943 ms
script.js
1995 ms
smooth-back-to-top-button.js
2077 ms
jquery.smartmenus.min.js
2053 ms
imagesloaded.min.js
2026 ms
webpack-pro.runtime.min.js
2031 ms
webpack.runtime.min.js
2046 ms
frontend-modules.min.js
2218 ms
wp-polyfill-inert.min.js
1975 ms
regenerator-runtime.min.js
2035 ms
wp-polyfill.min.js
2078 ms
hooks.min.js
1895 ms
i18n.min.js
2107 ms
frontend.min.js
2140 ms
waypoints.min.js
2046 ms
core.min.js
2006 ms
frontend.min.js
2197 ms
elements-handlers.min.js
2021 ms
jquery.sticky.min.js
1967 ms
underscore.min.js
1997 ms
wp-util.min.js
1943 ms
frontend.min.js
1908 ms
gtm.js
159 ms
loading_mobile_background_v3.jpg
802 ms
great-background-v8.jpg
1034 ms
lineanddot.png
1134 ms
20231026173820_1.jpg
1120 ms
login-screen-clean.jpg
945 ms
Duel-taunt.jpg
1214 ms
unknown-2022-04-01T182353.499.jpg
1245 ms
imagemixfinalv2.png
1241 ms
image5.jpg
1301 ms
KFOmCnqEu92Fr1Mu4mxM.woff
41 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
57 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
57 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
57 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
40 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
56 ms
j8_v6-zQ3rXpceZj9cqnViF-Png.woff
122 ms
j8_y6-zQ3rXpceZj9cqnVimhGmuta7Q.woff
120 ms
j8_y6-zQ3rXpceZj9cqnVinFG2uta7Q.woff
121 ms
font
127 ms
fa-brands-400.woff
1572 ms
fa-solid-900.woff
1626 ms
fa-regular-400.woff
1556 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff
56 ms
font
56 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff
58 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff
56 ms
font
58 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff
58 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff
117 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff
115 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8JoA.woff
116 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvQ.woff
116 ms
font
121 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvQ.woff
118 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5a7dvQ.woff
125 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvQ.woff
118 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba5a7dvQ.woff
122 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvQ.woff
119 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja5a7dvQ.woff
123 ms
o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvQ.woff
125 ms
ke8iOgUHP1dg-Rmi6RWjbLE_htaa.woff
119 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
120 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
120 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
121 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
122 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
123 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
122 ms
wpxpress.ttf
1477 ms
analytics.js
68 ms
pixel.js
80 ms
uwt.js
84 ms
fbevents.js
166 ms
events.js
80 ms
collect
25 ms
rp.gif
53 ms
t2_i0aa0lr6_telemetry
19 ms
rp.gif
55 ms
sa.css
9 ms
collect
101 ms
js
39 ms
adsct
177 ms
adsct
111 ms
adsct
126 ms
adsct
204 ms
saq_pxl
30 ms
ga-audiences
35 ms
mortalroyale.com 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
Links do not have a discernible name
mortalroyale.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
mortalroyale.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 Mortalroyale.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 Mortalroyale.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.
mortalroyale.com
Open Graph data is detected on the main page of Mortal Royale. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: