Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

kelloo.com

Resource management, project and work planning software | Kelloo

Page Load Speed

5.5 sec in total

First Response

235 ms

Resources Loaded

4.6 sec

Page Rendered

615 ms

About Website

Visit kelloo.com now to see the best up-to-date Kelloo content and also check out these interesting facts you probably never knew about kelloo.com

Join 1000s of project, product & agile teams who use Kelloo to plan, forecast and manage their resources, work and capacity. 30 day trial.

Visit kelloo.com

Key Findings

We analyzed Kelloo.com page load time and found that the first response time was 235 ms and then it took 5.3 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

kelloo.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value7.1 s

30/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

kelloo.com

235 ms

www.kelloo.com

499 ms

3cc5741cc7a8f63635b69df75989b7ca.css

385 ms

css

36 ms

css

52 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 66% of them (46 requests) were addressed to the original Kelloo.com, 17% (12 requests) were made to Fonts.gstatic.com and 13% (9 requests) were made to . The less responsive or slowest element that took the longest time to load (558 ms) belongs to the original domain Kelloo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.6 kB (27%)

Content Size

697.7 kB

After Optimization

511.1 kB

In fact, the total size of Kelloo.com main page is 697.7 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. 55% of websites need less resources to load. CSS take 195.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 140.9 kB

  • Original 168.2 kB
  • After minification 168.0 kB
  • After compression 27.3 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 140.9 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-10%

Potential reduce by 16.8 kB

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

CSS Optimization

-15%

Potential reduce by 28.8 kB

  • Original 195.4 kB
  • After minification 195.4 kB
  • After compression 166.6 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. Kelloo.com needs all CSS files to be minified and compressed as it can save up to 28.8 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

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

Accessibility Review

kelloo.com accessibility score

85

Accessibility Issues

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-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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

[id] attributes on active, focusable elements are not unique

Best Practices

kelloo.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

kelloo.com SEO score

91

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

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

    EN

  • Encoding

    UTF-8

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

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