1.7 sec in total
704 ms
835 ms
176 ms
Click here to check amazing Kahani content. Otherwise, check out these important facts you probably never knew about kahani.com
Kahani is back after a short break, and we're rebooting our presses! We created Kahani for children of South Asian heritages.
Visit kahani.comWe analyzed Kahani.com page load time and found that the first response time was 704 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
kahani.com performance score
name
value
score
weighting
Value14.3 s
0/100
10%
Value79.0 s
0/100
25%
Value22.9 s
0/100
10%
Value210 ms
89/100
30%
Value0.844
4/100
15%
Value79.2 s
0/100
10%
704 ms
92 ms
86 ms
106 ms
93 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 Kahani.com and no external sources were called. The less responsive or slowest element that took the longest time to load (704 ms) belongs to the original domain Kahani.com.
Page size can be reduced by 35.4 kB (21%)
168.9 kB
133.5 kB
In fact, the total size of Kahani.com main page is 168.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 123.8 kB which makes up the majority of the site volume.
Potential reduce by 3.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 538 B, which is 11% 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 3.6 kB or 73% of the original size.
Potential reduce by 0 B
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. Kahani images are well optimized though.
Potential reduce by 27.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 27.9 kB or 78% of the original size.
Potential reduce by 3.9 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. Kahani.com needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 91% of the original size.
Number of requests can be reduced by 7 (70%)
10
3
The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kahani. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
kahani.com
704 ms
style.css
92 ms
header_left_border.gif
86 ms
header_new.jpg
106 ms
header_right_border.gif
93 ms
bead.gif
92 ms
border_divider4.gif
71 ms
bead2.gif
116 ms
button_subscribe.gif
135 ms
button_current.gif
119 ms
button_contest.gi%20%3Cscript%20type=
113 ms
bg.gif
33 ms
kahani.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kahani.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
kahani.com SEO score
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kahani.com 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 Kahani.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
kahani.com
Open Graph description is not detected on the main page of Kahani. 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: