Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

gekko.ai

Gekko | Accelerate Legal Research & Document Vetting

Page Load Speed

5.5 sec in total

First Response

482 ms

Resources Loaded

4.9 sec

Page Rendered

128 ms

gekko.ai screenshot

About Website

Visit gekko.ai now to see the best up-to-date Gekko content and also check out these interesting facts you probably never knew about gekko.ai

{% block siteDescription %}Gekko Lab is an award-winning Hong Kong-based data company for financial intelligence and investigation, whose knowledge management software enhances users’ capability to de...

Visit gekko.ai

Key Findings

We analyzed Gekko.ai page load time and found that the first response time was 482 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gekko.ai performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value15.4 s

0/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

gekko.ai

482 ms

gekko.ai

862 ms

www.gekko.ai

1428 ms

index-dfca946e.css

2151 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Gekko.ai and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Gekko.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.6 kB (71%)

Content Size

384.4 kB

After Optimization

111.8 kB

In fact, the total size of Gekko.ai main page is 384.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 377.5 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 4.1 kB

  • Original 6.9 kB
  • After minification 6.8 kB
  • After compression 2.8 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 4.1 kB or 60% of the original size.

CSS Optimization

-71%

Potential reduce by 268.5 kB

  • Original 377.5 kB
  • After minification 376.2 kB
  • After compression 109.0 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. Gekko.ai needs all CSS files to be minified and compressed as it can save up to 268.5 kB or 71% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

Accessibility Review

gekko.ai accessibility score

77

Accessibility Issues

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

Image elements do not have [alt] attributes

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

gekko.ai 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

High

Missing source maps for large first-party JavaScript

SEO Factors

gekko.ai SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Gekko.ai 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 Gekko.ai 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 Gekko. 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: