44.7 sec in total
1.6 sec
42.5 sec
661 ms
Click here to check amazing Vx content for China. Otherwise, check out these important facts you probably never knew about vx.com
vx.com
Visit vx.comWe analyzed Vx.com page load time and found that the first response time was 1.6 sec and then it took 43.1 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. Unfortunately, there were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vx.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value8.1 s
2/100
25%
Value13.5 s
2/100
10%
Value410 ms
67/100
30%
Value0.214
58/100
15%
Value13.1 s
12/100
10%
1552 ms
7117 ms
1227 ms
11736 ms
983 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 40% of them (37 requests) were addressed to the original Vx.com, 53% (49 requests) were made to Img.vx.com and 1% (1 request) were made to S17.cnzz.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img.vx.com.
Page size can be reduced by 473.0 kB (42%)
1.1 MB
665.6 kB
In fact, the total size of Vx.com main page is 1.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. 35% of websites need less resources to load. Images take 574.9 kB which makes up the majority of the site volume.
Potential reduce by 56.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 11% 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 56.8 kB or 82% of the original size.
Potential reduce by 37.1 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. Vx images are well optimized though.
Potential reduce by 206.9 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 206.9 kB or 72% of the original size.
Potential reduce by 172.2 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. Vx.com needs all CSS files to be minified and compressed as it can save up to 172.2 kB or 82% of the original size.
Number of requests can be reduced by 21 (29%)
73
52
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vx. 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.
vx.com
1552 ms
www.vx.com
7117 ms
bootstrap.min.css
1227 ms
vxnewsbootstrap.css
11736 ms
default.css
983 ms
wind.js
2877 ms
jquery.js
5851 ms
jquery-migrate-1.2.1.js
3934 ms
api.php
1634 ms
api.php
2049 ms
bootstrap.min.js
862 ms
common.js
3845 ms
common_public.js
3055 ms
scroll_gallery.js
1926 ms
api.php
2535 ms
stat.php
1896 ms
56d7f963b475f.jpg
2697 ms
group.png
527 ms
logo.png
2557 ms
icon.png
1503 ms
nav_bg.png
2112 ms
hot.gif
482 ms
13_sm_loader.gif
401 ms
n_scroll.png
2014 ms
blank.gif
991 ms
qrcode_vx.jpg
11204 ms
56d7ed600740c.jpg
1982 ms
thumb_240_190_564938b3d6f87.jpg
3059 ms
thumb_240_190_564932dc5b34b.jpg
1599 ms
thumb_240_205_570319d4e01aa.png
5813 ms
thumb_240_205_57047c3ba6471.jpg
1720 ms
thumb_240_205_5703c68ad6151.jpg
4130 ms
thumb_240_205_5703c550117c2.jpg
2112 ms
thumb_240_205_5704a0c59d166.jpg
3492 ms
thumb_240_205_5703b227c8c0b.jpg
2530 ms
thumb_240_190_57076484d5a09.jpg
4443 ms
thumb_240_190_57073fde6e923.png
13350 ms
thumb_240_190_570620ad83b29.jpg
6093 ms
thumb_240_190_5704b6d445898.jpg
6060 ms
thumb_240_190_56fd39a670d84.png
14386 ms
thumb_240_190_56ffb928503ab.png
18456 ms
thumb_240_190_565d908947ff7.jpg
7632 ms
thumb_240_190_56167c3a19ad3.jpg
7380 ms
thumb_240_190_20131203090349361.png
15251 ms
thumb_240_190_56c81558ea357.png
17074 ms
thumb_240_190_20130702112712698.jpg
9346 ms
thumb_400_260_570746771c015.gif
9800 ms
thumb_400_260_570746f80819c.jpg
11457 ms
thumb_400_260_5707489c68089.jpg
15349 ms
thumb_400_260_57076484d5a09.jpg
19525 ms
thumb_400_260_570751cf2577f.png
19525 ms
thumb_400_260_5707577a1fb35.jpg
17780 ms
thumb_400_260_57075733e15fb.jpg
19173 ms
thumb_400_260_57075d1a225d0.png
19524 ms
thumb_400_260_57075e2ec63de.jpg
19525 ms
thumb_400_260_57075e77d799c.jpg
19524 ms
thumb_400_260_57075fb309220.jpg
19525 ms
thumb_400_260_57076206e6e8e.jpg
19525 ms
thumb_400_260_570794e64f500.jpg
19525 ms
thumb_400_260_5707643c7a189.jpg
19525 ms
thumb_200_200_569edcb26fef1.jpg
19525 ms
blue_index.jpg
1955 ms
vxicon.png
9678 ms
glyphicons-halflings-regular.woff
8201 ms
artDialog.js
5385 ms
iframeTools.js
4823 ms
api.php
3033 ms
user-center-pic77.png
3515 ms
footLiBg.gif
4055 ms
stat.htm
259 ms
core.php
1764 ms
90x90.jpg
19080 ms
thumb_200_200_569d979d3438e.jpg
19806 ms
9.gif
4030 ms
jquery.lazyload.min.js
3026 ms
jquery.scrollup.min.js
4517 ms
jquery.jSuggest.js
7280 ms
api.php
4437 ms
api.php
8339 ms
thumb_200_200_569736418730a.jpg
18663 ms
thumb_200_200_5694bd2f3480f.jpg
18936 ms
thumb_200_200_5695eb2c74b10.jpg
18231 ms
thumb_200_200_567a79966d902.png
19839 ms
thumb_200_200_566a699c1597f.jpg
18726 ms
thumb_200_200_566694d07a73c.jpg
17874 ms
563864971c094.jpg
20341 ms
56d7e83a94479.jpg
20082 ms
56e2924fc966e.jpg
19713 ms
app.gif
1187 ms
563864e96871a.jpg
20465 ms
5563e041352f8.png
18978 ms
gototop.png
543 ms
vx.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vx.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
vx.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
Tap targets are not sized appropriately
![]()
N/A
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vx.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Vx.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.
vx.com
Open Graph description is not detected on the main page of Vx. 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: