Tools & Wizards About Us
kuku.io screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

kuku.io

Page Load Speed

3.9 sec in total

First Response

208 ms

Resources Loaded

2.9 sec

Page Rendered

768 ms

kuku.io screenshot

About Website

Click here to check amazing Kuku content for Serbia. Otherwise, check out these important facts you probably never knew about kuku.io

Social media management app that allows you to adapt your voice for multiple social media networks, schedule and publish content to all of them at once

Visit kuku.io

Key Findings

We analyzed Kuku.io page load time and found that the first response time was 208 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

kuku.io performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

kuku.io

208 ms

kuku.io

578 ms

index.css

165 ms

sweet-alert.css

332 ms

jquery.min.js

657 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 86% of them (30 requests) were addressed to the original Kuku.io, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (684 ms) belongs to the original domain Kuku.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.9 kB (66%)

Content Size

759.0 kB

After Optimization

260.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kuku.io main page is 759.0 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. 40% of websites need less resources to load. Javascripts take 595.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 99.4 kB

  • Original 140.4 kB
  • After minification 134.7 kB
  • After compression 41.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 99.4 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 66 B

  • Original 22.9 kB
  • After minification 22.9 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. Kuku images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 399.4 kB

  • Original 595.4 kB
  • After minification 584.7 kB
  • After compression 196.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 399.4 kB or 67% of the original size.

CSS Optimization

-17%

Potential reduce by 32 B

  • Original 187 B
  • After minification 167 B
  • After compression 155 B

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. Kuku.io needs all CSS files to be minified and compressed as it can save up to 32 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (59%)

Requests Now

29

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kuku.io

kuku.io

208 ms

kuku.io

kuku.io

578 ms

index.css

index.css

165 ms

sweet-alert.css

sweet-alert.css

332 ms

jquery.min.js

jquery.min.js

657 ms

embed.v2.js

embed.v2.js

459 ms

sweet-alert.min.js

sweet-alert.min.js

361 ms

jquery.scroolly.min.js

jquery.scroolly.min.js

367 ms

main.js

main.js

369 ms

css

css

61 ms

config

config

223 ms

analytics.js

analytics.js

130 ms

yKBQ6HrJ7F

yKBQ6HrJ7F

392 ms

1en.png

1en.png

194 ms

2en.png

2en.png

179 ms

3en.png

3en.png

181 ms

4en.png

4en.png

186 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

299 ms

roboto-medium-webfont.woff

roboto-medium-webfont.woff

269 ms

roboto-light-webfont.woff

roboto-light-webfont.woff

333 ms

montserrat-bold-webfont.woff

montserrat-bold-webfont.woff

433 ms

roboto-bold-webfont.woff

roboto-bold-webfont.woff

439 ms

main.html

main.html

335 ms

collect

collect

12 ms

embed.html

embed.html

305 ms

edge.6.0.0.min.js

edge.6.0.0.min.js

451 ms

widget_en_US.js

widget_en_US.js

465 ms

app.min.js

app.min.js

684 ms

font-awesome.min.css

font-awesome.min.css

171 ms

bootstrap.min.css

bootstrap.min.css

269 ms

sweet-alert.css

sweet-alert.css

180 ms

embed.css

embed.css

172 ms

main_edge.js

main_edge.js

163 ms

preloader2.gif

preloader2.gif

172 ms

main_edge.js

main_edge.js

228 ms

Accessibility Review

kuku.io accessibility score

96

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

Best Practices

kuku.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kuku.io SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kuku.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Kuku.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

kuku.io

Open Graph data is detected on the main page of Kuku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: