60.7 sec in total
1.6 sec
55.8 sec
3.3 sec
Visit leikeji.com now to see the best up-to-date Leikeji content for China and also check out these interesting facts you probably never knew about leikeji.com
关注科技价值。前沿和深度的科技评论,人人可参与的产品分享交流平台
Visit leikeji.comWe analyzed Leikeji.com page load time and found that the first response time was 1.6 sec and then it took 59.1 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. Unfortunately, there were 11 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
leikeji.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.2 s
0/100
25%
Value16.3 s
0/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value16.6 s
5/100
10%
1571 ms
225 ms
477 ms
481 ms
477 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Leikeji.com, 70% (46 requests) were made to Img.leikeji.com and 3% (2 requests) were made to Img.wanshar.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Img.leikeji.com.
Page size can be reduced by 183.5 kB (39%)
464.7 kB
281.3 kB
In fact, the total size of Leikeji.com main page is 464.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 247.9 kB which makes up the majority of the site volume.
Potential reduce by 8.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 8.3 kB or 70% of the original size.
Potential reduce by 14.0 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. Leikeji images are well optimized though.
Potential reduce by 127.0 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 127.0 kB or 79% of the original size.
Potential reduce by 34.2 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. Leikeji.com needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 78% of the original size.
Number of requests can be reduced by 21 (40%)
52
31
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leikeji. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.leikeji.com
1571 ms
lkj_common.css
225 ms
iconfont.css
477 ms
swiper.min.css
481 ms
index.css
477 ms
article_list.css
485 ms
default.jpg
18010 ms
7f8eee2966f24616b71c57d24c0b35da.jpg
6117 ms
jquery.js
19514 ms
subscribe.js
1052 ms
lkj_common.min.js
8570 ms
z_stat.php
2321 ms
swiper.jquery.min.js
1220 ms
lazyload.min.js
1065 ms
jquery.nicescroll.js
1826 ms
index.js
1087 ms
0f9fd5b87eae491da7cb62edadbf5928.jpg
7423 ms
50174594dfba45689d220cf5cfebc64a.jpg
6098 ms
3e2f3568584a4860be1816b8de2f1cf5.jpg
6160 ms
logo_mobile.png
6823 ms
aliyun-logo.png
7774 ms
myweixin.jpg
11254 ms
logo_mobile.png
8822 ms
1458271033674.png
11260 ms
5602ad9eedda421f861cd078758eaf7f.jpg@0-64-1000-600a
19954 ms
b02a392606bb495f8a2d31781ab7193c.png@0-60-1200-720a
19946 ms
8466b0536bb14497b72e3930247dcf3e.jpg@0-92-3551-2131a
19943 ms
b381525da2504e559c7b034978a00b97.jpg
13009 ms
9cb5dcc7755747e8af15b061dd6b7814.gif
19942 ms
e5d2c58bb2b24bddb9e1f3f3ee23ee11.jpg
15013 ms
9b401042962b4983b864844a4e02befc.jpg
19942 ms
cac208944bd44b59a4b05168052bc316.jpg@89-19-424-424a%7C1e_339w_339h_1c_0i_1o_100q_1x.jpg
19940 ms
807460c9244141eebc39f6e79b78b160.jpg@82-0-478-478a%7C1e_339w_339h_1c_0i_1o_100q_1x.jpg
19931 ms
50eedf199f3044b0a6e73a85837e31c2.jpg@0-0-600-600a%7C1e_339w_339h_1c_0i_1o_100q_1x.jpg
19927 ms
iconfont.woff
299 ms
stat.htm
227 ms
core.php
632 ms
3e04f0b1fdef4126a9c1aef131d1b7df.jpg@112w_112h_1e_1c
1927 ms
acda75da14754e798ec0675f491cd5d8.jpg@113w_112h_1e_1c
1328 ms
1020ca9d368d4ae4bc5d0832444daf6c.jpg@112w_112h_1e_1c
4842 ms
6338d0af63404979aa388e78cce79631.jpg@113w_112h_1e_1c
1370 ms
05510392c717434093de09a174ed4f95.jpg@112w_112h_1e_1c
1365 ms
b8c65635a414493e9d27e8abca80608c.jpg@113w_112h_1e_1c
2763 ms
0a1aaf3b4a5e483e8a5b8c3e4a2c9698.jpg@112w_112h_1e_1c
1733 ms
645fb2e654ad47c7838d794b41027b5f.jpg@113w_112h_1e_1c
3485 ms
fe818e9ee57f49ac818e6ed9ce30df14.jpg@112w_112h_1e_1c
2157 ms
c3ea87f6561b440fb41a019a4043c6a5.jpg@112w_112h_1e_1c
2156 ms
25ca44c059dd46d4884b5170a5f7ee40.jpg@113w_112h_1e_1c
4442 ms
bf8a6e2907b54574a37ef21479d22f2e.jpg@112w_112h_1e_1c
4187 ms
15c86a55f9e74204bea5932a0978d1e7.jpg@113w_112h_1e_1c
5006 ms
c202c623e9a14c9f9f7a452a0ce2b353.jpg@112w_112h_1e_1c
5079 ms
88fad984d8934b93abb055d5c9133d91.jpg@113w_112h_1e_1c
4465 ms
766225a0474a4511aa9e1c29a0dd835c.jpg@112w_112h_1e_1c
4874 ms
2af751a8be5f467a9bb0647755bbf71a.jpg@112w_112h_1e_1c
5078 ms
6b841563740b4b89873d9b1495182bf2.jpg@113w_112h_1e_1c
7507 ms
b0cd7c9787ab4ed1a6be3a5598d8759b.jpg@112w_112h_1e_1c
7318 ms
acf85b1003dc4a748179b98605e28e7b.jpg@113w_112h_1e_1c
5349 ms
ad86664f87e1449997bca72ce7aef166.jpg@112w_112h_1e_1c
7507 ms
5fa88068e2ff475cac724a9de458d638.jpg@113w_112h_1e_1c
5839 ms
45bb1486a5054b8a918a2d1d684eb7af.jpg@112w_112h_1e_1c
7485 ms
76839d9d2cac4270b4a84451739e27c6.jpg@113w_112h_1e_1c
7293 ms
576e8a2ae5894596ab9dc1466cf4f57f.jpg@77-62-1579-948a%7Cbanner2_729w_438h_1e_1c
15415 ms
fcd15ea4e9684283858e965f3b4b5df6.jpg@0-11-940-564a%7Cbanner2_729w_438h_1e_1c
16861 ms
7566b6a6764943d9b2bbce9ff2109deb.jpg@316-0-1603-962a%7Cbanner2_729w_438h_1e_1c
11392 ms
6918aa09247445fe89f01656b4f94dff.png@118-0-1795-1078a
19635 ms
b02a392606bb495f8a2d31781ab7193c.png@0-60-1200-720a
19635 ms
leikeji.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
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.
leikeji.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
Browser errors were logged to the console
Page has valid source maps
leikeji.com 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 Leikeji.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 Leikeji.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.
leikeji.com
Open Graph description is not detected on the main page of Leikeji. 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: