5.7 sec in total
391 ms
5.2 sec
67 ms
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.inWe analyzed Mayyam.in page load time and found that the first response time was 391 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.
mayyam.in performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value48.7 s
0/100
25%
Value36.0 s
0/100
10%
Value3,460 ms
2/100
30%
Value0.032
100/100
15%
Value57.1 s
0/100
10%
391 ms
758 ms
738 ms
565 ms
777 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 91% 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 (1.8 sec) belongs to the original domain Mayyam.in.
Page size can be reduced by 228.7 kB (29%)
783.8 kB
555.1 kB
In fact, the total size of Mayyam.in main page is 783.8 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. 55% of websites need less resources to load. Javascripts take 593.1 kB which makes up the majority of the site volume.
Potential reduce by 28.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 28.5 kB or 82% of the original size.
Potential reduce by 79.9 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 79.9 kB or 13% of the original size.
Potential reduce by 120.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.3 kB or 77% of the original size.
Number of requests can be reduced by 97 (96%)
101
4
The browser has sent 101 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.
mayyam.in
391 ms
www.mayyam.in
758 ms
oj-redwood-min.css
738 ms
demo-alta-site-min.css
565 ms
all.css
777 ms
places.js@1.18.1
19 ms
require.js
568 ms
main.js
568 ms
js
68 ms
sdk.js
15 ms
app-min.css
185 ms
ojbootstrap.js
203 ms
knockout.js
203 ms
appController.js
190 ms
ojrouter.js
202 ms
ojlogger.js
364 ms
ojknockout.js
559 ms
ojmodule.js
386 ms
ojnavigationlist.js
381 ms
ojbutton.js
381 ms
ojtoolbar.js
545 ms
sdk.js
5 ms
analytics.js
25 ms
Montserrat-Medium.ttf
1111 ms
ojcontext.js
376 ms
jquery-3.6.1.min.js
565 ms
commonController.js
576 ms
lightgallery.min.js
536 ms
ojmodule-element-utils.js
549 ms
ojknockouttemplateutils.js
562 ms
ojresponsiveutils.js
719 ms
ojresponsiveknockoututils.js
735 ms
ojarraydataprovider.js
749 ms
ojoffcanvas.js
751 ms
ojmodule-element.js
756 ms
ojinputtext.js
912 ms
ojknockout-validation.js
919 ms
ojvalidation-number.js
935 ms
platform.js
49 ms
ojdialog.js
939 ms
ojprogressbar.js
944 ms
ojmasonrylayout.js
1095 ms
ojradioset.js
1105 ms
ojselectcombobox.js
1135 ms
ojdefer.js
1135 ms
ojcheckboxset.js
1134 ms
ojpopup.js
1278 ms
ojformlayout.js
1287 ms
ojvalidationgroup.js
1288 ms
ojavatar.js
1324 ms
loadingoverlay.min.js
1320 ms
ojselectsingle.js
1320 ms
Montserrat-Regular.ttf
1826 ms
collect
12 ms
collect
31 ms
js
67 ms
ojoption.js
1288 ms
ojcore-base.js
1289 ms
ojdomutils.js
1324 ms
ojthemeutils.js
1324 ms
ojcomponentcore.js
1326 ms
ojchildmutationobserver.js
1312 ms
ojlabelledbyutils.js
1308 ms
ojcustomelement-utils.js
1326 ms
ojbutton2.js
1164 ms
ojcomposite.js
949 ms
ojcore.js
912 ms
ojconfig.js
925 ms
ojtranslation.js
950 ms
ojL10n.js
951 ms
ojlocaledata.js
957 ms
ojvalidation-base.js
1083 ms
ojvalidator-numberrange.js
1095 ms
ojconverter-number.js
1109 ms
ojvalidationfactory-number.js
1136 ms
ojpopupcore.js
1135 ms
mouse.js
1143 ms
draggable.js
1264 ms
ojanimation.js
1274 ms
ojfocusutils.js
1134 ms
ojprogress.js
1158 ms
dnd-polyfill-1.0.2.min.js
1156 ms
ojcustomelement.js
797 ms
ojtimerutils.js
541 ms
localeElements.js
512 ms
ojmessaging.js
397 ms
ojconverterutils-i18n.js
427 ms
ojconverter.js
429 ms
ojvalidator.js
439 ms
ojvalidationfactory-base.js
549 ms
ojconverter-color.js
567 ms
ojvalidator-length.js
581 ms
ojvalidator-regexp.js
612 ms
ojvalidator-required.js
615 ms
ojvalidation-error.js
626 ms
ojvalidator-async.js
732 ms
ie.js
693 ms
version.js
706 ms
widget.js
740 ms
data.js
619 ms
plugin.js
632 ms
safe-active-element.js
732 ms
safe-blur.js
758 ms
scroll-parent.js
772 ms
localeElements.js
601 ms
mayyam.in accessibility score
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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
mayyam.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mayyam.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: