12.9 sec in total
925 ms
11 sec
896 ms
Welcome to archnature.diandian.com homepage info - get ready to check Archnature Diandian best content for China right away, or after learning these important things about archnature.diandian.com
点点数据,专业移动应用/游戏App数据查询分析平台,为您提供App市场份额分析(App下载/收入数据)、用户行为分析(App活跃、App留存、使用次数、使用时长、用户画像)等App数据分析统计。
Visit archnature.diandian.comWe analyzed Archnature.diandian.com page load time and found that the first response time was 925 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
archnature.diandian.com performance score
name
value
score
weighting
Value28.6 s
0/100
10%
Value32.3 s
0/100
25%
Value38.0 s
0/100
10%
Value2,250 ms
6/100
30%
Value0.009
100/100
15%
Value39.9 s
0/100
10%
925 ms
1475 ms
2455 ms
1403 ms
1182 ms
Our browser made a total of 214 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Archnature.diandian.com, 94% (202 requests) were made to Static.diandian.com and 3% (6 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Mapapi.qq.com.
Page size can be reduced by 522.2 kB (8%)
6.6 MB
6.1 MB
In fact, the total size of Archnature.diandian.com main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 338.8 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 338.8 kB or 70% of the original size.
Potential reduce by 160.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. Archnature Diandian images are well optimized though.
Potential reduce by 20.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Archnature.diandian.com has all CSS files already compressed.
Number of requests can be reduced by 164 (78%)
211
47
The browser has sent 211 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Archnature Diandian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 130 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
archnature.diandian.com
925 ms
www.diandian.com
1475 ms
gljs
2455 ms
iconfont.js
1403 ms
hm.js
1182 ms
hm.js
1232 ms
hm.js
1251 ms
styles~c5d2e459.5ca470a.css
1550 ms
styles~fb846e85.b2cf5e8.css
1687 ms
styles~91fbae5b.2d71123.css
1819 ms
styles~14622ba3.51d75e1.css
1806 ms
styles~52cf9c39.363d29f.css
1839 ms
styles~9ecb6240.885590b.css
1811 ms
styles~f5fef697.c3af736.css
1832 ms
styles~3be59c22.e73923f.css
1820 ms
styles~48c9fa38.8db7ee4.css
1954 ms
styles~a6ba5ee4.eff2082.css
1945 ms
styles~36598121.6b00507.css
1980 ms
styles~69846425.33a38cd.css
1956 ms
styles~42f9f7b1.a916504.css
1988 ms
styles~72517e41.a3e3896.css
1986 ms
styles~008a4c30.04c229b.css
2106 ms
styles~c76bb667.67ebe44.css
2089 ms
styles~d2284656.698c9b2.css
2107 ms
styles~819a6d22.6ffa8b4.css
2116 ms
styles~c39c3bba.2dc575c.css
2134 ms
styles~14a91b62.e179f2e.css
2140 ms
styles~75bb53e9.e16cb29.css
2228 ms
styles~1db99591.a79bb53.css
2247 ms
styles~01a121c5.5ccb285.css
2247 ms
styles~b53b1976.1c9e1a1.css
2278 ms
styles~14c32445.f264e53.css
2268 ms
styles~6a96436d.2db092f.css
2274 ms
styles~0137905b.35ff7e3.css
2391 ms
styles~00801bd5.974d147.css
2385 ms
styles~2a8e0bc3.471f9c8.css
2382 ms
styles~6b71a9ce.7b8b9b8.css
2435 ms
styles~8ab540b9.5389632.css
2423 ms
styles~bb980c89.3b82f67.css
2426 ms
styles~0d724057.363e3ff.css
3034 ms
styles~f897f74a.36811fd.css
3035 ms
styles~f28e52ee.fc517f4.css
3038 ms
dot.min.js
809 ms
app~0e8cffab.6431f92.css
1647 ms
runtime.d1be635.js
1496 ms
app~56cd9b39.fc46195.js
1360 ms
app~f1e4bfbc.3598a6c.js
1288 ms
app~ee3c9e66.5fa3e9e.js
1237 ms
app~3c559963.63f5ce3.js
1274 ms
app~eb499fd9.cfba35b.js
1274 ms
styles~c5d2e459.d751a3c.js
1217 ms
styles~fb846e85.d34e354.js
1254 ms
styles~91fbae5b.0138be9.js
1151 ms
styles~14622ba3.76652be.js
1142 ms
styles~52cf9c39.83c677d.js
1140 ms
styles~9ecb6240.d5bcf07.js
1118 ms
styles~f5fef697.9e2bcb9.js
1111 ms
styles~3be59c22.23a4666.js
1112 ms
styles~48c9fa38.cbe2766.js
1163 ms
styles~a6ba5ee4.b07fabc.js
1147 ms
styles~36598121.71b5086.js
1148 ms
styles~69846425.1e6ba43.js
1141 ms
styles~42f9f7b1.1522076.js
1124 ms
styles~72517e41.2dbba37.js
1119 ms
styles~008a4c30.1930b12.js
1030 ms
styles~c76bb667.fb8cf1f.js
1012 ms
styles~d2284656.24a548e.js
1013 ms
styles~819a6d22.7694a1e.js
1005 ms
styles~c39c3bba.eed484c.js
1047 ms
styles~14a91b62.aeac0a4.js
1047 ms
styles~75bb53e9.9cc1cad.js
965 ms
styles~1db99591.d08d6b6.js
962 ms
styles~01a121c5.5b18902.js
991 ms
styles~b53b1976.c96e7eb.js
1003 ms
styles~14c32445.6745050.js
1036 ms
styles~6a96436d.202a461.js
1033 ms
glyphAtla_202312281749_tiny.png
5973 ms
hm.gif
335 ms
server-qrcode.jpg
780 ms
hm.gif
327 ms
hm.gif
312 ms
styles~0137905b.f0ccad8.js
468 ms
styles~00801bd5.9e65c34.js
575 ms
styles~2a8e0bc3.394937e.js
475 ms
styles~6b71a9ce.e264495.js
530 ms
styles~8ab540b9.23453fc.js
576 ms
styles~bb980c89.9439766.js
579 ms
styles~0d724057.65491ef.js
562 ms
styles~f897f74a.183d99b.js
586 ms
styles~f28e52ee.a581335.js
624 ms
styles~b7594acd.3e07e30.js
665 ms
styles~f0c157be.85df63d.js
663 ms
styles~54fd0efc.8ff731a.js
666 ms
app~c6a4351b.7d96383.js
739 ms
app~b8f15f88.8595b1e.js
717 ms
app~bdc0199f.824657c.js
790 ms
app~92a68681.4ad4bce.js
849 ms
app~91cb7bc0.9ee5400.js
827 ms
app~cc0cc3d3.8b3d487.js
645 ms
app~15d33a99.1f38349.js
702 ms
app~34b97e85.4bd8b3a.js
718 ms
app~41f1a709.1f130b0.js
789 ms
app~5a88e3e8.e5d32cb.js
785 ms
app~fd209581.a85cdc2.js
815 ms
app~b0d8f46b.3efb612.js
860 ms
app~e982b20a.a61f73c.js
841 ms
app~27079c19.90dda0f.js
878 ms
app~24126af6.e4b20a8.js
932 ms
app~e40b4dc3.6d0b06d.js
921 ms
app~d93aa8c8.0888bbf.js
895 ms
app~db132b0b.0eb702e.js
920 ms
app~bf90d74d.846ad9d.js
906 ms
app~8abcadc8.216f85f.js
959 ms
app~069343bd.27151de.js
990 ms
app~bb1496dd.4bb4dae.js
924 ms
app~4b919bc2.4cd48ef.js
895 ms
app~45b06346.662da10.js
944 ms
app~ba0e92bf.73ebaba.js
889 ms
app~3564966e.43efa3b.js
941 ms
app~c38022b1.cffb6fc.js
935 ms
app~5c976143.ece70f0.js
882 ms
app~af4b9471.6a15c92.js
1102 ms
app~a80bee26.8d0a228.js
952 ms
app~638f3d36.0813756.js
910 ms
app~e17e0f23.9429bd3.js
934 ms
app~f0b5dbfc.e38a2e3.js
952 ms
app~8a467fc5.50196e7.js
902 ms
app~c805a17b.ee7a093.js
942 ms
app~226d385e.0359258.js
965 ms
app~9e40b436.2e7c0b2.js
947 ms
app~50d79142.37a68b0.js
980 ms
app~e7fc8277.91383cd.js
938 ms
app~17e7aa17.5009b19.js
940 ms
app~d72ff866.806684f.js
947 ms
app~05d0f8ed.b087b90.js
938 ms
app~15e12bfa.a7aaf32.js
997 ms
app~8c459288.6409c7d.js
991 ms
app~ede79487.ef794ed.js
932 ms
app~45e9aba3.9c66a65.js
963 ms
app~b8c847fb.fec64bc.js
945 ms
app~160f74f1.d3e2d0e.js
946 ms
app~c5d2e459.74725b7.js
983 ms
app~c75bc589.3d9086d.js
1151 ms
app~d5a19290.36bc7f6.js
939 ms
app~948af00a.1f22f83.js
967 ms
app~580b9291.e825d95.js
939 ms
app~4f7dd3be.354f978.js
971 ms
app~201a7b59.af5c3df.js
1003 ms
app~ee3c9e66.f3537fb.js
1094 ms
app~239b99e8.0954da6.js
945 ms
app~891937d3.12e7c47.js
972 ms
app~96452f0f.23f01b8.js
990 ms
app~e9a6cccc.f78c15f.js
1006 ms
app~08ba177c.fc4ce3b.js
1013 ms
app~b7c0cf6a.79ff412.js
975 ms
app~5bfa4b2a.8ea5b14.js
976 ms
app~8450c0f1.af9ab8b.js
1025 ms
app~e650ef72.39ae32f.js
993 ms
app~9c12c067.0642522.js
993 ms
app~0797f67f.9dcb073.js
969 ms
app~c62ed42f.19a8367.js
913 ms
app~f69643ec.0973143.js
954 ms
app~01e7b97c.653e4e2.js
1002 ms
app~06e40da7.fadf00b.js
999 ms
app~6e6d8645.0c84964.js
983 ms
app~ba25ee43.317a1f8.js
948 ms
app~0e8cffab.f400949.js
899 ms
app~748942c6.6b56e3b.js
943 ms
app~f9738bfe.9010a2e.js
1010 ms
app~9a607d2d.58f50cb.js
985 ms
app~92c3d631.150057f.js
998 ms
thinkingdata.umd.min.js
900 ms
pdf.worker.js
1212 ms
iconfont.d517a1f.woff
955 ms
logo.03bd5b7.png
984 ms
AS.157d1dd.png
986 ms
GP.2cf443b.png
946 ms
android.559d0c8.png
917 ms
tap.04a7949.png
938 ms
ps5.cedd3ed.png
989 ms
xbox.c494a21.png
979 ms
Switch.7c89f45.png
951 ms
Steam.31d9f40.png
907 ms
index-app-1.6d09b15.png
1158 ms
index-app-2.2e6a101.png
1152 ms
index-app-3.021646d.png
1118 ms
index-explore-1.b48db67.png
1134 ms
no-data.92347d2.png
1048 ms
index-card-1.ea07003.png
1048 ms
index-card-2.d1cde1f.png
1022 ms
index-card-3.6228690.png
1016 ms
index-card-4.d3d5d6f.png
976 ms
index-card-5.89b61c6.png
967 ms
index-card-6.6918be4.png
899 ms
index-card-7.df3f7b8.png
930 ms
index-card-8.d0dd09b.png
997 ms
wechat.ab8e932.png
990 ms
shangwu-qrcode.7c23ea2.png
979 ms
footer-hover-2.b2e5b87.png
935 ms
qun.5063994.png
976 ms
footer-1.de7c5c4.png
936 ms
footer-2.5e68d22.png
1007 ms
footer-3.1ad9430.png
988 ms
footer-4.7fec95e.png
973 ms
beian.d0289dc.png
924 ms
apple.2d77b11.png
923 ms
common-1.01228f2.png
1014 ms
common-2.146cfdf.png
1110 ms
common-3.f7ceb03.png
1081 ms
common-4.13e1c20.png
906 ms
common-5.5aeebea.png
1695 ms
hover.dafd4b6.png
966 ms
default.6a9ae80.png
1018 ms
index-app-list.dbc07d6.png
1142 ms
archnature.diandian.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
Image elements do not have [alt] attributes
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.
archnature.diandian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
archnature.diandian.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
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Archnature.diandian.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Archnature.diandian.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.
archnature.diandian.com
Open Graph description is not detected on the main page of Archnature Diandian. 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: