50.8 sec in total
1.8 sec
48.3 sec
653 ms
Welcome to vjson.com homepage info - get ready to check Vjson best content right away, or after learning these important things about vjson.com
专注于IT技术分享交流学习,每天进步一点点
Visit vjson.comWe analyzed Vjson.com page load time and found that the first response time was 1.8 sec and then it took 49 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
vjson.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value2.0 s
97/100
25%
Value5.3 s
57/100
10%
Value150 ms
95/100
30%
Value0
100/100
15%
Value3.1 s
95/100
10%
1820 ms
922 ms
3843 ms
7438 ms
19955 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 33% of them (17 requests) were addressed to the original Vjson.com, 12% (6 requests) were made to Bzclk.baidu.com and 12% (6 requests) were made to Imageplus.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Vjson.com.
Page size can be reduced by 325.6 kB (46%)
701.6 kB
376.0 kB
In fact, the total size of Vjson.com main page is 701.6 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. 30% of websites need less resources to load. Javascripts take 375.0 kB which makes up the majority of the site volume.
Potential reduce by 62.7 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 62.7 kB or 80% of the original size.
Potential reduce by 539 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. Vjson images are well optimized though.
Potential reduce by 219.2 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 219.2 kB or 58% of the original size.
Potential reduce by 43.1 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. Vjson.com needs all CSS files to be minified and compressed as it can save up to 43.1 kB or 80% of the original size.
Number of requests can be reduced by 29 (63%)
46
17
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vjson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
vjson.com
1820 ms
crayon.min.css
922 ms
classic.css
3843 ms
monaco.css
7438 ms
css
19955 ms
style.css
726 ms
style.css
860 ms
jquery.js
19955 ms
jquery-migrate.min.js
2587 ms
crayon.min.js
2765 ms
i.js
774 ms
c.js
1094 ms
navigation.js
1136 ms
buttons.png
4750 ms
rectengle.jpg
10842 ms
WeakReference_obj.jpg
3257 ms
LeakCanary-class-diagram.jpg
19960 ms
android-it.jpg
91 ms
android_deep_know.jpg
825 ms
js
1134 ms
monaco-webfont.woff
7935 ms
ui
531 ms
ui
409 ms
hm.js
547 ms
z_stat.php
1547 ms
eye.php
466 ms
ping
615 ms
hm.gif
298 ms
ui
334 ms
eye.php
516 ms
stat.htm
214 ms
core.php
1736 ms
ui
334 ms
eye.php
532 ms
9.gif
721 ms
pic.gif
1204 ms
wgxpath.install.js
507 ms
link
559 ms
app.gif
783 ms
nopic.jpg
561 ms
o.htm
962 ms
hm.gif
663 ms
ui
643 ms
ui
631 ms
wh.js
1177 ms
ac.js
888 ms
eye.php
599 ms
pa_lu_nobtn_inviewshow.app.js
5415 ms
eye.php
588 ms
fp.htm
704 ms
fp.htm
1305 ms
vjson.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
Form elements do not have associated labels
vjson.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
Browser errors were logged to the console
vjson.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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vjson.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Vjson.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.
vjson.com
Open Graph description is not detected on the main page of Vjson. 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: