55.9 sec in total
2.8 sec
50.9 sec
2.3 sec
Visit 91vs.com now to see the best up-to-date 91 Vs content for China and also check out these interesting facts you probably never knew about 91vs.com
91VS摔角网是专业提供WWE美国职业摔角在线观看和下载的网站
Visit 91vs.comWe analyzed 91vs.com page load time and found that the first response time was 2.8 sec and then it took 53.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
91vs.com performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value9.4 s
1/100
25%
Value13.8 s
1/100
10%
Value320 ms
76/100
30%
Value0.031
100/100
15%
Value7.4 s
49/100
10%
2757 ms
2719 ms
19718 ms
19718 ms
19719 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 91vs.com, 11% (15 requests) were made to Img.51vs.com and 6% (8 requests) were made to Rtb.behe.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Img.qiyou.com.
Page size can be reduced by 438.4 kB (26%)
1.7 MB
1.3 MB
In fact, the total size of 91vs.com main page is 1.7 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 36.2 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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.2 kB or 83% of the original size.
Potential reduce by 12.8 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. 91 Vs images are well optimized though.
Potential reduce by 374.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 374.8 kB or 74% of the original size.
Potential reduce by 14.6 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. 91vs.com needs all CSS files to be minified and compressed as it can save up to 14.6 kB or 81% of the original size.
Number of requests can be reduced by 49 (38%)
130
81
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 91 Vs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
www.51vs.com
2757 ms
style.css
2719 ms
jquery-1.8.2.min.js
19718 ms
jquery.rsli.1.0.js
19718 ms
common.js
19719 ms
inlay.js
1175 ms
view.php
9247 ms
stat.php
1713 ms
pre_dcqdkerk5pja.jpg
16830 ms
pre_6mdsvu3a2sdu.jpg
19986 ms
pre_vefjpku8j4su.jpg
14628 ms
pre_pypcrbym5pre.jpg
10271 ms
pre_bgppvqktkmnc_thumb.jpg
12477 ms
pre_3k9npkpua2sn_thumb.jpg
17038 ms
pre_hpkadeswbhhm_thumb.jpg
15904 ms
pre_tbrjuw24asvw_thumb.jpg
17161 ms
pre_t2cq5aqjrxpv_thumb.jpg
19331 ms
pre_m9xj55tcm9ft_thumb.jpg
18096 ms
pre_p8wpew2p5aar_thumb.jpg
19686 ms
pre_9juqxdw6mv6h_thumb.jpg
19191 ms
pre_8nxusxpxrvpf_thumb.jpg
19958 ms
bg.jpg
13255 ms
wrap.png
4231 ms
logo_1.gif
708 ms
metro.png
5946 ms
ex
1136 ms
ex
990 ms
throw
2096 ms
throw
5303 ms
stat.htm
241 ms
core.php
760 ms
spacegif.gif
2586 ms
stat.php
4465 ms
tanxssp.js
751 ms
20434 ms
main.js
16 ms
ex
4381 ms
ex
1969 ms
monitor.js
380 ms
m.js
384 ms
runtime.js
23 ms
rank.js
16 ms
logo2.png
1045 ms
acbeacon2.html
918 ms
spf
1968 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
261 ms
TB1DmIiHpXXXXbzXXXXO04pFXXX.html
926 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
250 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
246 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
247 ms
t.gif
4875 ms
tns.simba.taobao.com
3162 ms
imagelink.js
11 ms
t01d0b4402858f9df8d.jpg
604 ms
t01aa4160b5d8a0f89c.jpg
267 ms
t0178cffbd0c4618a25.jpg
20189 ms
t0158bcd9d1f1637ca4.jpg
20189 ms
t0179b9c53e07d8765b.jpg
265 ms
t0197538b13661f7775.jpg
2837 ms
t01b154d32bce00d41e.jpg
5705 ms
t01838252144871711f.jpg
279 ms
spf
650 ms
0.js
2466 ms
tc.js
2509 ms
TB2mdqgjpXXXXbqXpXXXXXXXXXX_!!25295936-2-saturn_solar.png_30x30.jpg
478 ms
T17hJxFCxXXXb1upjX.jpg
62 ms
s_cap_3.gif
1058 ms
tanxclick.js
51 ms
feature.htm
1184 ms
TB2jNYIfpXXXXayXpXXXXXXXXXX_!!11835946-0-saturn_solar.jpg_30x30.jpg
402 ms
TB2eYzPdVXXXXXPXpXXXXXXXXXX_!!30280853-0-saturn_solar.jpg_30x30.jpg
404 ms
T1EM42XbFgXXa7HzQ8_101236.jpg_30x30.jpg
404 ms
TB2SkuJaVXXXXX7XXXXXXXXXXXX_!!14441869-0-saturn_solar.jpg_30x30.jpg
404 ms
TB2HkoEiVXXXXXmXpXXXXXXXXXX_!!13642254-0-saturn_solar.jpg_30x30.jpg
408 ms
TB2do93aVXXXXXgXXXXXXXXXXXX_!!44926949-0-saturn_solar.jpg_30x30.jpg
410 ms
T1rWiIFz8aXXXXXXXX_!!0-item_pic.jpg_30x30.jpg
410 ms
TB2vfYXjVXXXXa4XpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
431 ms
TB2Q1lGgXXXXXcbXpXXXXXXXXXX_!!34905586-0-saturn_solar.jpg_30x30.jpg
431 ms
TB1RV7rJXXXXXXRXXXXXXXXXXXX_!!0-item_pic.jpg_30x30.jpg
428 ms
TB2ROpwgFXXXXb4XpXXXXXXXXXX_!!34249581-0-saturn_solar.jpg_30x30.jpg
428 ms
TB2_WQDbXXXXXXUXpXXXXXXXXXX_!!17391589-0-saturn_solar.jpg_30x30.jpg
437 ms
TB2ADmgcXXXXXbFXXXXXXXXXXXX_!!17391589-0-saturn_solar.jpg_30x30.jpg
450 ms
TB2MM_MjpXXXXarXpXXXXXXXXXX_!!46231993-0-saturn_solar.jpg_30x30.jpg
449 ms
TB2X1mjjFXXXXX.XpXXXXXXXXXX_!!109708667-0-saturn_solar.jpg_30x30.jpg
463 ms
TB2ORx1jXXXXXb4XpXXXXXXXXXX_!!12728412-0-saturn_solar.jpg_30x30.jpg
445 ms
TB2D1VLcpXXXXb9XXXXXXXXXXXX_!!96524635-0-saturn_solar.jpg_30x30.jpg
445 ms
TB2q111jpXXXXbRXXXXXXXXXXXX_!!30376030-0-saturn_solar.jpg_30x30.jpg
454 ms
TB1GHSXLpXXXXXpXVXXYXGcGpXX_M2.SS2_30x30.jpg
471 ms
TB2a0TojVXXXXcGXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
472 ms
TB2D.VahpXXXXchXXXXXXXXXXXX_!!96182559-0-saturn_solar.jpg_30x30.jpg
464 ms
TB2upV3gpXXXXaKXpXXXXXXXXXX_!!104055775-0-saturn_solar.jpg_30x30.jpg
445 ms
TB2sGZNeVXXXXXIXXXXXXXXXXXX_!!53559959-0-saturn_solar.jpg_30x30.jpg
447 ms
T1u.9hXe4hXXatY3UV_020624.jpg_30x30.jpg
465 ms
TB27Ep.fXXXXXaZXXXXXXXXXXXX_!!59225883-0-saturn_solar.jpg_30x30.jpg
465 ms
TB2_nSejXXXXXcRXXXXXXXXXXXX_!!12728412-0-saturn_solar.jpg_30x30.jpg
466 ms
TB2J8yhjVXXXXX6XXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
466 ms
TB2mdqgjpXXXXbqXpXXXXXXXXXX_!!25295936-2-saturn_solar.png_250x250.jpg
501 ms
T1AvVHFuNXXXb1upjX.jpg
23 ms
0.html
441 ms
behe_logo_v.png
515 ms
close1.png
19861 ms
jquery-1.9.1.js
10341 ms
app.gif
923 ms
TB2jNYIfpXXXXayXpXXXXXXXXXX_!!11835946-0-saturn_solar.jpg_250x250.jpg
17 ms
s_cap_4.gif
36 ms
um.js
769 ms
img
1255 ms
um.json
3428 ms
getDeviceInfo
1145 ms
TB2eYzPdVXXXXXPXpXXXXXXXXXX_!!30280853-0-saturn_solar.jpg_250x250.jpg
34 ms
T1EM42XbFgXXa7HzQ8_101236.jpg_250x250.jpg
10 ms
s_blue_5.gif
38 ms
getDeviceInfo
829 ms
TB2SkuJaVXXXXX7XXXXXXXXXXXX_!!14441869-0-saturn_solar.jpg_250x250.jpg
15 ms
TB2HkoEiVXXXXXmXpXXXXXXXXXX_!!13642254-0-saturn_solar.jpg_250x250.jpg
19 ms
s_cap_1.gif
46 ms
TB2do93aVXXXXXgXXXXXXXXXXXX_!!44926949-0-saturn_solar.jpg_250x250.jpg
11 ms
s_blue_4.gif
37 ms
T1rWiIFz8aXXXXXXXX_!!0-item_pic.jpg_250x250.jpg
16 ms
T1_qLZXoNjXXb.cabb-23-18.png
1349 ms
bhex
1206 ms
pixel
46 ms
t.gif
3894 ms
cm.gif
1002 ms
cm.mediav.com
2022 ms
pixel
30 ms
cm
473 ms
TB2vfYXjVXXXXa4XpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
16 ms
cm
476 ms
cm
472 ms
cm
448 ms
cm
471 ms
cm
500 ms
TB2Q1lGgXXXXXcbXpXXXXXXXXXX_!!34905586-0-saturn_solar.jpg_250x250.jpg
17 ms
s_blue_3.gif
35 ms
cm
492 ms
TB1RV7rJXXXXXXRXXXXXXXXXXXX_!!0-item_pic.jpg_250x250.jpg
14 ms
91vs.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
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
91vs.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
Browser errors were logged to the console
91vs.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 91vs.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 91vs.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.
91vs.com
Open Graph description is not detected on the main page of 91 Vs. 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: