Tools & Wizards About Us
janamkatha.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

janamkatha.com

Page Load Speed

7.1 sec in total

First Response

79 ms

Resources Loaded

6.2 sec

Page Rendered

859 ms

janamkatha.com screenshot

About Website

Welcome to janamkatha.com homepage info - get ready to check Janamkatha best content for India right away, or after learning these important things about janamkatha.com

Learn Hindi » Everything in hindi - a blog about Biography/ Jivani, Essay, Govt Schemes, Fun facts in hindi.

Visit janamkatha.com

Key Findings

We analyzed Janamkatha.com page load time and found that the first response time was 79 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

janamkatha.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value30.1 s

0/100

10%

TBT (Total Blocking Time)

Value50,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value66.9 s

0/100

10%

Network Requests Diagram

janamkatha.com

79 ms

www.janamkatha.com

632 ms

fads.js

66 ms

banger.js

109 ms

adsbygoogle.js

170 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 13% of them (13 requests) were addressed to the original Janamkatha.com, 17% (18 requests) were made to Cm.g.doubleclick.net and 11% (11 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.1 kB (47%)

Content Size

928.4 kB

After Optimization

492.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Janamkatha.com main page is 928.4 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. 70% of websites need less resources to load. Javascripts take 473.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 205.8 kB

  • Original 267.1 kB
  • After minification 267.0 kB
  • After compression 61.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 205.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 188.2 kB
  • After minification 186.6 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. Janamkatha images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 228.7 kB

  • Original 473.1 kB
  • After minification 416.1 kB
  • After compression 244.4 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 228.7 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (72%)

Requests Now

89

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

janamkatha.com

janamkatha.com

79 ms

www.janamkatha.com

www.janamkatha.com

632 ms

fads.js

fads.js

66 ms

banger.js

banger.js

109 ms

adsbygoogle.js

adsbygoogle.js

170 ms

cmbv2.js

cmbv2.js

96 ms

AVvXsEgGi36WcbHkqUN2CgXcCUrxwQ0LI2FWORPAgesy3y3sKcK2ydPA4B4g-eAUZIRuSXkjGSegyxEMIYuubJgDtLiFJA5vkJWbePQAfsHTHfqzvbcj6X744y6HxLkvDX_hzPWFXz4o8oMiuhbusU5ojDEzZiTqgLJPr7AIKGMj0h4r6-9xx7F9F2_cdugyaA=w300

AVvXsEgGi36WcbHkqUN2CgXcCUrxwQ0LI2FWORPAgesy3y3sKcK2ydPA4B4g-eAUZIRuSXkjGSegyxEMIYuubJgDtLiFJA5vkJWbePQAfsHTHfqzvbcj6X744y6HxLkvDX_hzPWFXz4o8oMiuhbusU5ojDEzZiTqgLJPr7AIKGMj0h4r6-9xx7F9F2_cdugyaA=w300

530 ms

jivani

jivani

570 ms

ezoic.png

ezoic.png

249 ms

iGz9KiU.gif

iGz9KiU.gif

236 ms

1583485740-widgets.js

1583485740-widgets.js

236 ms

augusta.js

augusta.js

113 ms

o-0IIpQlx3QUlC5A4PNb4Q.woff

o-0IIpQlx3QUlC5A4PNb4Q.woff

271 ms

o-0NIpQlx3QUlC5A4PNjXhFlYA.woff

o-0NIpQlx3QUlC5A4PNjXhFlYA.woff

529 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

304 ms

nmash.js

nmash.js

146 ms

cmbdv2.js

cmbdv2.js

140 ms

show_ads_impl.js

show_ads_impl.js

163 ms

zrt_lookup.html

zrt_lookup.html

71 ms

basher.ezodn.com

basher.ezodn.com

45 ms

cookie.js

cookie.js

74 ms

integrator.js

integrator.js

77 ms

ads

ads

422 ms

integrator.js

integrator.js

16 ms

ads

ads

735 ms

Amazing%20Facts

Amazing%20Facts

489 ms

reactive_library.js

reactive_library.js

88 ms

ca-pub-6983401967503011

ca-pub-6983401967503011

127 ms

integrator.js

integrator.js

25 ms

ads

ads

557 ms

o-0OIpQlx3QUlC5A4PNr4DRG.woff

o-0OIpQlx3QUlC5A4PNr4DRG.woff

123 ms

o-0TIpQlx3QUlC5A4PNr4Az5ZtyH.woff

o-0TIpQlx3QUlC5A4PNr4Az5ZtyH.woff

270 ms

invoke.js

invoke.js

105 ms

integrator.js

integrator.js

56 ms

ads

ads

473 ms

5bbe539ad7c95ad1b7dc2874c2ab6f46.js

5bbe539ad7c95ad1b7dc2874c2ab6f46.js

358 ms

load_preloaded_resource.js

load_preloaded_resource.js

483 ms

2c31c29323708f8c18cb525f4f35abd1.js

2c31c29323708f8c18cb525f4f35abd1.js

399 ms

abg_lite.js

abg_lite.js

509 ms

window_focus.js

window_focus.js

813 ms

qs_click_protection.js

qs_click_protection.js

507 ms

rx_lidar.js

rx_lidar.js

487 ms

fac60d4cdc0b8be56d9f8d6f9ac54a3d.js

fac60d4cdc0b8be56d9f8d6f9ac54a3d.js

349 ms

ads

ads

936 ms

css

css

919 ms

css

css

1012 ms

m_js_controller.js

m_js_controller.js

738 ms

integrator.js

integrator.js

194 ms

ads

ads

733 ms

summary

summary

709 ms

icon.png

icon.png

145 ms

downsize_200k_v1

downsize_200k_v1

452 ms

s

s

501 ms

cookie_push_onload.html

cookie_push_onload.html

498 ms

css

css

326 ms

summary

summary

576 ms

dpixel

dpixel

575 ms

trk

trk

922 ms

https://:0/

https://:0/

360 ms

downsize_200k_v1

downsize_200k_v1

428 ms

activeview

activeview

243 ms

activeview

activeview

550 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

287 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

286 ms

LKD9GaYAUlEKqmF0ENHbHL4TSMlp96a1WK2pS7gMh1I.js

LKD9GaYAUlEKqmF0ENHbHL4TSMlp96a1WK2pS7gMh1I.js

535 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

522 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

516 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

519 ms

dpixel

dpixel

378 ms

integrator.js

integrator.js

673 ms

ads

ads

1068 ms

adsbygoogle.js

adsbygoogle.js

534 ms

analytics.js

analytics.js

1220 ms

activeview

activeview

457 ms

houston.js

houston.js

828 ms

pixel

pixel

499 ms

pixel

pixel

488 ms

pixel

pixel

693 ms

pixel

pixel

631 ms

pixel

pixel

630 ms

pixel

pixel

617 ms

downsize_200k_v1

downsize_200k_v1

269 ms

413ecad83b8ff83bc77baaf535b6a876.js

413ecad83b8ff83bc77baaf535b6a876.js

184 ms

ads

ads

322 ms

downsize_200k_v1

downsize_200k_v1

259 ms

pixel

pixel

266 ms

pixel

pixel

258 ms

pixel

pixel

256 ms

pixel

pixel

231 ms

pixel

pixel

226 ms

collect

collect

424 ms

collect

collect

154 ms

pixel

pixel

40 ms

pixel

pixel

35 ms

pixel

pixel

37 ms

dall.js

dall.js

310 ms

pixel

pixel

103 ms

pixel

pixel

84 ms

pixel

pixel

98 ms

activeview

activeview

96 ms

activeview

activeview

63 ms

pixel

pixel

27 ms

ga-audiences

ga-audiences

20 ms

Accessibility Review

janamkatha.com accessibility score

87

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

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

janamkatha.com best practices score

67

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

janamkatha.com SEO score

64

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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

    HI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Janamkatha.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Hindi language. Our system also found out that Janamkatha.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

janamkatha.com

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