16.6 sec in total
2 sec
13.4 sec
1.1 sec
Click here to check amazing Keke 168 content for China. Otherwise, check out these important facts you probably never knew about keke168.com
优优漫画是非常棒的漫画网站,很多漫画都可以在优优漫画首页找到,并且提供优优漫画番acg漫画、工囗囗番漫画大全全彩优优等优优漫画,喜欢看漫画,请来优优漫画!
Visit keke168.comWe analyzed Keke168.com page load time and found that the first response time was 2 sec and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
keke168.com performance score
2008 ms
649 ms
1047 ms
2429 ms
2414 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 11% of them (9 requests) were addressed to the original Keke168.com, 73% (59 requests) were made to Img1.keke168.com and 15% (12 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source Img1.keke168.com.
Page size can be reduced by 214.7 kB (14%)
1.6 MB
1.3 MB
In fact, the total size of Keke168.com main page is 1.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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 64.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 64.3 kB or 83% of the original size.
Potential reduce by 3.3 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. Keke 168 images are well optimized though.
Potential reduce by 138.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 138.0 kB or 53% of the original size.
Potential reduce by 9.1 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. Keke168.com needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 71% of the original size.
Number of requests can be reduced by 16 (20%)
80
64
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keke 168. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
keke168.com
2008 ms
20140807.css
649 ms
logo.png
1047 ms
T1Kp5SXqNeXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2429 ms
T1ORKfXChcXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2414 ms
T1JVBzXwNdXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2399 ms
T1jJpBFiNaXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3944 ms
T1VkBvFglbXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2371 ms
T121BOFjldXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2761 ms
T19jBQXzBfXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3102 ms
T1GsZ1Xb4dXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
2809 ms
TB1ursJIpXXXXbZXVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3106 ms
TB1g_tGHVXXXXXgXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4074 ms
TB1gOVyHFXXXXc8XpXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3420 ms
TB1a5UFIXXXXXXCXFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3490 ms
TB1zuODFVXXXXcCXVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3456 ms
T1rU1.FzxaXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3489 ms
T1KuV2FBFXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3759 ms
T1303pFgxfXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3807 ms
T1JiOQXzBeXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3807 ms
T1XLEAFgBlXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3837 ms
T10k1MXEthXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4088 ms
TB1h6dnGXXXXXcrXVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4464 ms
TB1bEh1GVXXXXXYXpXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4451 ms
TB1JbOgGVXXXXXTXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4199 ms
TB1mcx9GVXXXXcCXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5890 ms
TB1kIepGVXXXXaFXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5643 ms
jquery.js
2068 ms
2014.js
1042 ms
tj.js
1037 ms
TB17CozHVXXXXaCXFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4416 ms
TB1J1JsIFXXXXaUXFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4540 ms
TB1LF0dHpXXXXXDXVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4764 ms
T18xkIFRBcXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5094 ms
TB1GbuQGXXXXXXtaXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4796 ms
T15CfLXcljXXX1Op37_063446.jpg_200x200.jpg
4889 ms
TB1Ye8KFVXXXXa_XXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5097 ms
TB1LZTHGXXXXXaEXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5465 ms
T1kx4.XsJgXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5549 ms
T1HWNPFgBbXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5459 ms
T1.hqJFDJfXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
5469 ms
TB1iNV5FVXXXXcjXpXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
6122 ms
common-s-b-f.png
329 ms
share.js
674 ms
jquery.js
1350 ms
my.js
337 ms
5448730.js
693 ms
TB1Xr91GXXXXXbcXpXXXXXXXXXX_!!2-item_pic.png_200x200.jpg
3821 ms
TB11snHFVXXXXXAXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3458 ms
TB1R6bGFVXXXXbzXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3503 ms
TB1EgjCFVXXXXa5XpXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4861 ms
TB17iy7HVXXXXbDXXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3423 ms
TB167uXHFXXXXcSaXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3737 ms
TB1pSyTGXXXXXbtXpXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3149 ms
TB1Tw1ZGFXXXXabXVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3376 ms
TB17zcjFXXXXXcQaVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3093 ms
T1daCpXlBCXXbIJoja_092507.jpg_200x200.jpg
3064 ms
share_api.js
226 ms
share_view.js
430 ms
select_api.js
877 ms
select_view.js
432 ms
image_api.js
434 ms
image_view.js
449 ms
T17dVqXx8bXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3092 ms
T1dGevFFBbXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3320 ms
tangram.js
925 ms
api_base.js
418 ms
TB12DK8IpXXXXX8XFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3087 ms
TB1i249IFXXXXbWXFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3048 ms
TB1sISTIpXXXXXuaXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
4285 ms
T1LijEFFxXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3449 ms
view_base.js
216 ms
TB16LrvFVXXXXbpaXXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3529 ms
T1QA1JFy4dXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3105 ms
T1x5dBFrJdXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3129 ms
T11IBJFS4dXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3316 ms
TB1C4nNGXXXXXX0XFXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3129 ms
T1m6R6XvpiXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
6966 ms
TB1.22wFVXXXXc2XVXXXXXXXXXX_!!0-item_pic.jpg_200x200.jpg
3813 ms
share_style0_16.css
225 ms
logger.js
229 ms
keke168.com SEO score
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keke168.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 Keke168.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.
keke168.com
Open Graph description is not detected on the main page of Keke 168. 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: