Tools & Wizards About Us
onlinerishte.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

onlinerishte.com

Welcome to Onlinerishte.com - The Best Indian Matrimonial Site For Matrimony, Rishtey, Shaadi & Marriage

Page Load Speed

5.7 sec in total

First Response

1.4 sec

Resources Loaded

4.1 sec

Page Rendered

235 ms

onlinerishte.com screenshot

About Website

Click here to check amazing Onlinerishte content. Otherwise, check out these important facts you probably never knew about onlinerishte.com

This is Online Matrimony Portal for Shaadi, Shadi, Rishtey, Rishte, Matrimony, Matrimonial and Vivah. No. 1 Matrimonial Portal in India, North India, Punjab, Haryana, Chandigarh, Delhi, Himachal Prade...

Visit onlinerishte.com

Key Findings

We analyzed Onlinerishte.com page load time and found that the first response time was 1.4 sec and then it took 4.3 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

onlinerishte.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.147

76/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

onlinerishte.com

1361 ms

jquery.min.js

578 ms

images2.css

390 ms

bootstrapn.css

592 ms

master.css

391 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 89% of them (59 requests) were addressed to the original Onlinerishte.com, 6% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Onlinerishte.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.8 kB (23%)

Content Size

1.2 MB

After Optimization

946.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onlinerishte.com main page is 1.2 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. 50% of websites need less resources to load. Images take 631.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 102.9 kB

  • Original 122.8 kB
  • After minification 96.6 kB
  • After compression 19.9 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 26.2 kB, which is 21% 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 102.9 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 11.1 kB

  • Original 631.8 kB
  • After minification 620.7 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. Onlinerishte images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 145.5 kB

  • Original 408.9 kB
  • After minification 408.9 kB
  • After compression 263.4 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 145.5 kB or 36% of the original size.

CSS Optimization

-34%

Potential reduce by 22.3 kB

  • Original 64.9 kB
  • After minification 62.9 kB
  • After compression 42.5 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. Onlinerishte.com needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onlinerishte.com

onlinerishte.com

1361 ms

jquery.min.js

jquery.min.js

578 ms

images2.css

images2.css

390 ms

bootstrapn.css

bootstrapn.css

592 ms

master.css

master.css

391 ms

ajax.js

ajax.js

431 ms

search.js

search.js

430 ms

java_script.js

java_script.js

598 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

786 ms

mouse_over.css

mouse_over.css

653 ms

photo_popup.css

photo_popup.css

657 ms

main.css

main.css

772 ms

css

css

32 ms

owl.carousel.css

owl.carousel.css

780 ms

owl.theme.css

owl.theme.css

784 ms

owl.transitions.css

owl.transitions.css

871 ms

jQuery.v1.8.2.min.js

jQuery.v1.8.2.min.js

1093 ms

modernizr.custom.79639.js

modernizr.custom.79639.js

970 ms

bootstrap.js

bootstrap.js

988 ms

html5.js

html5.js

984 ms

owl.carousel.min.js

owl.carousel.min.js

986 ms

amicss.css

amicss.css

1091 ms

newmain.css

newmain.css

1174 ms

jquery-ui-1.8.8.custom.min.js

jquery-ui-1.8.8.custom.min.js

1377 ms

jquery-ui.css

jquery-ui.css

1189 ms

jquery-ui.js

jquery-ui.js

1585 ms

jquery.min.js

jquery.min.js

25 ms

font-awesome.css

font-awesome.css

1315 ms

shBrushXml.js

shBrushXml.js

1127 ms

jquery.bxslider2.min.js

jquery.bxslider2.min.js

1185 ms

bjqs-1.3.min.js

bjqs-1.3.min.js

1204 ms

validationEngine.jquery.css

validationEngine.jquery.css

1345 ms

jquery.validationEngine-en.js

jquery.validationEngine-en.js

1349 ms

jquery.validationEngine.js

jquery.validationEngine.js

1385 ms

scripts.js

scripts.js

1389 ms

css

css

13 ms

4880l1.png

4880l1.png

197 ms

welcomelogo.png

welcomelogo.png

216 ms

android-app-banner.png

android-app-banner.png

775 ms

app.png

app.png

217 ms

assited.png

assited.png

590 ms

WhatsApp-help.png

WhatsApp-help.png

197 ms

g+.png

g+.png

392 ms

in.png

in.png

398 ms

insta.png

insta.png

434 ms

youtube.png

youtube.png

434 ms

facebook_icon.png

facebook_icon.png

588 ms

twitter_icon.png

twitter_icon.png

596 ms

batch.png

batch.png

649 ms

1372bg.jpg

1372bg.jpg

1059 ms

image_iframe_male.php

image_iframe_male.php

781 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

68 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

76 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

91 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

746 ms

imagesiframe.php

imagesiframe.php

776 ms

back2.png

back2.png

818 ms

style2.css

style2.css

200 ms

photoprocess.php

photoprocess.php

230 ms

trans.gif

trans.gif

205 ms

photoprocess.php

photoprocess.php

212 ms

photoprocess.php

photoprocess.php

296 ms

photoprocess.php

photoprocess.php

475 ms

photoprocess.php

photoprocess.php

469 ms

photoprocess.php

photoprocess.php

432 ms

Accessibility Review

onlinerishte.com accessibility score

50

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Some elements have a [tabindex] value greater than 0

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 IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

onlinerishte.com best practices score

58

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

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

Page has valid source maps

SEO Factors

onlinerishte.com SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

onlinerishte.com

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