48.9 sec in total
539 ms
47.9 sec
515 ms
Welcome to qhj.cn homepage info - get ready to check Qhj best content right away, or after learning these important things about qhj.cn
Visit qhj.cnWe analyzed Qhj.cn page load time and found that the first response time was 539 ms and then it took 48.4 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.
qhj.cn performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.0 s
49/100
25%
Value4.3 s
76/100
10%
Value340 ms
74/100
30%
Value0.094
91/100
15%
Value8.5 s
38/100
10%
539 ms
930 ms
1804 ms
1119 ms
475 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Qhj.cn, 16% (13 requests) were made to Cpro.baidustatic.com and 16% (13 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 413.1 kB (25%)
1.6 MB
1.2 MB
In fact, the total size of Qhj.cn main page is 1.6 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 18.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 18.7 kB or 83% of the original size.
Potential reduce by 6.4 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. Qhj images are well optimized though.
Potential reduce by 386.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 386.2 kB or 67% of the original size.
Potential reduce by 1.8 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. Qhj.cn needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 68% of the original size.
Number of requests can be reduced by 25 (32%)
78
53
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qhj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
479.dragonparking.com
539 ms
oneclick.css
930 ms
client2.js
1804 ms
track.js
1119 ms
dp.js
475 ms
ci.js
701 ms
c.js
1015 ms
f.js
1017 ms
f.js
827 ms
2025
79 ms
qq.jpg
1470 ms
biz2.jpg
19555 ms
fcem
692 ms
fcem
794 ms
fcem
713 ms
fcem
734 ms
fcem
828 ms
fcem
1087 ms
ls.js
275 ms
ls_flowbar.js
326 ms
home
1057 ms
fcem
2812 ms
fcem
3032 ms
fcem
5259 ms
fcem
6872 ms
fcem
4720 ms
fcem
6523 ms
xuanfu_close.png
459 ms
adx.php
881 ms
jquery_a4373ccd.js
546 ms
cpro.js
822 ms
adx.php
714 ms
arrow_left_60_e700a3bb.png
328 ms
arrow_left_50_1dfda915.png
585 ms
adx.php
1198 ms
adx.php
383 ms
u=3492775180,3053852274&fm=76
1924 ms
u=1364289134,2040624832&fm=76
20271 ms
u=492649758,4136142410&fm=76
5642 ms
bg.png
527 ms
reduce_bd-logo1_oper.png
593 ms
u=1496671384,950133907&fm=76
7212 ms
u=2121025579,2884219392&fm=76
5713 ms
u=1952165730,2783937158&fm=76
15581 ms
u=3453366020,4067188265&fm=76
3719 ms
adx.php
410 ms
u=917210101,1928570698&fm=76
3256 ms
u=1836872761,2313555235&fm=76
9529 ms
u=3059151468,3543266969&fm=76
4306 ms
u=1886383005,2258690469&fm=76
5644 ms
u=3638187594,3625324374&fm=76
2198 ms
u=3487477169,3169452735&fm=76
1851 ms
u=1914936128,2171640819&fm=76
1986 ms
u=688944986,4152436923&fm=76
7551 ms
icon_12px.png
520 ms
adx.php
464 ms
u=852391891,1035378621&fm=76
19794 ms
u=1378038637,1917658524&fm=76
7010 ms
u=3631708702,3929097240&fm=76
4052 ms
u=3300308898,3553001008&fm=76
728 ms
u=1063916820,1256237774&fm=76
7875 ms
u=3434588058,4231195861&fm=76
4793 ms
u=895584870,1003569823&fm=76
17198 ms
u=1957638900,2277614173&fm=76
6528 ms
u=1324301525,2489217917&fm=76
4060 ms
u=1474580414,2089030550&fm=76
4584 ms
u=2005515776,2722123731&fm=76
5700 ms
u=2053575326,2288407978&fm=76
5338 ms
u=3792442396,180395522&fm=76
9445 ms
u=1539087117,1142082672&fm=76
4112 ms
u=272191502,886421432&fm=76
15056 ms
u=1282722014,1552229938&fm=76
12437 ms
closefeedback.min.js
534 ms
u=670502524,3988544191&fm=76
8500 ms
u=948029639,1247973789&fm=76
19706 ms
u=1936533728,2734871428&fm=76
5998 ms
reduce_promotion_oper.png
597 ms
bd_logo.png
589 ms
bg_rb.png
607 ms
1.gif
144 ms
o.htm
1608 ms
ac.js
947 ms
wh.js
1305 ms
qhj.cn 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
qhj.cn 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
Missing source maps for large first-party JavaScript
qhj.cn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qhj.cn 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Qhj.cn 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.
qhj.cn
Open Graph description is not detected on the main page of Qhj. 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: