31.5 sec in total
2.2 sec
27.7 sec
1.6 sec
Click here to check amazing 36 Kr content for China. Otherwise, check out these important facts you probably never knew about 36kr.com
36氪通过全面,独家的视角为用户深度剖析最前沿的资讯,致力于让一部分人先看到未来,内容涵盖快讯,科技,金融,投资,房产,汽车,互联网,股市,教育,生活,职场等,秉承着新商业媒体人的使命砥砺前行
Visit 36kr.comWe analyzed 36kr.com page load time and found that the first response time was 2.2 sec and then it took 29.3 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.
36kr.com performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.3 s
2/100
25%
Value13.2 s
2/100
10%
Value750 ms
39/100
30%
Value0.167
71/100
15%
Value10.2 s
25/100
10%
2247 ms
1001 ms
2756 ms
2798 ms
7617 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 10% of them (12 requests) were addressed to the original 36kr.com, 18% (21 requests) were made to Krplus-pic.b0.upaiyun.com and 17% (20 requests) were made to Krplus-cdn.b0.upaiyun.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Static.anquan.org.
Page size can be reduced by 875.7 kB (21%)
4.3 MB
3.4 MB
In fact, the total size of 36kr.com main page is 4.3 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. 65% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 125.5 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 125.5 kB or 79% of the original size.
Potential reduce by 155.7 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. 36 Kr images are well optimized though.
Potential reduce by 430.6 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 430.6 kB or 69% of the original size.
Potential reduce by 163.9 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. 36kr.com needs all CSS files to be minified and compressed as it can save up to 163.9 kB or 87% of the original size.
Number of requests can be reduced by 30 (31%)
97
67
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 36 Kr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
36kr.com
2247 ms
m.js
1001 ms
common-da87baa3158c2504da6832b0e6fa0395.css
2756 ms
app-1ea67b5c3567454d520c6628fa695863.css
2798 ms
RongIMLib-2.0.11.min.js
7617 ms
react_front-270bc9ebfe1442331c1b1126cf93bd60.js
2664 ms
vendor-bundle-7c6c3550e2e201a80c6765ab5960dd50.js
2862 ms
app-bundle-ca4ac4ef2b819ce1e1a76c4ead4fbd5b.js
2822 ms
style.css
1805 ms
script-statics.js
1780 ms
hm.js
931 ms
vds.js
4296 ms
footer.css
1232 ms
aq_auth.js
19754 ms
footer-statics.js
1121 ms
hm.gif
340 ms
pv
5622 ms
protobuf-min-2.7.js
3142 ms
stat.js
1365 ms
zhongchou.png
60 ms
getui.png
1236 ms
logo.png
54 ms
aly.png
54 ms
txyun.png
56 ms
qy.png
55 ms
yp.png
58 ms
upy.png
57 ms
qny.png
57 ms
dp.png
58 ms
sina.png
59 ms
umeng.png
99 ms
rongyun.png
99 ms
qr.png
102 ms
aliyunfooter.png
100 ms
auf3bjiuzybiy4yp.jpg
1231 ms
ewsiiy8hk3fkm8vo.jpg
1235 ms
dxj8nqvn9a0dn12p.jpg
1235 ms
s67u65mqapgck2cq.jpg
1235 ms
icomoon.woff
42 ms
getui.png
146 ms
auf3bjiuzybiy4yp.jpg
167 ms
ewsiiy8hk3fkm8vo.jpg
168 ms
dxj8nqvn9a0dn12p.jpg
255 ms
s67u65mqapgck2cq.jpg
171 ms
hm.gif
1848 ms
track
1069 ms
b3e59b2cd03d80cd.jpg
2419 ms
12402439_985904.jpg!feature
2203 ms
20150303114548c29b7.jpg!feature
857 ms
7B73.tmp.jpg!feature
2191 ms
QQ20160404-6.png!feature
1931 ms
005u1cvzlad7eyzo.jpg
541 ms
3a51dc7b-d702-463a-8dbc-19f24c8232d0.jpg!480
1973 ms
hm.gif
1456 ms
jcxm
865 ms
ecpm
981 ms
scsm
1565 ms
acrm
936 ms
current_user.json
581 ms
hot.json
943 ms
ycmm
957 ms
yczm
1607 ms
ocem
1171 ms
1169 ms
130807-arcade-fire-spike-jonze-her-scarlett-johansson-trailer-score.jpg!feature
321 ms
2.pic.jpg!feature
324 ms
xai-pain-solution-a-1.png!feature
322 ms
_____20160408154239.png!feature
324 ms
243094114618926717.jpg!feature
324 ms
21597873406_47e66891c3_c.jpg!feature
1423 ms
_____2016-04-07___11.55.38.png!feature
1705 ms
54800dd1.jpg!feature
1705 ms
_____20160408150258.png!feature
1666 ms
3.jpg!feature
1657 ms
20120820043103357.png
1973 ms
1399202532Xx29icma.jpg
1868 ms
sgf.jpg
1855 ms
243094114618926717.jpg
1877 ms
___.png!feature
1807 ms
SwiftTNW2.jpg!feature
1840 ms
vehicle_hacking.png!feature
1903 ms
34234.png!feature
1921 ms
mvknek66zvol3qeu.jpg
350 ms
logo_off_33189.jpg
51 ms
3d67cfa895a72a0f.png
59 ms
d39014cf825c6f7f.png
57 ms
cef5e20d6f364680b2f3f75ebb9143f7.jpg!480
49 ms
aa509772ac6b4ddeb0e26293a7046b9a.jpg!480
57 ms
igb75kzsmsq6bk91.jpg!480
56 ms
da44dfa0prfqs0yd.jpg!480
119 ms
track
1705 ms
hm.gif
1123 ms
track
1335 ms
__.PNG!feature
1617 ms
20151016125458691.jpg!feature
1682 ms
Screen-Shot-2016-04-05-at-10.03.06-PM-930x522.png!feature
1622 ms
1.jpg!feature
1630 ms
icomoon.woff
84 ms
fontawesome-webfont.a35720c2fed2c7f043bc7e4ffb45e073.woff
81 ms
icomoon.183325119960b168c812b691b6e3fcce.ttf
82 ms
slick.b7c9e1e479de3b53f1e4e30ebac2403a.woff
28 ms
top_swing_bg.93bddf9bc2db76bd7eb5795c9a64d2f5.jpg
134 ms
jcxm
3 ms
acrm
2 ms
36kr-165x120-x2-1.jpg
10 ms
07fc0b85573d4f09ac2e070f3892b581.jpg!480
24 ms
h_main_KM3O_0fa60001f029111a.jpg
1331 ms
47c1119fbc4f46ee8ea32f4624270391.jpg!480
20 ms
a7b858a7-1e6f-4289-a45b-c38ea6f16c30.jpg!480
573 ms
ycmm
2 ms
0f0005DvCARINhGuKT7t50.jpg
1 ms
gw_83x30.png
2575 ms
0f000Q1WFVb2VmUM3jw026.jpg
13 ms
0f0002sMjluUOhmmNXP8E0.jpg
1 ms
o.htm
340 ms
hm.gif
472 ms
track
504 ms
wh.js
800 ms
ac.js
554 ms
hm.gif
783 ms
36kr.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
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.
36kr.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
36kr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 36kr.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 36kr.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.
36kr.com
Open Graph description is not detected on the main page of 36 Kr. 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: