Tools & Wizards About Us
srimannayagi.org screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

srimannayagi.org

Sri Natana Gopala Nayagi Swamigal Keerthans

Page Load Speed

1.7 sec in total

First Response

199 ms

Resources Loaded

1.4 sec

Page Rendered

148 ms

srimannayagi.org screenshot

About Website

Visit srimannayagi.org now to see the best up-to-date Sri Man Nayagi content and also check out these interesting facts you probably never knew about srimannayagi.org

Sriman Natanagopala Nayagi Swamigal Web page (complete)

Visit srimannayagi.org

Key Findings

We analyzed Srimannayagi.org page load time and found that the first response time was 199 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

srimannayagi.org performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

srimannayagi.org

199 ms

StyleSheet1.css

70 ms

NayagiMenu.js

135 ms

MeenaHari_01.gif

196 ms

MeenaHari_02.gif

133 ms

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

Page Optimization Overview & Recommendations

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

Content Size

172.3 kB

After Optimization

91.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Srimannayagi.org main page is 172.3 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. 20% of websites need less resources to load. Images take 83.4 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 73.2 kB

  • Original 78.7 kB
  • After minification 77.0 kB
  • After compression 5.5 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 73.2 kB or 93% of the original size.

Image Optimization

-6%

Potential reduce by 4.9 kB

  • Original 83.4 kB
  • After minification 78.5 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. Sri Man Nayagi images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 2.3 kB

  • Original 8.9 kB
  • After minification 8.9 kB
  • After compression 6.5 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 2.3 kB or 26% of the original size.

CSS Optimization

-41%

Potential reduce by 533 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 780 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. Srimannayagi.org needs all CSS files to be minified and compressed as it can save up to 533 B or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (59%)

Requests Now

88

After Optimization

36

  • Images
  • JavaScript
  • CSS

The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sri Man Nayagi. 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.

Network Requests Diagram

srimannayagi.org

srimannayagi.org

199 ms

StyleSheet1.css

StyleSheet1.css

70 ms

NayagiMenu.js

NayagiMenu.js

135 ms

MeenaHari_01.gif

MeenaHari_01.gif

196 ms

MeenaHari_02.gif

MeenaHari_02.gif

133 ms

MeenaHari_04.gif

MeenaHari_04.gif

68 ms

Menporul.gif

Menporul.gif

129 ms

2.jpg

2.jpg

259 ms

wesmalll.jpg

wesmalll.jpg

130 ms

Count.cgi

Count.cgi

132 ms

QHelp.gif

QHelp.gif

134 ms

QAppeal.gif

QAppeal.gif

191 ms

QSiteMap.gif

QSiteMap.gif

193 ms

fotter.gif

fotter.gif

197 ms

pbrowser_safari.js

pbrowser_safari.js

136 ms

mugappu.gif

mugappu.gif

68 ms

mugappul.gif

mugappul.gif

70 ms

Keerthansl.gif

Keerthansl.gif

67 ms

Keerthans.gif

Keerthans.gif

68 ms

Namavaligall.gif

Namavaligall.gif

69 ms

Namavaligal.gif

Namavaligal.gif

105 ms

SeviInbaml.gif

SeviInbaml.gif

135 ms

SeviInbam.gif

SeviInbam.gif

136 ms

mainmatravail.gif

mainmatravail.gif

137 ms

mainmatravai.gif

mainmatravai.gif

136 ms

Mugappurail.gif

Mugappurail.gif

138 ms

Mugappurai.gif

Mugappurai.gif

173 ms

Padippurail.gif

Padippurail.gif

201 ms

Padippurai.gif

Padippurai.gif

202 ms

Brindhavanl.gif

Brindhavanl.gif

204 ms

Brindhavan.gif

Brindhavan.gif

202 ms

Mandhirl.gif

Mandhirl.gif

202 ms

Mandhir.gif

Mandhir.gif

239 ms

Articlesl.gif

Articlesl.gif

275 ms

Articles.gif

Articles.gif

277 ms

Kurippul.gif

Kurippul.gif

275 ms

Kurippu.gif

Kurippu.gif

275 ms

pugaipadal.gif

pugaipadal.gif

276 ms

pugaipada.gif

pugaipada.gif

305 ms

Thodarbul.gif

Thodarbul.gif

335 ms

Thodarbu.gif

Thodarbu.gif

337 ms

Historyl.gif

Historyl.gif

339 ms

History.gif

History.gif

340 ms

GeethaNayagil.gif

GeethaNayagil.gif

339 ms

GeethaNayagi.gif

GeethaNayagi.gif

373 ms

Prabandhaml.gif

Prabandhaml.gif

403 ms

Prabandham.gif

Prabandham.gif

403 ms

NBhavaml.gif

NBhavaml.gif

404 ms

NBhavam.gif

NBhavam.gif

404 ms

andall.gif

andall.gif

397 ms

andal.gif

andal.gif

406 ms

Sourashtraml.gif

Sourashtraml.gif

406 ms

Sourashtram.gif

Sourashtram.gif

407 ms

Tamill.gif

Tamill.gif

408 ms

Tamil.gif

Tamil.gif

406 ms

TMSl.gif

TMSl.gif

408 ms

TMS.gif

TMS.gif

403 ms

TKRl.gif

TKRl.gif

405 ms

TKR.gif

TKR.gif

405 ms

VNNl.gif

VNNl.gif

405 ms

VNN.gif

VNN.gif

403 ms

TSRl.gif

TSRl.gif

405 ms

TSR.gif

TSR.gif

404 ms

TMCl.gif

TMCl.gif

407 ms

TMC.gif

TMC.gif

406 ms

avail.gif

avail.gif

406 ms

avai.gif

avai.gif

407 ms

2004cdl.gif

2004cdl.gif

406 ms

2004cd.gif

2004cd.gif

405 ms

Manraml.gif

Manraml.gif

402 ms

Manram.gif

Manram.gif

400 ms

vanolil.gif

vanolil.gif

400 ms

vanoli.gif

vanoli.gif

400 ms

IsaiThattul.gif

IsaiThattul.gif

401 ms

IsaiThattu.gif

IsaiThattu.gif

404 ms

matravail.gif

matravail.gif

407 ms

matravai.gif

matravai.gif

402 ms

katcheril.gif

katcheril.gif

404 ms

katcheri.gif

katcheri.gif

403 ms

OliNadal.gif

OliNadal.gif

404 ms

OliNada.gif

OliNada.gif

403 ms

cdreleasel.gif

cdreleasel.gif

403 ms

cdrelease.gif

cdrelease.gif

407 ms

guestbookl.gif

guestbookl.gif

404 ms

guestbook.gif

guestbook.gif

404 ms

nayagisevail.gif

nayagisevail.gif

405 ms

nayagisevai.gif

nayagisevai.gif

404 ms

newudavil.gif

newudavil.gif

402 ms

newudavi.gif

newudavi.gif

405 ms

Count.cgi

Count.cgi

404 ms

bgIndex.gif

bgIndex.gif

402 ms

Accessibility Review

srimannayagi.org accessibility score

58

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

srimannayagi.org 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

High

Browser errors were logged to the console

SEO Factors

srimannayagi.org SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Srimannayagi.org 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 Srimannayagi.org 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

srimannayagi.org

Open Graph description is not detected on the main page of Sri Man Nayagi. 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: