1.3 sec in total
125 ms
975 ms
205 ms
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.ioWe 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.
ahana.io performance score
name
value
score
weighting
Value19.6 s
0/100
10%
Value28.0 s
0/100
25%
Value30.3 s
0/100
10%
Value15,450 ms
0/100
30%
Value0.668
8/100
15%
Value43.9 s
0/100
10%
125 ms
128 ms
329 ms
145 ms
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 size can be reduced by 252.5 kB (43%)
592.9 kB
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.
Potential reduce by 148.6 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.
Potential reduce by 103.7 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.
Potential reduce by 172 B
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.
Number of requests can be reduced by 21 (91%)
23
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.
ahana.io
125 ms
watsonx-data
128 ms
ibm-common.js
329 ms
loader.js
145 ms
clientlib-idlStylesCarbon.min.ACSHASH6b7f7aca22f55d7ccef93668b20d1b11.css
70 ms
clientlib-idlStyles.min.ACSHASHb07d72d124dca340f1f121a435a56f0a.css
105 ms
plex.css
342 ms
sans.css
334 ms
masthead.min.js
337 ms
paragraph.min.js
335 ms
heading.min.js
335 ms
leadspace.min.js
360 ms
react.production.min.js
21 ms
react-dom.production.min.js
28 ms
react-intl.min.js
30 ms
main.a1b709bb.css
283 ms
main.c08dda2c.js
291 ms
clientlib-idlBundle.min.ACSHASH8e0a5ada9d90d4e69372aa22f35e468f.js
63 ms
clientlib-target-antiflicker.min.ACSHASH36a1efb28e947b5873f4a28c2cf9d5eb.js
112 ms
clientlib-idlWebComponents.min.ACSHASHaa58d161067036934162c981c49c78ef.js
323 ms
clientlib-idlStyles.min.ACSHASH0c4f9840b697954a53613c359277701b.js
111 ms
cm-app.min.js
300 ms
mR2A8ahk
276 ms
sec-4-3.css
122 ms
sec-cpt-4-3.js
277 ms
IBMPlexSans-Text.woff
31 ms
IBMPlexSans-Regular.woff
7 ms
IBMPlexSans-Medium.woff
6 ms
IBMPlexSans-Light.woff
28 ms
IBMPlexSans-ExtraLight.woff
30 ms
IBMPlexSans-Thin.woff
29 ms
IBMPlexSans-SemiBold.woff
27 ms
IBMPlexSans-Bold.woff
28 ms
IBMPlexSans-TextItalic.woff
63 ms
IBMPlexSans-Italic.woff
7 ms
IBMPlexSans-MediumItalic.woff
8 ms
IBMPlexSans-LightItalic.woff
9 ms
IBMPlexSans-ExtraLightItalic.woff
10 ms
IBMPlexSans-ThinItalic.woff
61 ms
IBMPlexSans-SemiBoldItalic.woff
60 ms
IBMPlexSans-BoldItalic.woff
61 ms
ffc8ae5d07a2166e6af1.ttf
62 ms
ahana.io accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ahana.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ahana.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
ahana.io
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: