Tools & Wizards About Us
rellimatrimony.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% 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

rellimatrimony.com

Relli Matrimony - The No. 1 Matrimony Site for Rellis - RelliMatrimony.com

Page Load Speed

5 sec in total

First Response

531 ms

Resources Loaded

4.2 sec

Page Rendered

302 ms

rellimatrimony.com screenshot

About Website

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

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

Visit rellimatrimony.com

Key Findings

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

Performance Metrics

rellimatrimony.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

www.rellimatrimony.com

531 ms

jquery-3.5.1.min.js

286 ms

lazysizes.min.js

310 ms

jquery-ui.min.js

347 ms

homepage-seo.css

334 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 307.9 kB (38%)

Content Size

799.9 kB

After Optimization

492.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rellimatrimony.com main page is 799.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. 50% of websites need less resources to load. Javascripts take 310.6 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 275.3 kB
  • After minification 275.2 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. Relli Matrimony images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 132.8 kB

  • Original 310.6 kB
  • After minification 301.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 132.8 kB or 43% of the original size.

CSS Optimization

-83%

Potential reduce by 103.6 kB

  • Original 124.4 kB
  • After minification 108.7 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. Rellimatrimony.com needs all CSS files to be minified and compressed as it can save up to 103.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Relli 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.rellimatrimony.com

www.rellimatrimony.com

531 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

286 ms

lazysizes.min.js

lazysizes.min.js

310 ms

jquery-ui.min.js

jquery-ui.min.js

347 ms

homepage-seo.css

homepage-seo.css

334 ms

select2.full.min.js

select2.full.min.js

332 ms

materialmenu.jquery.js

materialmenu.jquery.js

329 ms

jquery.tinycarousel.min.js

jquery.tinycarousel.min.js

365 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

331 ms

hp-commonnew.js

hp-commonnew.js

337 ms

slick-theme.css

slick-theme.css

331 ms

retail-count.js

retail-count.js

341 ms

home_seo.js

home_seo.js

341 ms

lightslider.min.js

lightslider.min.js

341 ms

lightslider.min.css

lightslider.min.css

342 ms

js

js

48 ms

select2.min.css

select2.min.css

361 ms

slick.css

slick.css

361 ms

ajax.js

ajax.js

361 ms

trans.gif

trans.gif

101 ms

hp_menu_hamburger.png

hp_menu_hamburger.png

308 ms

logo_icon.svg

logo_icon.svg

42 ms

menu-top-arrow.png

menu-top-arrow.png

242 ms

password-eye-icon.png

password-eye-icon.png

191 ms

css

css

51 ms

popregnew.js

popregnew.js

105 ms

slick.min.js

slick.min.js

39 ms

help_newicon.svg

help_newicon.svg

229 ms

home_genericreg_bg.png

home_genericreg_bg.png

232 ms

dd_newicon.png

dd_newicon.png

208 ms

hp-frm-bg.png

hp-frm-bg.png

128 ms

google-event-track.js

google-event-track.js

63 ms

REL104137_eQO783_TS_1.jpg

REL104137_eQO783_TS_1.jpg

1092 ms

REL104132_2PEP1t_TS_1.jpg

REL104132_2PEP1t_TS_1.jpg

1905 ms

REL104131_BenFY4_TS_1.jpg

REL104131_BenFY4_TS_1.jpg

2117 ms

REL104128_XqY549_TS_1.jpg

REL104128_XqY549_TS_1.jpg

2074 ms

REL104130_7M2ieD_TS_1.jpg

REL104130_7M2ieD_TS_1.jpg

2046 ms

REL104122_TD9R1G_TS_1.jpg

REL104122_TD9R1G_TS_1.jpg

2092 ms

REL104129_qvV096_TS_1.jpg

REL104129_qvV096_TS_1.jpg

2096 ms

REL104120_ff7cRa_TS_1.jpg

REL104120_ff7cRa_TS_1.jpg

2742 ms

REL104125_NUU9Uh_TS_1.jpg

REL104125_NUU9Uh_TS_1.jpg

2868 ms

REL104093_HyW69_TS_1.jpg

REL104093_HyW69_TS_1.jpg

2919 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

82 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

107 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

118 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

106 ms

trustedhome_icon.png

trustedhome_icon.png

210 ms

ring_icon.png

ring_icon.png

88 ms

denominationshome_icon.png

denominationshome_icon.png

263 ms

genuinehome_icon.png

genuinehome_icon.png

267 ms

location_icon.png

location_icon.png

252 ms

Accessibility Review

rellimatrimony.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

rellimatrimony.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

rellimatrimony.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 Rellimatrimony.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 Rellimatrimony.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

rellimatrimony.com

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