11.9 sec in total
2.9 sec
7.7 sec
1.3 sec
Click here to check amazing 222 Mp content. Otherwise, check out these important facts you probably never knew about 222mp.com
-
Visit 222mp.comWe analyzed 222mp.com page load time and found that the first response time was 2.9 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
222mp.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value17.0 s
0/100
25%
Value18.0 s
0/100
10%
Value4,850 ms
0/100
30%
Value0.273
45/100
15%
Value16.6 s
5/100
10%
2889 ms
874 ms
676 ms
713 ms
1596 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 222mp.com, 85% (100 requests) were made to 29847798.s21i.faiusr.com and 7% (8 requests) were made to 1.ss.faisys.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain 222mp.com.
Page size can be reduced by 1.2 MB (53%)
2.2 MB
1.1 MB
In fact, the total size of 222mp.com main page is 2.2 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. 65% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 1.2 MB
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 1.2 MB or 96% of the original size.
Potential reduce by 22.2 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, 222 Mp needs image optimization as it can save up to 22.2 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 24 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 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. 222mp.com has all CSS files already compressed.
Number of requests can be reduced by 11 (58%)
19
8
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 222 Mp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
222mp.com
2889 ms
browserCheck.min.js
874 ms
main.e3858f4e.js
676 ms
main.2cb7bee5.css
713 ms
jzresponsivecusstyle.jsp
1596 ms
jquery.min.js
341 ms
jquery_ui.min.js
328 ms
jquery.mobile.min.js
324 ms
vue-2.7.14.min.js
330 ms
jzRequest.min.js
576 ms
jzUtils.min.js
624 ms
bizShared.min.js
652 ms
bizShared.min.css
637 ms
2052.min.js
642 ms
video.min.js
346 ms
hawkEye.min.js
240 ms
ABUIABADGAAgmsznsAYoko3TuAcwdTgg.gif
349 ms
ABUIABACGAAgneqesAYo6OKGowUwqAc4zgo.jpg
397 ms
vbg01.png
171 ms
AD0I9obbCRACGAAg_aHj6wUo-4rVmwIwiAQ42AQ.jpg
526 ms
ABUI9uGdDhBMGAAgodDzsAYohPqsngU
60 ms
ABUI9uGdDhBMGAAgodDzsAYowIu9wAU
805 ms
ABUI9uGdDhBMGAAgodDzsAYo3KaF5QY
993 ms
ABUI9uGdDhBMGAAgotDzsAYou5iauAQ
993 ms
ABUI9uGdDhBMGAAgotDzsAYojoL93QI
932 ms
ABUI9uGdDhBMGAAgotDzsAYo64vVVw
336 ms
ABUI9uGdDhBMGAAgotDzsAYo-K7c1gc
931 ms
ABUI9uGdDhBMGAAgotDzsAYo8LKQkgY
381 ms
ABUI9uGdDhBMGAAgo9DzsAYomtfVmQM
758 ms
ABUI9uGdDhBMGAAgo9DzsAYo873wuQc
802 ms
ABUI9uGdDhBMGAAgo9DzsAYouqia7gM
1548 ms
ABUI9uGdDhBMGAAgo9DzsAYosImJUA
863 ms
ABUI9uGdDhBMGAAgo9DzsAYooJWvtgQ
1833 ms
ABUI9uGdDhBMGAAgpNDzsAYo6JDYkQI
1335 ms
ABUI9uGdDhBMGAAgpNDzsAYo9e_pmwE
992 ms
ABUI9uGdDhBMGAAgpNDzsAYo8vXh5gY
992 ms
ABUI9uGdDhBMGAAgpNDzsAYo-7_PwgM
992 ms
ABUI9uGdDhBMGAAgpNDzsAYo4Pni3Ac
1055 ms
ABUI9uGdDhBMGAAgpNDzsAYoxtCIswQ
1463 ms
ABUI9uGdDhBMGAAgpdDzsAYotInamQM
1288 ms
ABUI9uGdDhBMGAAgpdDzsAYohprh7gE
1757 ms
ABUI9uGdDhBMGAAgpdDzsAYostqP1AY
1333 ms
ABUI9uGdDhBMGAAgpdDzsAYo8N368gY
1689 ms
ABUI9uGdDhBMGAAgpdDzsAYowLjPiAc
1398 ms
ABUI9uGdDhBMGAAgpdDzsAYozY-E7wE
2096 ms
ABUI9uGdDhBMGAAgpdDzsAYo1MHqngU
2046 ms
ABUI9uGdDhBMGAAgodDzsAYorMDC2QM
1547 ms
ABUI9uGdDhBMGAAgodDzsAYosOHY5QE
1617 ms
ABUI9uGdDhBMGAAgodDzsAYo6Pb8dA
1902 ms
ABUI9uGdDhBMGAAgodDzsAYo8Nv99AM
1972 ms
ABUI9uGdDhBMGAAgotDzsAYo7MD9-wc
1756 ms
ABUI9uGdDhBMGAAgotDzsAYo4LbniAc
2094 ms
ABUI9uGdDhBMGAAgotDzsAYo2saHmQY
1830 ms
ABUI9uGdDhBMGAAgotDzsAYosJ-LogU
1901 ms
ABUI9uGdDhBMGAAgotDzsAYoo_DjMw
2774 ms
ABUI9uGdDhBMGAAgo9DzsAYosJH22QU
2292 ms
ABUI9uGdDhBMGAAgo9DzsAYoh_qq_QU
2874 ms
ABUI9uGdDhBMGAAgo9DzsAYovfKBMQ
1719 ms
ABUI9uGdDhBMGAAgo9DzsAYo75bUlgM
1753 ms
ABUI9uGdDhBMGAAgo9DzsAYo_sq6ugQ
1390 ms
ABUI9uGdDhBMGAAgpNDzsAYopMfwtQQ
1389 ms
ABUI9uGdDhBMGAAgpNDzsAYorfiQvwM
1813 ms
ABUI9uGdDhBMGAAgpNDzsAYo5JmD8AM
1281 ms
ABUI9uGdDhBMGAAgpNDzsAYo9NOy7gY
1617 ms
ABUI9uGdDhBMGAAgpNDzsAYomKSo-QU
1623 ms
ABUI9uGdDhBMGAAgpNDzsAYo1NrSiAE
1391 ms
ABUI9uGdDhBMGAAgpdDzsAYoqJLRswY
1392 ms
ABUI9uGdDhBMGAAgpdDzsAYokNL6rQM
1838 ms
ABUI9uGdDhBMGAAgpdDzsAYoiKGcjgM
1915 ms
ABUI9uGdDhBMGAAgpdDzsAYosL7roQE
1959 ms
ABUI9uGdDhBMGAAgpdDzsAYonuyhvgI
1900 ms
ABUI9uGdDhBMGAAgpdDzsAYowNDxqwU
1499 ms
ABUI9uGdDhBMGAAgodDzsAYoroqJhAE
1569 ms
ABUI9uGdDhBMGAAgodDzsAYo4ZutlwY
1507 ms
ABUI9uGdDhBMGAAgodDzsAYokJq8eA
1462 ms
ABUI9uGdDhBMGAAgodDzsAYosPzxuwM
1380 ms
ABUI9uGdDhBMGAAgotDzsAYozsCi7wE
1445 ms
ABUI9uGdDhBMGAAgotDzsAYogLaqowM
1399 ms
ABUI9uGdDhBMGAAgotDzsAYo2MrO9gM
1325 ms
ABUI9uGdDhBMGAAgotDzsAYoiM2-jQM
1257 ms
ABUI9uGdDhBMGAAgotDzsAYo2aK9_gE
1238 ms
ABUI9uGdDhBMGAAgo9DzsAYo_KGT6wE
1185 ms
ABUI9uGdDhBMGAAgo9DzsAYo0KqOkwI
1164 ms
ABUI9uGdDhBMGAAgo9DzsAYomNrW0gI
1115 ms
ABUI9uGdDhBMGAAgo9DzsAYo3OOBfw
1094 ms
ABUI9uGdDhBMGAAgpNDzsAYoxIuStwc
1047 ms
ABUI9uGdDhBMGAAgpNDzsAYowPnnqgE
978 ms
ABUI9uGdDhBMGAAgpNDzsAYokYzkxAI
905 ms
ABUI9uGdDhBMGAAgpNDzsAYo_quItgY
904 ms
ABUI9uGdDhBMGAAgpNDzsAYoiKDGnwU
1059 ms
ABUI9uGdDhBMGAAgpNDzsAYozrr4Iw
969 ms
ABUI9uGdDhBMGAAgpdDzsAYo1IjokAQ
967 ms
ABUI9uGdDhBMGAAgpdDzsAYo0PCbygQ
967 ms
ABUI9uGdDhBMGAAgpdDzsAYondWwuwc
966 ms
ABUI9uGdDhBMGAAgpdDzsAYo0NzshwU
921 ms
ABUI9uGdDhBMGAAgpdDzsAYoloCSjgE
776 ms
ABUI9uGdDhBMGAAgodDzsAYosbONtgM
775 ms
ABUI9uGdDhBMGAAgodDzsAYo_qaifw
705 ms
ABUI9uGdDhBMGAAgodDzsAYozNj81wM
565 ms
ABUI9uGdDhBMGAAgodDzsAYorP-jkAI
487 ms
ABUI9uGdDhBMGAAgotDzsAYoktCFtAU
408 ms
ABUI9uGdDhBMGAAgotDzsAYo56mdiwQ
330 ms
ABUI9uGdDhBMGAAgotDzsAYos_DAhwY
329 ms
ABUI9uGdDhBMGAAgotDzsAYohI78uAI
257 ms
ABUI9uGdDhBMGAAgotDzsAYo1P28vgQ
257 ms
ABUI9uGdDhBMGAAgo9DzsAYo-IqoPQ
256 ms
ABUI9uGdDhBMGAAgo9DzsAYouPax6wQ
255 ms
ABUI9uGdDhBMGAAgo9DzsAYo65rs9QQ
256 ms
ABUI9uGdDhBMGAAgo9DzsAYolLiSiQY
208 ms
ABUI9uGdDhBMGAAgo9DzsAYo_6DG6wM
170 ms
ABUI9uGdDhBMGAAgpNDzsAYox7aOhgM
170 ms
ABUI9uGdDhBMGAAgpNDzsAYom8K0sAM
170 ms
ABUI9uGdDhBMGAAgpNDzsAYowOb7_gM
169 ms
ABUI9uGdDhBMGAAgpNDzsAYoq7v95gI
170 ms
ABUI9uGdDhBMGAAgpdDzsAYo_bGpgwE
169 ms
ABUI9uGdDhBMGAAgpdDzsAYo4KyAgQI
169 ms
ABUI9uGdDhBMGAAgpdDzsAYouNvmzgE
169 ms
ABUI9uGdDhBMGAAgpdDzsAYoxfT8gAI
168 ms
222mp.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
Image elements do not have [alt] attributes
Links do not have a discernible name
222mp.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
222mp.com 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
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 222mp.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 222mp.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.
222mp.com
Open Graph description is not detected on the main page of 222 Mp. 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: