Tools & Wizards About Us
mayyam.in screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

mayyam.in

Mayyam.in - The No.1 online matrimonial service provider in India

Page Load Speed

5.7 sec in total

First Response

390 ms

Resources Loaded

5.3 sec

Page Rendered

75 ms

mayyam.in screenshot

About Website

Click here to check amazing Mayyam content for India. Otherwise, check out these important facts you probably never knew about mayyam.in

The No.1 online matrimonial service provider. Secured matchmaking with exclusive privacy. Find Matches instantly, Join FREE!

Visit mayyam.in

Key Findings

We analyzed Mayyam.in page load time and found that the first response time was 390 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

mayyam.in performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value51.1 s

0/100

25%

SI (Speed Index)

Value41.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value58.5 s

0/100

10%

Network Requests Diagram

mayyam.in

390 ms

www.mayyam.in

773 ms

oj-redwood-min.css

751 ms

demo-alta-site-min.css

554 ms

all.css

745 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 92% of them (96 requests) were addressed to the original Mayyam.in, 2% (2 requests) were made to Connect.facebook.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mayyam.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.6 kB (30%)

Content Size

847.3 kB

After Optimization

596.7 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 28.5 kB

  • Original 34.5 kB
  • After minification 34.0 kB
  • After compression 6.1 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 28.5 kB or 82% of the original size.

JavaScript Optimization

-16%

Potential reduce by 101.7 kB

  • Original 656.0 kB
  • After minification 654.0 kB
  • After compression 554.3 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 101.7 kB or 16% of the original size.

CSS Optimization

-77%

Potential reduce by 120.4 kB

  • Original 156.7 kB
  • After minification 42.8 kB
  • After compression 36.3 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. Mayyam.in needs all CSS files to be minified and compressed as it can save up to 120.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (97%)

Requests Now

100

After Optimization

3

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

mayyam.in

mayyam.in

390 ms

www.mayyam.in

www.mayyam.in

773 ms

oj-redwood-min.css

oj-redwood-min.css

751 ms

demo-alta-site-min.css

demo-alta-site-min.css

554 ms

all.css

all.css

745 ms

places.js@1.18.1

places.js@1.18.1

46 ms

require.js

require.js

564 ms

main.js

main.js

614 ms

js

js

81 ms

sdk.js

sdk.js

15 ms

app-min.css

app-min.css

187 ms

ojbootstrap.js

ojbootstrap.js

209 ms

knockout.js

knockout.js

389 ms

appController.js

appController.js

193 ms

ojrouter.js

ojrouter.js

192 ms

ojlogger.js

ojlogger.js

366 ms

ojknockout.js

ojknockout.js

386 ms

ojmodule.js

ojmodule.js

387 ms

ojnavigationlist.js

ojnavigationlist.js

615 ms

ojbutton.js

ojbutton.js

552 ms

ojtoolbar.js

ojtoolbar.js

570 ms

sdk.js

sdk.js

5 ms

analytics.js

analytics.js

26 ms

Montserrat-Medium.ttf

Montserrat-Medium.ttf

1112 ms

ojcontext.js

ojcontext.js

377 ms

jquery-3.6.1.min.js

jquery-3.6.1.min.js

561 ms

commonController.js

commonController.js

542 ms

lightgallery.min.js

lightgallery.min.js

557 ms

ojmodule-element-utils.js

ojmodule-element-utils.js

574 ms

ojknockouttemplateutils.js

ojknockouttemplateutils.js

621 ms

ojresponsiveutils.js

ojresponsiveutils.js

727 ms

ojresponsiveknockoututils.js

ojresponsiveknockoututils.js

739 ms

ojarraydataprovider.js

ojarraydataprovider.js

746 ms

ojoffcanvas.js

ojoffcanvas.js

751 ms

ojmodule-element.js

ojmodule-element.js

825 ms

ojinputtext.js

ojinputtext.js

913 ms

ojknockout-validation.js

ojknockout-validation.js

921 ms

ojvalidation-number.js

ojvalidation-number.js

931 ms

platform.js

platform.js

37 ms

ojdialog.js

ojdialog.js

938 ms

ojprogressbar.js

ojprogressbar.js

1028 ms

ojmasonrylayout.js

ojmasonrylayout.js

1097 ms

ojradioset.js

ojradioset.js

1107 ms

ojselectcombobox.js

ojselectcombobox.js

1118 ms

ojdefer.js

ojdefer.js

1125 ms

ojcheckboxset.js

ojcheckboxset.js

1232 ms

ojpopup.js

ojpopup.js

1283 ms

ojformlayout.js

ojformlayout.js

1285 ms

ojvalidationgroup.js

ojvalidationgroup.js

1287 ms

ojavatar.js

ojavatar.js

1302 ms

loadingoverlay.min.js

loadingoverlay.min.js

1311 ms

ojselectsingle.js

ojselectsingle.js

1435 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

2024 ms

collect

collect

18 ms

js

js

118 ms

ojoption.js

ojoption.js

1119 ms

ojcore-base.js

ojcore-base.js

1120 ms

ojdomutils.js

ojdomutils.js

1138 ms

ojthemeutils.js

ojthemeutils.js

1148 ms

ojcomponentcore.js

ojcomponentcore.js

1290 ms

ojchildmutationobserver.js

ojchildmutationobserver.js

1285 ms

ojlabelledbyutils.js

ojlabelledbyutils.js

1282 ms

ojcustomelement-utils.js

ojcustomelement-utils.js

1262 ms

ojbutton2.js

ojbutton2.js

1149 ms

ojcomposite.js

ojcomposite.js

1025 ms

ojcore.js

ojcore.js

908 ms

ojconfig.js

ojconfig.js

909 ms

ojtranslation.js

ojtranslation.js

934 ms

ojL10n.js

ojL10n.js

945 ms

ojlocaledata.js

ojlocaledata.js

1090 ms

ojvalidation-base.js

ojvalidation-base.js

1091 ms

ojvalidator-numberrange.js

ojvalidator-numberrange.js

1119 ms

ojconverter-number.js

ojconverter-number.js

1114 ms

ojvalidationfactory-number.js

ojvalidationfactory-number.js

1131 ms

ojpopupcore.js

ojpopupcore.js

1268 ms

mouse.js

mouse.js

1268 ms

draggable.js

draggable.js

1273 ms

ojanimation.js

ojanimation.js

1206 ms

ojfocusutils.js

ojfocusutils.js

1156 ms

ojprogress.js

ojprogress.js

1149 ms

dnd-polyfill-1.0.2.min.js

dnd-polyfill-1.0.2.min.js

1282 ms

ojcustomelement.js

ojcustomelement.js

921 ms

ojtimerutils.js

ojtimerutils.js

559 ms

localeElements.js

localeElements.js

532 ms

ojmessaging.js

ojmessaging.js

416 ms

ojconverterutils-i18n.js

ojconverterutils-i18n.js

437 ms

ojconverter.js

ojconverter.js

548 ms

ojvalidator.js

ojvalidator.js

549 ms

ojvalidationfactory-base.js

ojvalidationfactory-base.js

565 ms

ojconverter-color.js

ojconverter-color.js

578 ms

ojvalidator-length.js

ojvalidator-length.js

601 ms

ojvalidator-regexp.js

ojvalidator-regexp.js

639 ms

ojvalidator-required.js

ojvalidator-required.js

730 ms

ojvalidation-error.js

ojvalidation-error.js

731 ms

ojvalidator-async.js

ojvalidator-async.js

742 ms

ie.js

ie.js

583 ms

version.js

version.js

608 ms

widget.js

widget.js

663 ms

data.js

data.js

728 ms

plugin.js

plugin.js

728 ms

safe-active-element.js

safe-active-element.js

741 ms

safe-blur.js

safe-blur.js

770 ms

scroll-parent.js

scroll-parent.js

789 ms

localeElements.js

localeElements.js

649 ms

Accessibility Review

mayyam.in accessibility score

86

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

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

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

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

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

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

SEO Factors

mayyam.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 Mayyam.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 Mayyam.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

mayyam.in

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