40.4 sec in total
7.4 sec
32.3 sec
738 ms
Visit jiandan.net now to see the best up-to-date Jiandan content and also check out these interesting facts you probably never knew about jiandan.net
煎蛋以译介方式传播网络新鲜资讯
Visit jiandan.netWe analyzed Jiandan.net page load time and found that the first response time was 7.4 sec and then it took 33 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.
jiandan.net performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value7.0 s
6/100
25%
Value8.8 s
16/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
7370 ms
6153 ms
3162 ms
2700 ms
2609 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jiandan.net, 10% (10 requests) were made to Ww1.sinaimg.cn and 9% (9 requests) were made to Ww4.sinaimg.cn. The less responsive or slowest element that took the longest time to load (13.6 sec) relates to the external source Tankr.net.
Page size can be reduced by 268.7 kB (5%)
6.0 MB
5.7 MB
In fact, the total size of Jiandan.net main page is 6.0 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. 85% 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 5.5 MB which makes up the majority of the site volume.
Potential reduce by 87.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. 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 87.1 kB or 80% of the original size.
Potential reduce by 9.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. Jiandan images are well optimized though.
Potential reduce by 156.8 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 156.8 kB or 45% of the original size.
Potential reduce by 15.0 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. Jiandan.net needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 79% of the original size.
Number of requests can be reduced by 32 (32%)
100
68
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jiandan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
jiandan.net
7370 ms
jandan.net
6153 ms
style.css
3162 ms
jquery-2.0.3.min.js
2700 ms
jquery.lazyload.min.js
2609 ms
common.js
3342 ms
adsbygoogle.js
100 ms
c.js
1014 ms
I89C.jpg
4208 ms
blank.png
4596 ms
88c184bcgw1f2po0ssubnj20f90b1mxs.jpg
59 ms
69d909a5jw1f2pncdcad2j20q414a7hq.jpg
316 ms
68f6e545jw1f2pmut2kbfg20dc07i4qq.gif
63 ms
68f6e545jw1f2pmdwhr2yg20dc07iqv6.gif
59 ms
68f6e545jw1f2pn53tu7dg20dc07i4qq.gif
56 ms
68f6e545jw1f2pm9c7nytg20dc07ikjp.gif
56 ms
69d909a5jw1f2pmsbd390j20j60qyjzc.jpg
312 ms
005CLsEmjw1f2p28im5pwj30k00zjk6y.jpg
68 ms
97f224aajw1f2ofo14za7j20c84h94qp.jpg
348 ms
cd7861dcjw1erarduqk0dj20go0fn76a.jpg
156 ms
4bf31e43jw1f2i0cmlqcqj20go0p0gou.jpg
319 ms
4bf31e43jw1f2i0cm19zdj20n50ycq5e.jpg
91 ms
cd7861dcjw1etti8lq4q1j20hd097wff.jpg
57 ms
8841dbe3gw1ezhm98xlsgj219y6un4qp.jpg
380 ms
a69337f3jw1f2p46ll59sg207w04ob2g.gif
310 ms
622df3e2gw1f2p28c7d97j20fa0emt9j.jpg
64 ms
8841dbe3gw1f2p42qnvn4j216i6hd4qp.jpg
308 ms
4bf31e43jw1f2i0cn7vdrj20kr0v9dj5.jpg
154 ms
68f6e545jw1f2pmj1zcwug20dc07iqv8.gif
56 ms
6d9d69bajw1f2pii1sdgoj20hs0dat9l.jpg
60 ms
67175fe4gw1f2p7lvm6r3j20f00jzjuq.jpg
95 ms
4bf31e43jw1f2i0co6knpj20hl0qeacw.jpg
84 ms
cd7861dcjw1ehm6vtirtcj20dw0ijabm.jpg
56 ms
4bf31e43jw1f2i0cotpv7j20dw0j0wgk.jpg
64 ms
J02U.jpg
13577 ms
6NLL.jpg
2130 ms
W88B.jpg
2738 ms
68f6e545jw1f2pmouc4gdg20dc07ib2c.gif
51 ms
68f6e545jw1f2pn3ri8leg20dc07i1kz.gif
59 ms
69d909a5jw1f2pm92k7snj20gj0ne42y.jpg
313 ms
d54a1fa7jw1f2pkkd6xftg209s0684qr.gif
304 ms
69d909a5jw1f2pm4p3w8qj20jg1lrk6v.jpg
85 ms
622df3e2gw1f2p28t7ozdj21411hc45g.jpg
82 ms
622df3e2gw1f2p28bhsvxj20fa084q31.jpg
85 ms
a93f80dfjw1f2onf7b9fij20dc0dcab7.jpg
312 ms
4bf31e43jw1f2i0cq0hcuj20b40jswga.jpg
181 ms
logo-2014.gif
581 ms
body.gif
582 ms
chart.png
4644 ms
ca-pub-5673546663729848.js
196 ms
zrt_lookup.html
232 ms
show_ads_impl.js
118 ms
ucfm
1649 ms
1.jpg
4955 ms
5.jpg
4499 ms
04.png
5504 ms
ads
190 ms
ucfm
954 ms
osd.js
28 ms
ads
224 ms
analytics.js
21 ms
hm.js
672 ms
HYM6.jpg
1838 ms
71JY.jpg
5391 ms
collect
16 ms
collect
107 ms
10180670430636607704
48 ms
abg.js
50 ms
m_js_controller.js
62 ms
googlelogo_color_112x36dp.png
32 ms
s
44 ms
x_button_blue2.png
43 ms
5133665603143942263
11 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
7 ms
hm.gif
345 ms
ucfm
987 ms
adx.php
702 ms
cpro_media_small.png
876 ms
0f000DH69chonfBPLq-J86.jpg
790 ms
time.js
482 ms
lawDes.min.js
533 ms
ucfm
536 ms
sync.htm
507 ms
adPic.new.20150909.min.js
86 ms
bot-patch.min.js
93 ms
click.min.js
93 ms
pixel
58 ms
rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png
1141 ms
56fe2563N7aab6a6a.jpg
203 ms
adx.php
381 ms
gpixel
677 ms
sync_pos.htm
429 ms
sync2r.htm
858 ms
55e40d3fN2a01189f.png
61 ms
closefeedback.min.js
533 ms
closeBtn_oper.png
2038 ms
bd_logo.png
501 ms
promotionLeftBottom.png
978 ms
bg_rb.png
504 ms
o.htm
877 ms
ui
39 ms
hm.gif
722 ms
wh.js
741 ms
ac.js
537 ms
fp.htm
611 ms
jiandan.net accessibility score
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.
jiandan.net 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
jiandan.net 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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jiandan.net 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 Jiandan.net 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.
jiandan.net
Open Graph description is not detected on the main page of Jiandan. 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: