Tools & Wizards About Us
searchandmarry.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

searchandmarry.com

Page Load Speed

2.6 sec in total

First Response

498 ms

Resources Loaded

1.6 sec

Page Rendered

521 ms

searchandmarry.com screenshot

About Website

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

This matrimonial website has been created to serve people of India to find suitable life partner. We work specifically in Delhi, Noida, Gurgaon and National Capital Region. Create free Matrimonial Pro...

Visit searchandmarry.com

Key Findings

We analyzed Searchandmarry.com page load time and found that the first response time was 498 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

searchandmarry.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

searchandmarry.com

498 ms

style.css

119 ms

font-awesome.css

116 ms

bootstrap.min.css

160 ms

font-awesome.min.css

13 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 88% of them (68 requests) were addressed to the original Searchandmarry.com, 3% (2 requests) were made to Maxcdn.bootstrapcdn.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (498 ms) belongs to the original domain Searchandmarry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (84%)

Content Size

2.1 MB

After Optimization

331.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Searchandmarry.com main page is 2.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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 187.7 kB

  • Original 223.9 kB
  • After minification 124.3 kB
  • After compression 36.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 99.6 kB, which is 44% 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 187.7 kB or 84% of the original size.

Image Optimization

-94%

Potential reduce by 1.5 MB

  • Original 1.6 MB
  • After minification 105.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. Obviously, Searchandmarry needs image optimization as it can save up to 1.5 MB or 94% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 23.9 kB

  • Original 168.3 kB
  • After minification 161.3 kB
  • After compression 144.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 23.9 kB or 14% of the original size.

CSS Optimization

-3%

Potential reduce by 1.2 kB

  • Original 46.0 kB
  • After minification 46.0 kB
  • After compression 44.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. Searchandmarry.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

66

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

searchandmarry.com

searchandmarry.com

498 ms

style.css

style.css

119 ms

font-awesome.css

font-awesome.css

116 ms

bootstrap.min.css

bootstrap.min.css

160 ms

font-awesome.min.css

font-awesome.min.css

13 ms

md5Home.js

md5Home.js

120 ms

fadeslideshow.js

fadeslideshow.js

121 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

180 ms

bootstrap.min.js

bootstrap.min.js

200 ms

jquery.signalR-1.1.4.min.js

jquery.signalR-1.1.4.min.js

197 ms

bootstrap.min.css

bootstrap.min.css

228 ms

ChatStyle.css

ChatStyle.css

190 ms

Chat.js

Chat.js

238 ms

hubs

hubs

236 ms

WebResource.axd

WebResource.axd

292 ms

ScriptResource.axd

ScriptResource.axd

246 ms

ScriptResource.axd

ScriptResource.axd

258 ms

ScriptResource.axd

ScriptResource.axd

299 ms

ScriptResource.axd

ScriptResource.axd

300 ms

ScriptResource.axd

ScriptResource.axd

301 ms

ScriptResource.axd

ScriptResource.axd

310 ms

ScriptResource.axd

ScriptResource.axd

323 ms

ScriptResource.axd

ScriptResource.axd

326 ms

ScriptResource.axd

ScriptResource.axd

326 ms

ScriptResource.axd

ScriptResource.axd

327 ms

ScriptResource.axd

ScriptResource.axd

328 ms

sdk.js

sdk.js

5 ms

header.png

header.png

299 ms

banner2.png

banner2.png

301 ms

banner3.png

banner3.png

303 ms

banner4.png

banner4.png

335 ms

logo.png

logo.png

205 ms

register.png

register.png

205 ms

imagesHidden.jpg

imagesHidden.jpg

207 ms

H000593_4_12_2015_2_33.jpeg

H000593_4_12_2015_2_33.jpeg

210 ms

WM_B000024_27_9_2015_8_7.jpeg

WM_B000024_27_9_2015_8_7.jpeg

299 ms

WM_H000590_14_9_2015_2_37.jpeg

WM_H000590_14_9_2015_2_37.jpeg

298 ms

WM_H000586_17_6_2015_5_31_1.jpeg

WM_H000586_17_6_2015_5_31_1.jpeg

330 ms

WM_H000582_10_6_2015_23_14.jpeg

WM_H000582_10_6_2015_23_14.jpeg

330 ms

WM_Honey11_16_5_2015_12_53_1.jpeg

WM_Honey11_16_5_2015_12_53_1.jpeg

331 ms

loader.gif

loader.gif

332 ms

malephoto.jpg

malephoto.jpg

343 ms

WM_H000579_13_5_2015_11_40_1.jpeg

WM_H000579_13_5_2015_11_40_1.jpeg

368 ms

testimonial.jpg

testimonial.jpg

384 ms

music(1)_03.png

music(1)_03.png

384 ms

music(1)_05.png

music(1)_05.png

385 ms

sdk.js

sdk.js

21 ms

87 ms

submit.png

submit.png

258 ms

shadow.png

shadow.png

271 ms

search_bg.png

search_bg.png

294 ms

sub.png

sub.png

305 ms

login_bg.png

login_bg.png

305 ms

h1_bg.png

h1_bg.png

309 ms

subm.png

subm.png

310 ms

online_now.jpg

online_now.jpg

326 ms

mobile_verified.jpg

mobile_verified.jpg

348 ms

email_verified.jpg

email_verified.jpg

370 ms

down.png

down.png

369 ms

smallborder.gif

smallborder.gif

371 ms

testi.png

testi.png

371 ms

foot_bg.png

foot_bg.png

482 ms

border.png

border.png

404 ms

Tangerine_Bold.ttf

Tangerine_Bold.ttf

354 ms

Tangerine_Regular.ttf

Tangerine_Regular.ttf

351 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

350 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

355 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

37 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

425 ms

analytics.js

analytics.js

32 ms

loading.gif

loading.gif

393 ms

113 ms

collect

collect

40 ms

collect

collect

39 ms

negotiate

negotiate

75 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

53 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

120 ms

Accessibility Review

searchandmarry.com accessibility score

53

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

searchandmarry.com best practices score

42

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

Prevents users to paste into password fields

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

SEO Factors

searchandmarry.com SEO score

58

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Searchandmarry.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Searchandmarry.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

searchandmarry.com

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