2.8 sec in total
18 ms
2.1 sec
668 ms
Visit keep.com now to see the best up-to-date Keep content for China and also check out these interesting facts you probably never knew about keep.com
「Keep」是一款健身App,超过2亿运动爱好者的选择!无论是想减肥塑形或增肌,还是寻找健身跑步瑜伽计步等训练计划,你可以随时随地选择课程进行训练!权威教练视频教学,健身干货自由分享。在这里健身打卡,结识志同道合的运动好友,让运动不再是孤单的坚持!
Visit keep.comWe analyzed Keep.com page load time and found that the first response time was 18 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
keep.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.5 s
4/100
25%
Value7.8 s
24/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value29.9 s
0/100
10%
18 ms
939 ms
78 ms
68 ms
142 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Keep.com, 75% (84 requests) were made to Res.cloudinary.com and 9% (10 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (939 ms) belongs to the original domain Keep.com.
Page size can be reduced by 660.2 kB (13%)
4.9 MB
4.2 MB
In fact, the total size of Keep.com main page is 4.9 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. 60% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 123.6 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 123.6 kB or 86% of the original size.
Potential reduce by 149.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. Keep images are well optimized though.
Potential reduce by 193.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 193.8 kB or 64% of the original size.
Potential reduce by 193.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. Keep.com needs all CSS files to be minified and compressed as it can save up to 193.1 kB or 81% of the original size.
Number of requests can be reduced by 36 (34%)
106
70
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keep. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
keep.com
18 ms
keep.com
939 ms
all.8240beae.css
78 ms
jquery.min.01855ad3.js
68 ms
bundle.270d6f42.js
142 ms
b84e0ed616bd20ccf1704d7e23971006.png
289 ms
cce74cf37be31f4dce9013e92072c2b6.jpg
460 ms
1c3622499757491b988b235a06b03a67.jpg
334 ms
e88fb3fdad174e0da4338365f66f6150.jpg
390 ms
76857e59844fdce05df2ee29958a4b1f.jpg
352 ms
ddf206814302c1a72b7ea1b27e5e38bf.jpg
430 ms
2b00eed09aa674f22e5db7cd16151920.jpg
333 ms
18a78cfaea2ee996c6ae7f183db0524b.jpg
474 ms
e5e9058679259a1e21adadb09b30ef9e.jpg
477 ms
95568bb5b3a4bd54098640c6a57b1bff.jpg
500 ms
3aa43f32be3e817717683d03c69d391e.png
437 ms
255be1662c931b25cca0cb21b9e006b1.jpg
477 ms
e4bbfe7e78d9314f23ab987068b88610.jpg
475 ms
fde7ee55f0c0ef3f7a53e7738557e954.jpg
473 ms
3bb28e63ecc76fbd48893905fbf67286.jpg
492 ms
d4c96aa80cefb834d316fffb9ddd0e33.jpg
497 ms
c1e61ec90416b577d2ce40b9402d4aa0.jpg
674 ms
57855d28b74dee8203c3a165fc5f18d7.jpg
492 ms
475f139677804aa21118573a77e2f19a.jpg
673 ms
357b86668111c243d7b00e626a32c367.png
513 ms
8e5c51ea1c6eaccc8b3ddb2ad20cdb55.jpg
514 ms
d672174b17cba8a0ed17ede4c10a681c.jpg
565 ms
0703f105e68caf17d1b106a3608256ed.jpg
559 ms
3a11a3fcd1a421c1ab6bc3791ab3e883.jpg
534 ms
419671aa3eebecac90f0377103d21a91.jpg
532 ms
a4c970ccc91966c360b1b9aa52895b30.jpg
551 ms
a01ae05e028ea185336333e9921034ed.jpg
553 ms
9c6d32b1a0ba1c9e9bc67eefda54b44a.jpg
571 ms
587ea0dbf48dec6913fc539dc415f3a4.jpg
573 ms
6372e507ea2c312aa8fad394cf1a04cb.jpg
579 ms
6eae4797ceb0e38db5f57b75fbd25750.jpg
627 ms
0a9505024a21050de824a668b554e3dc.jpg
635 ms
180f0089e77b9ef94e673e7f14d4b978.jpg
637 ms
14a79912ea5a54668d4d74c7712bbe33.jpg
597 ms
01e9982f7fd061f60bbe59482f2c8735.jpg
614 ms
1e43f9fd26962cfd15e3c30b13a81b79.jpg
642 ms
8be397b3099fc4448572477415b1cde1.jpg
645 ms
shoeperbowl_modal.v60a5e7df.png
290 ms
8656a077359283b229512f4ee4465fd2.png
306 ms
77239536eed63a9439a64af91b35968a.png
591 ms
34edf538bf7c1959d2f923edce9a3c38.png
379 ms
7e013b9e4e3dc15a952049a113d2cb42.png
349 ms
8ab838f42db197d427061107b7fd7a1e.png
350 ms
ace16ce1a34633b2eaef5e7846a66711.jpg
313 ms
PN-reg.woff
148 ms
analytics.js
294 ms
get_all_actions_taken
76 ms
fbevents.js
374 ms
2338e9e66d6493f613fdab3e0efaa9a9.jpg
284 ms
bf021e6bdc19d9b390acef430693074b.jpg
286 ms
0a026b716f9f87b95d17b15a5d0e169a.jpg
326 ms
PN-semibold.woff
76 ms
newsletter-lightbox.png
26 ms
validating-spinner.gif
38 ms
PN-light.woff
34 ms
ec.js
30 ms
collect
44 ms
87369184b4554cc21cf0b6374ca72a8d.jpg
347 ms
5551a6001d9be421f7dd43a645791fde.jpg
340 ms
99258dd7e3a837b0ebb4b90190900dfb.jpg
316 ms
collect
70 ms
d8aa233d1da4e76800318106e8485f3d.jpg
280 ms
d577f5c428950af2af3ebaf5c23a086f.jpg
356 ms
1fe718114bff083ad0d0a00876a15fdc.jpg
259 ms
4902a795438dcfc0a650801b5aba3195.jpg
254 ms
106 ms
8a810501cdff794360d1e8f3dd90dd58.jpg
222 ms
1e1af46c36a023674dda4cd48c1cd2df.jpg
225 ms
7108b7e489fd87b4ec95ea4c70d1f035.jpg
225 ms
01d858a7c5e3ee6dc25ebf43fe50f5c4.jpg
231 ms
c5b9a8e9fcd3f51da8c900618edd7bfe.jpg
236 ms
e0267e3b709834b86e9c5c5c54db58a5.png
222 ms
ad32146215450b29c09a331d689ef551.jpg
224 ms
057d7a7dce3f3ec8bea34ff92a1ab4c4.jpg
222 ms
865c36e04e54772fe07be0a5c4c837fa.jpg
227 ms
e8c1adc5ef0f5c5f720e09df9122e10a.jpg
222 ms
83bd8d8d18cc14d3232643ccc6b8e9df.jpg
217 ms
e2e5505f87dc63ecdb70f8fc97f1e90c.jpg
267 ms
1bf97f65d37265383ac4eb5a002348c1.jpg
266 ms
46c0f28ee8a99ff433bdc23752497571.jpg
194 ms
6e6b311ffc54a73c02f3f87727c882c8.jpg
199 ms
7026d0cc320f9ff30d00c27a331e78eb.jpg
194 ms
418186b010e17619c5544b2742bbaa2f.jpg
197 ms
56e14b05481b49fde615cfd6bc8410f0.jpg
206 ms
c5ac394b32a91252c94b83acf8852620.jpg
201 ms
7a827c62944c9089650c517b26a822b2.jpg
203 ms
555870982fe28f868791eec762967bd6.jpg
199 ms
8b46a21fad4361ecb2b426a442111517.jpg
182 ms
599c24bd94835051ed4a3a6841ea4e5d.jpg
417 ms
1fdfd080c61b2ab6a86a274264f58a02.jpg
166 ms
9cd89c06538b30c0f0579fa52d695cfc.jpg
181 ms
268d1f4b2a1509e21d187f83835d91cf.jpg
180 ms
e8d5ef087ed49e90ffc22994de75f3a3.jpg
272 ms
df3d0ba603ae0fad32874b2f71deed40.jpg
256 ms
2949ce011803571a527d5ca6e074ce92.jpg
152 ms
0a52f0fe7e11262561228122abc09ae7.jpg
171 ms
97f1b87ffca76132db929c79e538f765.jpg
172 ms
31d35c1d3281d77311b76f23cb4972be.jpg
163 ms
34ee0947116fabaa102e22fa44fa9dfc.jpg
182 ms
5f055a79149b3568fec0d25b85b5d3c8.jpg
190 ms
09ad9c82715cfbf8d07209b72eadd79e.jpg
174 ms
8d105ccb2ff22798a6e980452f02b73c.jpg
193 ms
da36ef869051e34d9bde3cb15789bbfc.jpg
185 ms
4324ff6fd3668ee9c6a658e6d55ffe5a.jpg
196 ms
b619680c95cae1ce0ff8d183b3018338.jpg
198 ms
91dd924d5142b86dc293a7401d6123e5.jpg
195 ms
153c6b836e81caf759f0681474af8306.jpg
206 ms
keep.com 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.
keep.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
keep.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Tap targets are not sized appropriately
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keep.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Keep.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.
keep.com
Open Graph description is not detected on the main page of Keep. 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: