50.9 sec in total
1.1 sec
49.1 sec
714 ms
Click here to check amazing Jingzhuzangyao content for China. Otherwise, check out these important facts you probably never knew about jingzhuzangyao.com
青海晶珠藏药高新技术产业股份有限公司
Visit jingzhuzangyao.comWe analyzed Jingzhuzangyao.com page load time and found that the first response time was 1.1 sec and then it took 49.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. 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.
jingzhuzangyao.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value73.9 s
0/100
25%
Value17.7 s
0/100
10%
Value160 ms
93/100
30%
Value0.718
7/100
15%
Value37.9 s
0/100
10%
1118 ms
858 ms
433 ms
1299 ms
2175 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 75% of them (107 requests) were addressed to the original Jingzhuzangyao.com, 20% (28 requests) were made to Www4c1.53kf.com and 3% (4 requests) were made to Idm-su.baidu.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Ztouch4.gather.shushang-z.cn.
Page size can be reduced by 2.5 MB (35%)
7.1 MB
4.6 MB
In fact, the total size of Jingzhuzangyao.com main page is 7.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. 55% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 61.1 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 11.5 kB, which is 15% 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 61.1 kB or 81% of the original size.
Potential reduce by 1.9 MB
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. Obviously, Jingzhuzangyao needs image optimization as it can save up to 1.9 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 546.4 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 546.4 kB or 70% of the original size.
Potential reduce by 5.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. Jingzhuzangyao.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 21% of the original size.
Number of requests can be reduced by 32 (23%)
137
105
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jingzhuzangyao. 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 from 8 to 1 for CSS and as a result speed up the page load time.
jingzhuzangyao.com
1118 ms
lib.min-1547111889220.css.css
858 ms
page_index.min-1547111889220.css.css
433 ms
jquery.js
1299 ms
lib.min.js
2175 ms
Js1.js
1308 ms
style.css
643 ms
jquery.pagepiling.css
648 ms
examples.css
859 ms
lrtk.css
864 ms
lrtk.js
1071 ms
visittrack.js
651 ms
su_new.js
655 ms
EasePack.min.js
860 ms
TweenLite.min.js
869 ms
verge.min.js
879 ms
start.js
1288 ms
jquery.min.js
1306 ms
memoryDesign.js
1308 ms
iealert.js
1099 ms
woodapple.js
1100 ms
jquery.pagepiling.min.js
1314 ms
d996ac23-7eb3-438b-b4a9-6d1c379d.png
449 ms
8a332204-b922-44e9-a6f6-6fc310ae.png
217 ms
4518ab7d-568e-4e07-840c-1db2235f.png
229 ms
608e17fb-97ad-4924-aa50-5bb06b5a.png
231 ms
94ae142e-e6a4-4c43-80e6-80cae943.png
1114 ms
87dff462-85b7-4b5d-81fb-6d2235a3.png
232 ms
1c67d2eb-773d-4ebc-a71a-a4bbb6f2.png
1522 ms
004bfded-6420-4d92-bae6-73c618d4.png
451 ms
fccb8600-ae51-487e-ad0f-344f5172.png
679 ms
58bb4522-4d1d-4355-9569-67ab1010.png
682 ms
6b4b843c-3ba6-49e9-96ab-3559b79d.png
884 ms
13e49e13-1a7d-4759-88b9-dcd5cad6.png
933 ms
85df8116-3f77-4c5e-a864-624db774.png
901 ms
4dfae932-723a-47da-8ec9-13ede9a8.png
905 ms
de9c7350-1a68-4be1-b18d-72cb0643.png
1319 ms
92ac3ab6-045b-4320-88d6-d9489781.png
1337 ms
87c8c36a-2764-4883-929b-ab69a299.png
1344 ms
f93bc65a-9db1-43f9-838f-4b285b2a.png
1368 ms
d8247323-0ccb-422e-a009-1e5f0c53.png
1548 ms
af730b18-5077-476d-be79-ac9b5fc2.png
1756 ms
4dec2f08-ae09-4007-959c-24c8b9cb.png
1554 ms
4c86cf7a-131f-40d9-9365-867da1a9.png
1563 ms
b71fe15f-4954-45d5-902d-94d6f2fd.png
1586 ms
d184f75d-92d1-4a65-87d0-c2d6e570.png
1953 ms
eb0c2db3-e6aa-487d-94b0-3a65c844.png
1983 ms
4aca1515-c599-4670-8e45-2eaa0d23.png
1776 ms
35e4980e-f407-4876-9f2b-45e2d7c8.png
1784 ms
2af601cf-3e36-406e-9b47-e435453f.png
1804 ms
c55fff48-9d58-401a-a386-110bd957.png
1974 ms
9f9ea815-a0bc-4e7d-97ea-e5d27476.png
1993 ms
4be43e84-1581-4365-b07d-28105b21.png
2003 ms
335e0cdc-1c6b-4e12-a1a6-560f7af5.png
2023 ms
22ca3db6-8060-44b9-8ac4-0ab9b30b.png
2169 ms
0002.png
2193 ms
0001.png
2200 ms
7f8d68f1-0754-4364-b4e3-14486960.png
2203 ms
1
1017 ms
trace.do
20136 ms
su.png
827 ms
aayqlj.html
2010 ms
cc4a5e30-0d3c-4025-bbcd-112338db.png
2017 ms
bc2faf52-f363-427c-9382-96faff0d.png
2160 ms
30c36b6b-96e1-4cb6-b1e6-4895c157.png
2400 ms
0ee36caf-8399-4125-8397-1e679907.png
1978 ms
091c8840-e9da-41a0-ba5b-4f66d953.png
2198 ms
70588d23-09cb-4508-89b9-b3a0b7d8.png
1982 ms
88e5fb38-ea94-455f-9075-f8af6d15.png
1784 ms
4d5d35a1-212a-4eb7-982f-42e47575.png
1724 ms
9eea4b80-534d-4577-b985-76bd46d3.png
1957 ms
2463d688-110c-48af-ac87-81e7cadd.png
1783 ms
9e78c8a5-c719-410a-9118-d5299e97.png
1896 ms
su.png
830 ms
sendacc.jsp
675 ms
mobile_icon_72027951_1.js
884 ms
mobile_invite_72027951_1.js
888 ms
assign_worker_72027951_1.js
889 ms
mobile_chat_default.js
924 ms
kf_new.php
974 ms
bc25a6c7-d0ab-4c7c-a163-16505f16.png
1737 ms
22a91752-6e38-4990-a607-5c930db6.png
1764 ms
8253800e-869a-4604-ab97-18448744.png
1545 ms
4971ba62-e57f-46f4-b77d-0fcc5b70.png
1565 ms
39f5ab6e-387e-45dc-9e96-91f0f44a.png
1680 ms
38bf1513-0b90-49a7-8afe-3d88e6a0.png
1551 ms
06351632-f04e-4a32-913e-ebdbd356.png
1528 ms
4ec8fa75-e6bb-4e6e-b0ba-630fa90f.png
1547 ms
78585abb-5a82-4465-929b-f4102d92.png
1563 ms
d552e98a-42b8-46f1-80c8-1e4ed996.png
1678 ms
334e49f7-881f-4ca8-aae5-4c660039.png
1532 ms
c71a9f96-d493-41b8-a57e-1b857b2b.png
1520 ms
254b86a6-55d2-4e01-aa11-4d01142e.jpg
1517 ms
7cf432e8-a43b-4a37-9a8e-42233318.png
1512 ms
sy_1_01.png
7373 ms
2-24_02.png
3056 ms
dier.png
1522 ms
2-24_03.png
2204 ms
2-24_05.png
3519 ms
2-24_06.png
5778 ms
kf_ivt_new.php
437 ms
icon_off_58361464856000.jpg
873 ms
icon_off_64791464856000.gif
291 ms
2-24_07.png
3997 ms
2-24_09.png
4445 ms
diba_03.png
3048 ms
2-24_11.jpg
3913 ms
page_aayqlj.min-1547111889220.cs.css
3516 ms
Js9.js
3713 ms
btn.png
3786 ms
sy8_08.png
3917 ms
elevator.png
3919 ms
commonbg_1.png
396 ms
closebtn_1.png
218 ms
otherimg_11.png
433 ms
clickbtn_81.png
198 ms
mobile_53kf_1411888505.png
831 ms
jquery-1.4.2.flp.js
207 ms
minkh.php
222 ms
client.css
202 ms
placedata_minkh.js
201 ms
hz6d_iframe_proxy.html
249 ms
07a02eb2-c06f-412b-a851-5d4fe108.jpg
433 ms
e7998d8a-c370-44df-894e-896d21ea.jpg
598 ms
46e7bde2-bc48-45b2-8346-3c7be74d.jpg
643 ms
0ff79910-8c4b-4b4b-a4b7-fa38af0f.jpg
649 ms
752ded1b-9d30-4542-bfb2-68e0e257.jpg
813 ms
4c1fbaf8-2a6b-4357-8b7f-5f973127.jpg
859 ms
a3566d4d-807a-4b70-b38f-22d25a80.jpg
866 ms
12d77787-c4a3-435a-85a0-668b3336.jpg
895 ms
trace.do
20156 ms
su.png
197 ms
su.png
237 ms
53kf_6d_logo.png
19993 ms
mnkf_ad_img.jpg
597 ms
mnkf_bg_rx2.png
404 ms
mnkf_icons.png
431 ms
6d_icon.png
649 ms
6d_icon.png
647 ms
6d_icon.png
802 ms
6d_icon.png
846 ms
rpc_new_sqb.php
301 ms
rpc_new_sqb.php
370 ms
jingzhuzangyao.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
jingzhuzangyao.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
Detected JavaScript libraries
Browser errors were logged to the console
jingzhuzangyao.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
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jingzhuzangyao.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 Jingzhuzangyao.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.
jingzhuzangyao.com
Open Graph description is not detected on the main page of Jingzhuzangyao. 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: