Tools & Wizards About Us
m4marry.in screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

m4marry.in

M4Marry - Most Trusted Matrimonial Website for South Indians

Page Load Speed

2 sec in total

First Response

142 ms

Resources Loaded

1.4 sec

Page Rendered

386 ms

m4marry.in screenshot

About Website

Click here to check amazing M4Marry content. Otherwise, check out these important facts you probably never knew about m4marry.in

The Most Trusted Matrimony Sites for South Indians. Find verified profiles from Kerala, Karnataka, Tamil Nadu and Telangana. 100% secured matchmaking services with millions of success stories. Registe...

Visit m4marry.in

Key Findings

We analyzed M4marry.in page load time and found that the first response time was 142 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

m4marry.in performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

www.m4marry.com

142 ms

bootstrap.min-1.3.css

269 ms

colorbox-1.2.css

351 ms

m4marry-19.7.css

407 ms

jquery.min-1.4.js

489 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M4marry.in, 4% (3 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (659 ms) relates to the external source Static.m4marry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.2 kB (3%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M4marry.in main page is 3.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 65.6 kB

  • Original 81.8 kB
  • After minification 67.7 kB
  • After compression 16.2 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 14.1 kB, which is 17% 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 65.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 12.9 kB

  • Original 3.0 MB
  • After minification 3.0 MB

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. M4Marry images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 1.1 kB

  • Original 35.0 kB
  • After minification 35.0 kB
  • After compression 33.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. This website has mostly compressed JavaScripts.

CSS Optimization

-38%

Potential reduce by 438 B

  • Original 1.2 kB
  • After minification 1.1 kB
  • After compression 720 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. M4marry.in needs all CSS files to be minified and compressed as it can save up to 438 B or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (22%)

Requests Now

63

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.m4marry.com

www.m4marry.com

142 ms

bootstrap.min-1.3.css

bootstrap.min-1.3.css

269 ms

colorbox-1.2.css

colorbox-1.2.css

351 ms

m4marry-19.7.css

m4marry-19.7.css

407 ms

jquery.min-1.4.js

jquery.min-1.4.js

489 ms

bootstrap.min-1.4.js

bootstrap.min-1.4.js

487 ms

jquery.colorbox-1.7.js

jquery.colorbox-1.7.js

381 ms

lens.2.9-latest.js

lens.2.9-latest.js

47 ms

locale-0.8.js

locale-0.8.js

516 ms

common-9.7.js

common-9.7.js

516 ms

home-4.1.js

home-4.1.js

659 ms

register-5.7.js

register-5.7.js

550 ms

gtm.js

gtm.js

126 ms

WKQET-8QWZM-4Y25Y-GFW6J-TMY2P

WKQET-8QWZM-4Y25Y-GFW6J-TMY2P

380 ms

banner_64ae8ed546d4d.jpg

banner_64ae8ed546d4d.jpg

105 ms

ribbon-bg.jpg

ribbon-bg.jpg

70 ms

m4marry.newLogo.png

m4marry.newLogo.png

71 ms

ico.247.png

ico.247.png

81 ms

ico.refine.arrow.png

ico.refine.arrow.png

69 ms

language-icon.png

language-icon.png

72 ms

premium-services-bg.jpg

premium-services-bg.jpg

77 ms

royale-icon-img.png

royale-icon-img.png

74 ms

activeplus-icon-img.png

activeplus-icon-img.png

78 ms

matchmaking.png

matchmaking.png

80 ms

secure-confidential.png

secure-confidential.png

81 ms

manually-verified.png

manually-verified.png

81 ms

bg-pattern.jpg

bg-pattern.jpg

184 ms

quick-reg.slideB.jpg

quick-reg.slideB.jpg

98 ms

quick-reg.slideB1.jpg

quick-reg.slideB1.jpg

87 ms

quick-reg.slideC.jpg

quick-reg.slideC.jpg

90 ms

quick-reg.slideC1.jpg

quick-reg.slideC1.jpg

92 ms

quick-reg.slideD.jpg

quick-reg.slideD.jpg

100 ms

quick-reg.slideD1.jpg

quick-reg.slideD1.jpg

99 ms

quick-reg.slideE.jpg

quick-reg.slideE.jpg

134 ms

quick-reg.slideE1.jpg

quick-reg.slideE1.jpg

136 ms

quick-reg.slideF.jpg

quick-reg.slideF.jpg

134 ms

quick-reg.slideF1.jpg

quick-reg.slideF1.jpg

135 ms

quick-reg.slideG.jpg

quick-reg.slideG.jpg

180 ms

quick-reg.slideG1.jpg

quick-reg.slideG1.jpg

135 ms

quick-reg.slideH.jpg

quick-reg.slideH.jpg

136 ms

quick-reg.slideH1.jpg

quick-reg.slideH1.jpg

181 ms

quick-reg.slideI.jpg

quick-reg.slideI.jpg

182 ms

quick-reg.slideI1.jpg

quick-reg.slideI1.jpg

181 ms

appDownload-android-logo.png

appDownload-android-logo.png

183 ms

appDownload-iOS-logo.png

appDownload-iOS-logo.png

155 ms

m4marry.mobileApp-bg.png

m4marry.mobileApp-bg.png

127 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

127 ms

roboto_regular-webfont.woff

roboto_regular-webfont.woff

155 ms

m4marry.mobileApp-device-2023.png

m4marry.mobileApp-device-2023.png

123 ms

m4marry.mobileApp-text.png

m4marry.mobileApp-text.png

119 ms

m4marry.mobileApp-btn-apple.png

m4marry.mobileApp-btn-apple.png

120 ms

m4marry.mobileApp-btn-google.png

m4marry.mobileApp-btn-google.png

121 ms

icon-facebook.png

icon-facebook.png

118 ms

icon-instagram.png

icon-instagram.png

118 ms

icon-youtube.png

icon-youtube.png

115 ms

twitter-new.png

twitter-new.png

115 ms

js

js

55 ms

js

js

202 ms

analytics.js

analytics.js

196 ms

sdk.js

sdk.js

279 ms

beacon.js

beacon.js

194 ms

fbevents.js

fbevents.js

192 ms

blur-img.jpg

blur-img.jpg

148 ms

config.json

config.json

117 ms

collect

collect

81 ms

collect

collect

80 ms

collect

collect

82 ms

collect

collect

17 ms

Accessibility Review

m4marry.in accessibility score

84

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

m4marry.in best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Missing source maps for large first-party JavaScript

SEO Factors

m4marry.in SEO score

90

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

High

Tap targets are not sized appropriately

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 M4marry.in 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 M4marry.in 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

m4marry.in

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