Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

kakophone.com

The kakophone : The music-composition machine for your mobile phone

Page Load Speed

1.2 sec in total

First Response

226 ms

Resources Loaded

888 ms

Page Rendered

70 ms

About Website

Visit kakophone.com now to see the best up-to-date Kako Phone content for France and also check out these interesting facts you probably never knew about kakophone.com

The kakophone is a free music generator. It can create thousands different tunes everyday, just by clicking and turning knobs. You can use it to compose your very unique ringtone, within a few seconds...

Visit kakophone.com

Key Findings

We analyzed Kakophone.com page load time and found that the first response time was 226 ms and then it took 958 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

kakophone.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

kakophone.com

226 ms

www.kakophone.com

447 ms

txt.css

84 ms

swfobject.js

167 ms

urchin.js

7 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 67% of them (4 requests) were addressed to the original Kakophone.com, 17% (1 request) were made to Google-analytics.com and 17% (1 request) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (447 ms) belongs to the original domain Kakophone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.7 kB (49%)

Content Size

19.6 kB

After Optimization

9.9 kB

In fact, the total size of Kakophone.com main page is 19.6 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. Only 5% of websites need less resources to load. Javascripts take 13.2 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.0 kB

  • Original 4.9 kB
  • After minification 4.8 kB
  • After compression 1.9 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 3.0 kB or 61% of the original size.

JavaScript Optimization

-41%

Potential reduce by 5.4 kB

  • Original 13.2 kB
  • After minification 12.6 kB
  • After compression 7.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 5.4 kB or 41% of the original size.

CSS Optimization

-83%

Potential reduce by 1.3 kB

  • Original 1.5 kB
  • After minification 1.3 kB
  • After compression 256 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. Kakophone.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kako Phone. According to our analytics all requests are already optimized.

Accessibility Review

kakophone.com accessibility score

88

Accessibility Issues

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

Best Practices

kakophone.com best practices score

67

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kakophone.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kakophone.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 Kakophone.com main page’s claimed encoding is iso-8859-1. 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

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