14.4 sec in total
699 ms
11.4 sec
2.3 sec
Visit ssqian.com.cn now to see the best up-to-date Ssqian content and also check out these interesting facts you probably never knew about ssqian.com.cn
上上签电子签约云平台,为企业提供电子合同全生命周期智能管理服务,帮助企业实现降本增效,全领域电子签约解决方案,随时随地完成电子合同的实时签署与线上智能管理,确保其安全、合法合规、不可篡改,终身服务有保障。
Visit ssqian.com.cnWe analyzed Ssqian.com.cn page load time and found that the first response time was 699 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ssqian.com.cn performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value10.4 s
0/100
25%
Value22.4 s
0/100
10%
Value2,250 ms
6/100
30%
Value0
100/100
15%
Value29.6 s
0/100
10%
699 ms
785 ms
991 ms
1336 ms
514 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Ssqian.com.cn, 47% (64 requests) were made to Static.bestsign.cn and 23% (31 requests) were made to Bestsign.cn. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Static.bestsign.cn.
Page size can be reduced by 1.0 MB (13%)
8.1 MB
7.1 MB
In fact, the total size of Ssqian.com.cn main page is 8.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. 70% of websites need less resources to load. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 947.3 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 947.3 kB or 66% of the original size.
Potential reduce by 61.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. Ssqian images are well optimized though.
Potential reduce by 980 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 26 (22%)
120
94
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ssqian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
ssqian.com.cn
699 ms
ssqian.com.cn
785 ms
www.ssqian.com.cn
991 ms
www.bestsign.cn
1336 ms
0521768b14de82ff40a3.css
514 ms
899bbf6703a84ab4cbe7.css
819 ms
5bb32081bcc1a3eb8c35.css
738 ms
js
57 ms
awsc.js
166 ms
defb17cb9458ce8aa802.js
797 ms
770dd3b6919e2a89f33e.js
1013 ms
d6a830f038585c74dd46.js
1187 ms
deb7a612aba79b9d93b1.js
1988 ms
5aa377029b917730a742.js
2156 ms
utracking.js
320 ms
hm.js
1189 ms
et_n.js
184 ms
gdtevent.min.js
2354 ms
104b1cf90757066eefd9a297e5cd8238553776c7.jpg
1481 ms
92bc144d1f1b58268689dbb36aa0a6340bb92a72.jpg
1474 ms
b5e593b2f968f81147171357126c01a14ad88bd4.jpg
1529 ms
ee99a49853357b416eb69ac1562e60195b63e0c6.jpg
1474 ms
daa5574d65d4e204c42071d8088f472725c4d6f5.jpg
1584 ms
824f71d275147e2dd81f5a3555e975329182c8cc.png
1473 ms
db0f793d267a7d749d83d383a97b4f9d44e432e2.jpg
2099 ms
48f5ea5126a3ec77ec660f512b546d3c5077d0ad.png
1668 ms
7f46b2d59210eba96799381af74e7c765f1adf6a.jpg
2127 ms
47470c7142301e6149a6e1c3892c3a7602c534c4.png
1638 ms
963e862d125634f6109834bb4718c52b499f9075.jpg
2126 ms
7f387476d11aabfa3290cf74e4c6f39615c0835.png
2098 ms
535a5a90fe25f873e1d61ac1c12dd68925a3c60e.jpg
2339 ms
57b17dcfb3ef15288fa68d6194c83be33874faf7.png
2126 ms
46767e607ccee6421728da99c7fd22c52865b001.jpg
2261 ms
eebd9860200bcdbc76cb901600c4a1e0b96ed0b.png
2126 ms
1043e338bed10a5b2d8f7ad3811d2439cf59f2fe.jpg
2383 ms
31972d4162c7114827d729badb966d0944d7b9a3.png
2380 ms
fc12bd1c0d608ecbce76fb6df14d101213fb9151.jpg
2524 ms
50188cedf4dfc0a54c3947b2835245b5d5de7368.png
2368 ms
fd2fed52b1558cc05c81d332eaf03fea075807dc.jpg
2533 ms
7635ee94f2d4b101867d8ac5a2bcd4fdc6a5d61f.png
2590 ms
939037739ad50692292a4ba0ddcb81131fa3a196.jpg
2871 ms
59769187c6217fadc2a947646bd75565fc770297.jpg
2635 ms
222ec9c99f788543e2d54ea9c1af4074ade11c94.jpg
2659 ms
b8b856b1a83f6723917058afd86ffde9df7ce7ed.jpg
2703 ms
1be61fa50c82911ef33418f342bc6c2269da9f74.jpg
2866 ms
b61591c4464a0e0317ec6c53315df505a1829430.jpg
3249 ms
8e8b79217e94b995ba297478a7e4dd43c40c150b.jpg
2948 ms
edb18ae.svg
243 ms
38db2a1.gif
1592 ms
1dd2729.jpg
737 ms
d132af5.jpg
1503 ms
435733.js
1297 ms
fcagl.js
1918 ms
5149370.woff
796 ms
535877f.woff
775 ms
hm.gif
324 ms
7ebcf5fcb8fbeb436021.js
249 ms
s.gif
871 ms
mediav1130.html
1613 ms
proxy.html
1114 ms
hm.gif
417 ms
sa.gif
1085 ms
b51707f09247f4558eb7.js
543 ms
getCore
391 ms
getStability
364 ms
getCarbonNeutrality
353 ms
getJudicialCases
341 ms
list
843 ms
getFriendLink
323 ms
right-ad
510 ms
getHeadBanner
483 ms
getTextBanner
471 ms
list
850 ms
getContractShot
478 ms
contentShotCategory
468 ms
s.gif
754 ms
stdlog
1110 ms
config
523 ms
pixel
522 ms
top-ad
316 ms
navigation-bar
244 ms
2a8658faa5bf4f824d6f204f769bdd424b6c6fe0.jpg
406 ms
f420771a52bce5cd5b33c80a0591bb1ad781f3e5.jpg
430 ms
9d1bd111c6862016dc26fa000b4311986b29a552.jpg
534 ms
fb80549b7295a64f753affb360f40b2cb48f730c.jpg
578 ms
local.info.g9hc4.cn
222 ms
6732e14a4e201284e37b7a49280b3a785f6a6b31.gif
941 ms
local.info.g9hc4.cn
34 ms
29a7a72fe464d86dd4ace1cfc9881f5dde74bc99.jpg
430 ms
f4094d62ef6b99ff8441858062cc9b251b966be4.png
455 ms
538678f2560d4940d0916192c2680870a85f4aa8.jpg
556 ms
dd307a1c9d255ff174b83e2c13dc1162d2d04eff.png
601 ms
b5055dc8ef890967533c4bf3f446b1479395996d.jpg
846 ms
9b0cf825e26de81f5ba329327ba6c60a7cd2229b.png
702 ms
5260e0c798fe02e849f59274f35dfbd410479c38.jpg
748 ms
27ef552a523f30a00b41bc547ef3d1b604491590.png
832 ms
411f2aa423109be0f2a8e1bc9e138da9a8a7bb81.jpg
892 ms
e7479548c8064cf87e7f97ffb1c207d6bbda16fc.png
980 ms
72e6ad7f47b574cd284ea3e6794184cc1815b57e.jpg
1019 ms
37b2747e9ccacde3a6f000c183ffbd013b4999.png
1131 ms
91b0238ffcda855c45b0ce3986297299ab19bb61.jpg
1145 ms
1a2164eb2a4f4ba4e3ff2792ee67f5e4e4a46523.png
1113 ms
5bc33479c3b9cc130ba39ce30740f7a628c028a2.jpg
1192 ms
870b671aaadbf600d347b0915b735e93ee9f0d69.png
1264 ms
b24c49ab5b59a17b7ffb301e5190a0b07edc847c.jpg
1307 ms
99cb81503e794a5a8c95317b8a0ac29b1f0f86e4.png
1348 ms
2d940e8390bcdb053a71003b56153678092d2a8d.jpg
1431 ms
8a9e1003127d2dfa9066347b22945a22c55ed6fc.png
1406 ms
ededfde364cfce245ba0984cd5889532b28246dd.jpg
1475 ms
1dcb030f0acc19311a476d966bbd52cde9ab96fc.png
1567 ms
8cb2592cf74ff568713dbfe2698989f78932ef83.jpg
1586 ms
82ff4e890146d0a59529f0b74c502069db8b7036.png
1598 ms
f4468ede2f69dc982850af16e7190b656b05b02b.png
1595 ms
493cb4d03ef3e5f7b5ee0e19a1ae79065d1def8b.png
1643 ms
becb45428e8d620f01de7af8e782e079d874a6cf.png
1676 ms
8ab5a820edb6b72d619fbb1d41e86a39e839deb4.png
1780 ms
829b0c4eb6ad4781f73e1654aa8faeea591c0e53.png
1783 ms
87c8290c57aa7bd5ea864ffa2902503493d40cd5.png
1758 ms
b
963 ms
pixel
39 ms
t.gif
1080 ms
ckmap.htm
954 ms
cm.gif
1243 ms
max.dmp.360.cn
1172 ms
pixel
20 ms
m
192 ms
m
186 ms
m
366 ms
m
432 ms
m
526 ms
m
509 ms
track
956 ms
s.gif
240 ms
gtm.js
47 ms
getseal
276 ms
us.norton.com
33 ms
ssqian.com.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
ssqian.com.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ssqian.com.cn 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 uses 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 Ssqian.com.cn 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 Ssqian.com.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.
ssqian.com.cn
Open Graph description is not detected on the main page of Ssqian. 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: