Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ahana.io

IBM watsonx.data

Page Load Speed

1.3 sec in total

First Response

125 ms

Resources Loaded

975 ms

Page Rendered

205 ms

ahana.io screenshot

About Website

Click here to check amazing Ahana content for United States. Otherwise, check out these important facts you probably never knew about ahana.io

The hybrid, open data lakehouse to power AI and analytics with all your data, anywhere.

Visit ahana.io

Key Findings

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

Performance Metrics

ahana.io performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value19.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.0 s

0/100

25%

SI (Speed Index)

Value30.3 s

0/100

10%

TBT (Total Blocking Time)

Value15,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.668

8/100

15%

TTI (Time to Interactive)

Value43.9 s

0/100

10%

Network Requests Diagram

ahana.io

125 ms

watsonx-data

128 ms

ibm-common.js

329 ms

loader.js

145 ms

clientlib-idlStylesCarbon.min.ACSHASH6b7f7aca22f55d7ccef93668b20d1b11.css

70 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ahana.io, 55% (23 requests) were made to 1.www.s81c.com and 29% (12 requests) were made to Ibm.com. The less responsive or slowest element that took the longest time to load (360 ms) relates to the external source 1.www.s81c.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.5 kB (43%)

Content Size

592.9 kB

After Optimization

340.4 kB

In fact, the total size of Ahana.io main page is 592.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 420.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 148.6 kB

  • Original 165.3 kB
  • After minification 141.4 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 23.8 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 148.6 kB or 90% of the original size.

JavaScript Optimization

-25%

Potential reduce by 103.7 kB

  • Original 420.6 kB
  • After minification 420.0 kB
  • After compression 316.9 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 103.7 kB or 25% of the original size.

CSS Optimization

-2%

Potential reduce by 172 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 6.8 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. Ahana.io has all CSS files already compressed.

Requests Breakdown

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

Requests Now

23

After Optimization

2

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

Accessibility Review

ahana.io 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-hidden="true"] elements contain focusable descendents

High

[role]s do not have all required [aria-*] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

ahana.io best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ahana.io SEO score

93

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

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

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