61.7 sec in total
1.9 sec
59.5 sec
349 ms
Click here to check amazing Wjhfz content. Otherwise, check out these important facts you probably never knew about wjhfz.com
Visit wjhfz.comWe analyzed Wjhfz.com page load time and found that the first response time was 1.9 sec and then it took 59.8 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.
wjhfz.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.6 s
18/100
25%
Value6.5 s
40/100
10%
Value430 ms
65/100
30%
Value0.184
67/100
15%
Value5.3 s
73/100
10%
1944 ms
6374 ms
554 ms
593 ms
732 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 73% of them (116 requests) were addressed to the original Wjhfz.com, 6% (10 requests) were made to R.mapbar.com and 4% (6 requests) were made to Img.mapbar.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Wjhfz.com.
Page size can be reduced by 819.3 kB (30%)
2.8 MB
1.9 MB
In fact, the total size of Wjhfz.com main page is 2.8 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 144.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. This page needs HTML code to be minified as it can gain 43.1 kB, which is 26% 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 144.7 kB or 87% of the original size.
Potential reduce by 90.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. Wjhfz images are well optimized though.
Potential reduce by 547.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 547.2 kB or 70% of the original size.
Potential reduce by 36.7 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. Wjhfz.com needs all CSS files to be minified and compressed as it can save up to 36.7 kB or 79% of the original size.
Number of requests can be reduced by 62 (40%)
155
93
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wjhfz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
wjhfz.com
1944 ms
www.wjhfz.com
6374 ms
base.css
554 ms
global.css
593 ms
list.css
732 ms
scroll.css
1227 ms
xixun.css
726 ms
scroll.js
2637 ms
m.js
1321 ms
lbjs.js
1467 ms
tab.js
2281 ms
tslf.js
1790 ms
mobile.js
2644 ms
jquery1.42.min.js
2019 ms
lrtk.js
2590 ms
uaredirect.js
501 ms
Vizo-style.css
2082 ms
bannerPic.js
2089 ms
get_flash_player.gif
28 ms
redesigncase1_01.jpg
4793 ms
logo.jpg
2999 ms
logo2.jpg
17579 ms
logo3.jpg
8593 ms
tq.gif
1036 ms
qs_icon.jpg
2178 ms
sst.jpg
4513 ms
dj.jpg
5055 ms
redesigncase3.jpg
19501 ms
redesigncase4.jpg
20502 ms
icon_title.jpg
5542 ms
more_title.jpg
6068 ms
rl_img11.jpg
6576 ms
rl_img22.jpg
14580 ms
rl_img33.jpg
8399 ms
rl_img55.jpg
17112 ms
rl_img66.jpg
18836 ms
rl_img77.jpg
18166 ms
rl_img88.jpg
20376 ms
askzx.jpg
19799 ms
question_iocn.jpg
19367 ms
index.jsp
1364 ms
indexdi.html
19747 ms
swt.js
19018 ms
mapbar31.2.js
4220 ms
prototype.js
6630 ms
jquery-1.3.2.pack.js
3237 ms
template.js
6280 ms
common.jsp
1609 ms
infowindow2.js
6270 ms
cityDataWithBus.pack.js
5562 ms
sendtool.js
3717 ms
kwt.js
18026 ms
jquery_1.js
16528 ms
arrow_right.jpg
16802 ms
5-13061409352D26.jpg
16550 ms
byby_btn1.jpg
16625 ms
byby_btn2.jpg
17386 ms
mapbar.plugin.js
510 ms
jkwd.jpg
14509 ms
jkwd_line.jpg
13926 ms
bg_ckbg.png
629 ms
bg_ckbgA.gif
633 ms
bg_tools.gif
631 ms
mapbar31.2.1.png
2398 ms
49_44.png
3153 ms
48_43.png
3842 ms
49_43.png
3297 ms
bg_tagbut.gif
632 ms
bg_li.gif
636 ms
bg_butInp.gif
664 ms
biaozhu.gif
2861 ms
48_44.png
2044 ms
9_9.png
2843 ms
0_9.png
9233 ms
48_42.png
6476 ms
49_42.png
2073 ms
jkwd_more.jpg
8606 ms
tsjs_icon.jpg
6043 ms
redesigncase_width.gif
7536 ms
335.jpg
6798 ms
341.jpg
7552 ms
sss_05.jpg
4572 ms
sss_07.jpg
6169 ms
sss_03.jpg
4525 ms
hover.jpg
6036 ms
navbar_bg.jpg
4753 ms
nav_left.jpg
5271 ms
nav_right.jpg
5093 ms
nav_ge.jpg
5234 ms
search_btn.jpg
6491 ms
TabTitle_a.jpg
9713 ms
TabTitle_n.jpg
6931 ms
dian.jpg
6480 ms
redesigncase2_15.jpg
8145 ms
byby_title.jpg
7915 ms
byby_left.jpg
7317 ms
jkwd_icon.jpg
7223 ms
zlxm_07.jpg
8410 ms
TabTitle_a.jpg
8200 ms
TabTitle_n.jpg
9164 ms
347.jpg
20479 ms
334.jpg
12556 ms
stat.php
1110 ms
342.jpg
11027 ms
309.jpg
9214 ms
jquery.min.js
12991 ms
310.jpg
9989 ms
311.jpg
10467 ms
stat.htm
162 ms
core.php
669 ms
312.jpg
13607 ms
313.jpg
19603 ms
59.jpg
13855 ms
9.gif
1304 ms
pic1.gif
771 ms
ks.j
4712 ms
25.jpg
11825 ms
26.jpg
13427 ms
27.jpg
13851 ms
5_131025095442_1-lp.jpg
13611 ms
app.gif
4656 ms
4-12060G40430328-lp.jpg
12840 ms
zxdddd.jpg
13853 ms
yyhj_03.jpg
14427 ms
20110827095058765.jpg
13812 ms
20110827094949425.gif
19904 ms
20110827093947664.jpg
13779 ms
20110827093544666.jpg
15158 ms
20110827093627362.jpg
16695 ms
20110827092408983.jpg
15328 ms
20110827092615368.jpg
16817 ms
20110827093346540.jpg
15791 ms
20110827093439282.jpg
17123 ms
20110827093809575.gif
18942 ms
112.jpg
15443 ms
cvt.j
2014 ms
103.jpg
16833 ms
106.jpg
15196 ms
3947.jpg
15122 ms
107.jpg
16411 ms
113.jpg
16979 ms
5.jpg
16256 ms
kwt_cen.jpg
10877 ms
1.gif
2360 ms
01.gif
4168 ms
99.jpg
15176 ms
3946.jpg
14711 ms
114.jpg
18635 ms
1_11091041095436.jpg
14888 ms
1_092510323212c.jpg
14346 ms
1_1109105110a94.jpg
13516 ms
link_title.jpg
12230 ms
footer_bg.jpg
18385 ms
moni.htm
448 ms
banner_bottom1.jpg
15664 ms
banner_bottom2.jpg
14213 ms
moni.htm
449 ms
moni.htm
452 ms
wjhfz.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
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
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
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.
wjhfz.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
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
wjhfz.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 doesn't use legible font sizes
Tap targets are not sized appropriately
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wjhfz.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 Wjhfz.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
wjhfz.com
Open Graph description is not detected on the main page of Wjhfz. 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: