Tools & Wizards About Us
simplymarry.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

21.7 sec in total

First Response

596 ms

Resources Loaded

14.2 sec

Page Rendered

6.9 sec

simplymarry.com screenshot

About Website

Visit simplymarry.com now to see the best up-to-date Simplymarry content for India and also check out these interesting facts you probably never knew about simplymarry.com

Visit simplymarry.com

Key Findings

We analyzed Simplymarry.com page load time and found that the first response time was 596 ms and then it took 21.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

simplymarry.com performance score

0

Network Requests Diagram

simplymarry.com

596 ms

www.simplymarry.com

2500 ms

common_sm.css

894 ms

public.css

877 ms

anythingslider.css

1240 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 79% of them (46 requests) were addressed to the original Simplymarry.com, 5% (3 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Simplymarry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (45%)

Content Size

2.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 80.3 kB

  • Original 98.2 kB
  • After minification 82.7 kB
  • After compression 17.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 15.5 kB, which is 16% 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 80.3 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 40.9 kB

  • Original 1.2 MB
  • After minification 1.1 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. Simplymarry images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 506.5 kB

  • Original 706.9 kB
  • After minification 631.0 kB
  • After compression 200.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 506.5 kB or 72% of the original size.

CSS Optimization

-88%

Potential reduce by 552.2 kB

  • Original 627.0 kB
  • After minification 603.6 kB
  • After compression 74.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. Simplymarry.com needs all CSS files to be minified and compressed as it can save up to 552.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

simplymarry.com

simplymarry.com

596 ms

www.simplymarry.com

www.simplymarry.com

2500 ms

common_sm.css

common_sm.css

894 ms

public.css

public.css

877 ms

anythingslider.css

anythingslider.css

1240 ms

anythingslider-ie.css

anythingslider-ie.css

622 ms

jquery-1.9.0.js

jquery-1.9.0.js

374 ms

jquery-migrate-1.0.0.js

jquery-migrate-1.0.0.js

206 ms

nyroModal.css

nyroModal.css

632 ms

all_popups.css

all_popups.css

1870 ms

jquery.nyroModal.custom.js

jquery.nyroModal.custom.js

1965 ms

jquery.validate.min.js

jquery.validate.min.js

1869 ms

jquery.anythingslider.min.js

jquery.anythingslider.min.js

1869 ms

application.js

application.js

1931 ms

newsmhome.css

newsmhome.css

2378 ms

new-sm-style.css

new-sm-style.css

2497 ms

feedback.js

feedback.js

2497 ms

aa.js

aa.js

2088 ms

conversion.js

conversion.js

1885 ms

dc.js

dc.js

1665 ms

beacon.js

beacon.js

1666 ms

ie_safari_browser.png

ie_safari_browser.png

2812 ms

ie_mozilla_browser.png

ie_mozilla_browser.png

2528 ms

ie_chrome_browser.png

ie_chrome_browser.png

2254 ms

ie_opera_browser.png

ie_opera_browser.png

1799 ms

ie_internet_browser.png

ie_internet_browser.png

2253 ms

ie_close_div.png

ie_close_div.png

1798 ms

soulmate-logo.png

soulmate-logo.png

2253 ms

register-mbl.png

register-mbl.png

1658 ms

login-mbl.png

login-mbl.png

1446 ms

smnw-lg.jpg

smnw-lg.jpg

1447 ms

smnw-hpimg.jpg

smnw-hpimg.jpg

2920 ms

new-sm-round2.png

new-sm-round2.png

2910 ms

new-sm-srch-btn.jpg

new-sm-srch-btn.jpg

2919 ms

sunita-dhirendra.jpg

sunita-dhirendra.jpg

2919 ms

new-sm-ar.png

new-sm-ar.png

3797 ms

pooja-deepak.jpg

pooja-deepak.jpg

5160 ms

amruta-rahul.jpg

amruta-rahul.jpg

4489 ms

kamini-dharam.jpg

kamini-dharam.jpg

5119 ms

radha-himanshu.jpg

radha-himanshu.jpg

3753 ms

smgpls-new.png

smgpls-new.png

2934 ms

smwrdp-new.png

smwrdp-new.png

3752 ms

smtwtr-new.png

smtwtr-new.png

3755 ms

smfcbk-new.png

smfcbk-new.png

3787 ms

google-play-btn.png

google-play-btn.png

4448 ms

sm-hp-sprite.png

sm-hp-sprite.png

4150 ms

new-sm-img1.jpg

new-sm-img1.jpg

3634 ms

new-sm-img2.jpg

new-sm-img2.jpg

4149 ms

__utm.gif

__utm.gif

235 ms

ga-audiences

ga-audiences

1530 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

5546 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

5512 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

5545 ms

nsm_newddselect.png

nsm_newddselect.png

2300 ms

message

message

968 ms

732 ms

__utm.gif

__utm.gif

59 ms

92 ms

SEO Factors

simplymarry.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simplymarry.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Simplymarry.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

simplymarry.com

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