Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

help.kigo.net

YieldPlanet SL Support

Page Load Speed

1.3 sec in total

First Response

544 ms

Resources Loaded

676 ms

Page Rendered

116 ms

help.kigo.net screenshot

About Website

Visit help.kigo.net now to see the best up-to-date Help Kigo content for United States and also check out these interesting facts you probably never knew about help.kigo.net

YieldPlanet SL Support Center helps you to find FAQ, how-to guides and step-by-step tutorials.

Visit help.kigo.net

Key Findings

We analyzed Help.kigo.net page load time and found that the first response time was 544 ms and then it took 792 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

help.kigo.net performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

help.kigo.net

544 ms

stub.js

37 ms

3_3_3.Finalorg.ajax4jsf.javascript.AjaxScript

45 ms

SfdcCore.js

30 ms

picklist.js

68 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Help.kigo.net and no external sources were called. The less responsive or slowest element that took the longest time to load (544 ms) belongs to the original domain Help.kigo.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 165.0 kB (61%)

Content Size

270.1 kB

After Optimization

105.1 kB

In fact, the total size of Help.kigo.net main page is 270.1 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. 20% of websites need less resources to load. Javascripts take 198.5 kB which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 32.9 kB

  • Original 71.6 kB
  • After minification 70.7 kB
  • After compression 38.7 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 32.9 kB or 46% of the original size.

JavaScript Optimization

-67%

Potential reduce by 132.1 kB

  • Original 198.5 kB
  • After minification 198.3 kB
  • After compression 66.4 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 132.1 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

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

Accessibility Review

help.kigo.net accessibility score

56

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

help.kigo.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

help.kigo.net SEO score

100

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Help.kigo.net 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 Help.kigo.net 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

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