9.4 sec in total
666 ms
8.4 sec
378 ms
Welcome to hzins.com homepage info - get ready to check Hzins best content for China right away, or after learning these important things about hzins.com
慧择,中国知名互联网保险平台,纳斯达克上市公司,业务涵盖大病保险、意外保险、财产保险、健康保险、旅游保险、儿童保险、人寿保险和家庭保险等,同时提供保险资讯、保险咨询、保险方案定制、智能核保、保单保全、协助理赔等一站式保险服务。
Visit hzins.comWe analyzed Hzins.com page load time and found that the first response time was 666 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hzins.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value18.7 s
0/100
25%
Value16.0 s
0/100
10%
Value740 ms
40/100
30%
Value0.103
89/100
15%
Value17.9 s
4/100
10%
666 ms
786 ms
1776 ms
1024 ms
695 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hzins.com, 57% (46 requests) were made to Hz.huizecdn.com and 19% (15 requests) were made to Img.huizecdn.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Hmcdn.baidu.com.
Page size can be reduced by 805.6 kB (28%)
2.9 MB
2.1 MB
In fact, the total size of Hzins.com main page is 2.9 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 587.4 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 587.4 kB or 87% of the original size.
Potential reduce by 78.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. Hzins images are well optimized though.
Potential reduce by 139.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 139.2 kB or 15% of the original size.
Potential reduce by 528 B
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. Hzins.com has all CSS files already compressed.
Number of requests can be reduced by 48 (62%)
77
29
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hzins. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hzins.com
666 ms
www.huize.com
786 ms
www.huize.com
1776 ms
animate.min.css
1024 ms
hznewga.min.js
695 ms
hznewga.min.js
1651 ms
analytics.js
716 ms
generate-window.min.js
696 ms
scale.js
697 ms
index.min.js
711 ms
646595744edcfe5b5e84.css
928 ms
abb32344eba1e181d662.css
1222 ms
1e60119ab4f2414fa1cb.css
1125 ms
92152a6a58b6cf5ceca0.css
787 ms
1de7fa562cc62dce2ddc.css
811 ms
polyfills-4ee02414775b5a0ce6d9.js
783 ms
main-48e81aeb99ce62eda163.js
245 ms
webpack-a2db5744fee61346eaac.js
310 ms
framework.6b751b1b01add178b851.js
375 ms
75fc9c18.7e362f03915ac2c216ca.js
387 ms
43768d8f.c6811bde3747677fdf89.js
448 ms
commons.65bbc1ec3e293e6c7818.js
452 ms
9691ec1e60ab723939e7e5ac24650a1e72cb55fd.413751af7f2342bc40ee.js
872 ms
69202e9fb54260c2cfe9ef2bad983362bdae8b82.fd5e17466b15f4c419bb.js
499 ms
f6078781a05fe1bcb0902d23dbbb2662c8d200b3.18a46bfe584dc0928376.js
520 ms
_app-1e677f52f5115f0eb7b5.js
781 ms
01253bc4.92b8b1878549d89d9cf2.js
574 ms
66b882c1a6e0dc1dcaa42672977b21ea958a7006.f52246fd8d1761e91c9f.js
802 ms
66b882c1a6e0dc1dcaa42672977b21ea958a7006_CSS.bbf891a3461cc9dcfc12.js
780 ms
3e87d11493bee1e7a01fbe63fb4a3658ce5de7a8.cf5fe3d700503f77a145.js
780 ms
49258624b066b29b02266d4e36b21c71abf350f8.40f1c1a8d6a797fcf67f.js
872 ms
f63924740fcbc61cf228c01b4be77fa70d8845d7.be4a579b1acbd0b0fc26.js
874 ms
86ff851091054c5e6a267d44f72baa8dbc6b78f5.99d5af147877c145d792.js
874 ms
e57dc3b80a590f4db776b885565840754ce4cbb7.754f18f0081d77085ea4.js
876 ms
31c5949800cac4c153428c80938fe596a4a0fe08.12016820112f2d1e67b5.js
874 ms
902b23efe8ba7f949f153cbaca976c70d0dc48aa.0cc5ad5783617c06396b.js
872 ms
479095edecd82a69b1737c31079626d386deaa63.f7a6a28e0649dc099a6b.js
915 ms
0d600b7d2d451892571260297675fb36065c5a68.88c585057a2008d83017.js
912 ms
372e5d4fd00b5dc4f3a1693df8eefae2c7b2d06b.f655d03c218093ac96c6.js
911 ms
02196f5ec909ffeadc8e530b945731ff1cdebece.2b43ec9715b18ff2b82e.js
939 ms
372e5d4fd00b5dc4f3a1693df8eefae2c7b2d06b_CSS.d87633962092d7962783.js
884 ms
index-ac181857ce339c291b64.js
896 ms
_buildManifest.js
915 ms
_ssgManifest.js
900 ms
logo1.gif
535 ms
5cc54f4a-a4e7-46ff-afe3-82db296ce7f9.png
1118 ms
CgUA3GEVVF2ATP6XAACrnibtNZ4821.png
1109 ms
CgUA3GEVVSSABV2-AAClCoYZUBM534.png
1399 ms
CgUA3GEVWw-AZBgTAACfgfm1GdA069.png
1425 ms
CgUA3GEVWcKANjHJAACYfkS-QeM904.png
2501 ms
CgUA3GEVXBaAG6xkAADNqh2XXmg173.png
1901 ms
CgUA3GEVXYeAGdBZAACvtAeLWRQ088.png
1846 ms
CgUA3GEVYCuAAGFNAADz7cqIGo4802.png
2043 ms
rBYA3GKVy5iAPcBBAAOtNoVjuZE756.png
1616 ms
CgUA3GEVYSuAJQLUAAEKJKsiCSA421.png
2331 ms
CgUA3GEVY6iAfc62AADowmOFIBM319.png
2466 ms
modal-banner.png
537 ms
close.png
928 ms
icon-wechat-fill.png
528 ms
6000.png
526 ms
17.png
526 ms
100.png
519 ms
app_code3.png
532 ms
gzh_code.png
529 ms
vip_bg.png
540 ms
location_icon_new.png
332 ms
app_code.png
348 ms
sprite_01.png
371 ms
icon-sprite.png
424 ms
footer.png
372 ms
iconfont.woff
221 ms
index.js
76 ms
hz-analytics.min.js
83 ms
push.js
909 ms
hm.js
1202 ms
push.js
1153 ms
opportunity.min.js
69 ms
global.min.js
78 ms
opportunity.min.css
64 ms
UrlChangeTracker.js
2907 ms
hm.gif
304 ms
hzins.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.
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
Form elements do not have associated labels
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
hzins.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
hzins.com SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hzins.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 Hzins.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.
hzins.com
Open Graph description is not detected on the main page of Hzins. 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: