Tools & Wizards About Us
kakama.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

kakama.com

Disposable Non Woven Cleaning Cloths Manufacturers, Supplier

Page Load Speed

6.1 sec in total

First Response

653 ms

Resources Loaded

5.1 sec

Page Rendered

377 ms

kakama.com screenshot

About Website

Welcome to kakama.com homepage info - get ready to check Kakama best content right away, or after learning these important things about kakama.com

Kakama Technology Co., Ltd is China Disposable Cleaning Cloths Manufacturers and non woven cleaning cloth Suppliers, Offer wholesale Disposable non woven cleaning cloth for sale

Visit kakama.com

Key Findings

We analyzed Kakama.com page load time and found that the first response time was 653 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

kakama.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.373

28/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

www.kakama.com

653 ms

css

921 ms

slick.css

66 ms

basic.css

96 ms

main.css

119 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 89% of them (59 requests) were addressed to the original Kakama.com, 5% (3 requests) were made to Player.polyv.net and 2% (1 request) were made to Fonts.font.im. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Supertest.hqsmartcloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 481.7 kB (24%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kakama.com main page is 2.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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 424.4 kB

  • Original 468.4 kB
  • After minification 461.8 kB
  • After compression 44.0 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 424.4 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 52.8 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. Kakama images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 248 B

  • Original 24.4 kB
  • After minification 24.4 kB
  • After compression 24.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 4.3 kB

  • Original 44.4 kB
  • After minification 44.4 kB
  • After compression 40.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. Kakama.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (37%)

Requests Now

57

After Optimization

36

  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kakama. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.kakama.com

www.kakama.com

653 ms

css

css

921 ms

slick.css

slick.css

66 ms

basic.css

basic.css

96 ms

main.css

main.css

119 ms

font-awesome.min.css

font-awesome.min.css

128 ms

animate.min.css

animate.min.css

124 ms

jquery.js

jquery.js

145 ms

hwaq.js

hwaq.js

134 ms

qrcode.min.js

qrcode.min.js

169 ms

main.js

main.js

224 ms

slick.js

slick.js

244 ms

wow.min.js

wow.min.js

243 ms

swiper.min.css

swiper.min.css

200 ms

swiper.min.js

swiper.min.js

332 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

242 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

266 ms

index_js.js

index_js.js

310 ms

player.js

player.js

485 ms

layer.js

layer.js

310 ms

email-decode.min.js

email-decode.min.js

243 ms

logo.png

logo.png

146 ms

white-search.png

white-search.png

140 ms

en.jpg

en.jpg

140 ms

es.jpg

es.jpg

138 ms

banner1.jpg

banner1.jpg

185 ms

banner.jpg

banner.jpg

186 ms

banner-pro.png

banner-pro.png

151 ms

banner3.jpg

banner3.jpg

182 ms

product-cat.jpg

product-cat.jpg

230 ms

home-1.png

home-1.png

305 ms

111.jpg

111.jpg

786 ms

222.jpg

222.jpg

621 ms

care.png

care.png

858 ms

beacty.png

beacty.png

424 ms

pg.png

pg.png

382 ms

auchan.png

auchan.png

469 ms

2.png

2.png

870 ms

4.png

4.png

580 ms

5.png

5.png

854 ms

8.png

8.png

703 ms

11.png

11.png

733 ms

3.png

3.png

867 ms

1.png

1.png

839 ms

6-1.png

6-1.png

904 ms

9.png

9.png

953 ms

7.png

7.png

1022 ms

10.png

10.png

999 ms

111.png

111.png

1066 ms

left-jt.png

left-jt.png

953 ms

news-img.jpg

news-img.jpg

1042 ms

news-img2.jpg

news-img2.jpg

1063 ms

news-img1.jpg

news-img1.jpg

1098 ms

right-jt.png

right-jt.png

1091 ms

message-icon.png

message-icon.png

1118 ms

foot-logo.png

foot-logo.png

1159 ms

jszc_en_hei.svg

jszc_en_hei.svg

1140 ms

Lora-Regular.ttf

Lora-Regular.ttf

1223 ms

about-img.jpg

about-img.jpg

1245 ms

polyvplayer.min.js

polyvplayer.min.js

39 ms

layer.css

layer.css

1030 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1014 ms

upgrade_flash_player.png

upgrade_flash_player.png

29 ms

8QIHdirahM3j_su5uIg.ttf

8QIHdirahM3j_su5uIg.ttf

1109 ms

matomo.js

matomo.js

890 ms

matomo.php

matomo.php

1249 ms

Accessibility Review

kakama.com accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

kakama.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kakama.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kakama.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kakama.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.

Social Sharing Optimization

kakama.com

Open Graph description is not detected on the main page of Kakama. 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: