Tools & Wizards About Us
edigamatrimony.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

edigamatrimony.com

Ediga Matrimony - The No. 1 Matrimony Site for Edigas - EdigaMatrimony.com

Page Load Speed

6.9 sec in total

First Response

394 ms

Resources Loaded

6.2 sec

Page Rendered

302 ms

edigamatrimony.com screenshot

About Website

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

EdigaMatrimony - The No. 1 & most successful Ediga Matrimony Site from CommunityMatrimony.com. Trusted by millions of Ediga Brides & Grooms world over. Register FREE!

Visit edigamatrimony.com

Key Findings

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

Performance Metrics

edigamatrimony.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

www.edigamatrimony.com

394 ms

jquery-3.5.1.min.js

193 ms

lazysizes.min.js

206 ms

jquery-ui.min.js

221 ms

homepage-seo.css

242 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Edigamatrimony.com, 61% (31 requests) were made to Imgs.edigamatrimony.com and 20% (10 requests) were made to Cbs.matrimonycdn.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Cbs.matrimonycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.7 kB (45%)

Content Size

434.9 kB

After Optimization

238.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 71.4 kB

  • Original 89.7 kB
  • After minification 79.5 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 10.2 kB, 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 71.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 91 B

  • Original 21.4 kB
  • After minification 21.3 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. Ediga Matrimony images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 120.8 kB

  • Original 298.5 kB
  • After minification 289.1 kB
  • After compression 177.8 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 120.8 kB or 40% of the original size.

CSS Optimization

-18%

Potential reduce by 4.4 kB

  • Original 25.2 kB
  • After minification 25.2 kB
  • After compression 20.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. Edigamatrimony.com needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (58%)

Requests Now

45

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.edigamatrimony.com

www.edigamatrimony.com

394 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

193 ms

lazysizes.min.js

lazysizes.min.js

206 ms

jquery-ui.min.js

jquery-ui.min.js

221 ms

homepage-seo.css

homepage-seo.css

242 ms

select2.full.min.js

select2.full.min.js

254 ms

materialmenu.jquery.js

materialmenu.jquery.js

263 ms

jquery.tinycarousel.min.js

jquery.tinycarousel.min.js

248 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

238 ms

hp-commonnew.js

hp-commonnew.js

235 ms

slick-theme.css

slick-theme.css

262 ms

retail-count.js

retail-count.js

261 ms

home_seo.js

home_seo.js

261 ms

lightslider.min.js

lightslider.min.js

304 ms

lightslider.min.css

lightslider.min.css

311 ms

js

js

56 ms

select2.min.css

select2.min.css

392 ms

slick.css

slick.css

308 ms

ajax.js

ajax.js

309 ms

trans.gif

trans.gif

226 ms

hp_menu_hamburger.png

hp_menu_hamburger.png

441 ms

logo_icon.svg

logo_icon.svg

91 ms

menu-top-arrow.png

menu-top-arrow.png

306 ms

password-eye-icon.png

password-eye-icon.png

287 ms

css

css

27 ms

popregnew.js

popregnew.js

123 ms

slick.min.js

slick.min.js

135 ms

help_newicon.svg

help_newicon.svg

114 ms

hp-frm-bg.png

hp-frm-bg.png

511 ms

dd_newicon.png

dd_newicon.png

137 ms

google-event-track.js

google-event-track.js

151 ms

EDG135047_cPB409_TS_2.jpg

EDG135047_cPB409_TS_2.jpg

1254 ms

EDG135029_jDZ359_TS_1.jpg

EDG135029_jDZ359_TS_1.jpg

2040 ms

EDG135040_Fa683_TS_1.jpg

EDG135040_Fa683_TS_1.jpg

2496 ms

EDG135021_Cij897_TS_1.jpg

EDG135021_Cij897_TS_1.jpg

2199 ms

EDG135037_kUP18_TS_1.jpg

EDG135037_kUP18_TS_1.jpg

2099 ms

EDG135019_nEDF9d_TS_1.jpg

EDG135019_nEDF9d_TS_1.jpg

3227 ms

EDG135031_Fgl05_TS_1.jpg

EDG135031_Fgl05_TS_1.jpg

2173 ms

EDG135007_kmR627_TS_1.jpg

EDG135007_kmR627_TS_1.jpg

2837 ms

EDG135028_rXg408_TS_1.jpg

EDG135028_rXg408_TS_1.jpg

2977 ms

EDG134996_VtB67_TS_1.jpg

EDG134996_VtB67_TS_1.jpg

5233 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

50 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

51 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

98 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

99 ms

trustedhome_icon.png

trustedhome_icon.png

300 ms

ring_icon.png

ring_icon.png

467 ms

denominationshome_icon.png

denominationshome_icon.png

367 ms

genuinehome_icon.png

genuinehome_icon.png

168 ms

location_icon.png

location_icon.png

538 ms

Accessibility Review

edigamatrimony.com accessibility score

98

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 input fields do not have accessible names

Best Practices

edigamatrimony.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

edigamatrimony.com 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 Edigamatrimony.com 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 Edigamatrimony.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

edigamatrimony.com

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