Tools & Wizards About Us
kandy.io screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

kandy.io

Kandy - Skyvera

Page Load Speed

1.8 sec in total

First Response

39 ms

Resources Loaded

1.5 sec

Page Rendered

311 ms

kandy.io screenshot

About Website

Click here to check amazing Kandy content for Turkey. Otherwise, check out these important facts you probably never knew about kandy.io

A cloud-based, real-time communications platform with products that enrich clients’ applications and services with a more engaging user experience.

Visit kandy.io

Key Findings

We analyzed Kandy.io page load time and found that the first response time was 39 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

kandy.io performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value5.2 s

61/100

10%

TBT (Total Blocking Time)

Value650 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

36/100

10%

Network Requests Diagram

kandy.io

39 ms

308 ms

form-basic.css

14 ms

main.min.css

22 ms

header.min.css

33 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Kandy.io, 84% (46 requests) were made to Skyvera.com and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (640 ms) relates to the external source Skyvera.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.8 kB (18%)

Content Size

379.9 kB

After Optimization

313.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 65.9 kB

  • Original 77.4 kB
  • After minification 76.3 kB
  • After compression 11.5 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 65.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 156 B

  • Original 151.4 kB
  • After minification 151.4 kB
  • After compression 151.3 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

-1%

Potential reduce by 716 B

  • Original 75.2 kB
  • After minification 75.0 kB
  • After compression 74.5 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. Kandy.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (91%)

Requests Now

47

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kandy.io

kandy.io

39 ms

308 ms

form-basic.css

form-basic.css

14 ms

main.min.css

main.min.css

22 ms

header.min.css

header.min.css

33 ms

page-header.min.css

page-header.min.css

25 ms

blocks.min.css

blocks.min.css

30 ms

utilities.min.css

utilities.min.css

35 ms

studio.min.css

studio.min.css

31 ms

desktop.min.css

desktop.min.css

36 ms

style.css

style.css

36 ms

elementor-icons.min.css

elementor-icons.min.css

51 ms

frontend-lite.min.css

frontend-lite.min.css

45 ms

swiper.min.css

swiper.min.css

51 ms

post-951.css

post-951.css

54 ms

frontend-lite.min.css

frontend-lite.min.css

52 ms

global.css

global.css

52 ms

post-1362.css

post-1362.css

54 ms

post-1196.css

post-1196.css

59 ms

post-1079.css

post-1079.css

58 ms

post-1291.css

post-1291.css

57 ms

css

css

35 ms

fontawesome.min.css

fontawesome.min.css

63 ms

solid.min.css

solid.min.css

71 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

65 ms

footer.min.css

footer.min.css

68 ms

skip-links.min.js

skip-links.min.js

68 ms

jquery.min.js

jquery.min.js

88 ms

jquery.sticky.min.js

jquery.sticky.min.js

97 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

98 ms

global.min.js

global.min.js

100 ms

menus.min.js

menus.min.js

100 ms

header.min.js

header.min.js

129 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

99 ms

webpack.runtime.min.js

webpack.runtime.min.js

99 ms

frontend-modules.min.js

frontend-modules.min.js

129 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

129 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

130 ms

wp-polyfill.min.js

wp-polyfill.min.js

130 ms

hooks.min.js

hooks.min.js

136 ms

i18n.min.js

i18n.min.js

127 ms

frontend.min.js

frontend.min.js

127 ms

waypoints.min.js

waypoints.min.js

120 ms

core.min.js

core.min.js

120 ms

frontend.min.js

frontend.min.js

117 ms

elements-handlers.min.js

elements-handlers.min.js

122 ms

gtm.js

gtm.js

80 ms

Skyvera-logo-navy.png

Skyvera-logo-navy.png

64 ms

Kandy-Logo_Kandy-Pink-With-Line-3.png

Kandy-Logo_Kandy-Pink-With-Line-3.png

640 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

20 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

24 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

33 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

37 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

36 ms

Accessibility Review

kandy.io accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

kandy.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

SEO Factors

kandy.io SEO score

93

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kandy.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kandy.io 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

kandy.io

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