15.5 sec in total
129 ms
14 sec
1.4 sec
Visit sweethomemarriage.com now to see the best up-to-date Sweet Home Marriage content and also check out these interesting facts you probably never knew about sweethomemarriage.com
One of India's best known brands and the world's largest matrimonial service was founded with a simple objective - to help people find happiness. The company pioneered online matrimonial in and contin...
Visit sweethomemarriage.comWe analyzed Sweethomemarriage.com page load time and found that the first response time was 129 ms and then it took 15.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sweethomemarriage.com performance score
129 ms
1567 ms
253 ms
487 ms
695 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sweethomemarriage.com, 98% (174 requests) were made to Sweethomemarriage.in and 1% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Sweethomemarriage.in.
Page size can be reduced by 6.8 MB (16%)
42.6 MB
35.8 MB
In fact, the total size of Sweethomemarriage.com main page is 42.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 42.2 MB which makes up the majority of the site volume.
Potential reduce by 293.3 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 138.3 kB, which is 43% 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 293.3 kB or 92% of the original size.
Potential reduce by 6.5 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. Obviously, Sweet Home Marriage needs image optimization as it can save up to 6.5 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 716 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Sweethomemarriage.com needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 13% of the original size.
Number of requests can be reduced by 6 (3%)
175
169
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweet Home Marriage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
sweethomemarriage.com
129 ms
www.sweethomemarriage.in
1567 ms
bootstrap.css
253 ms
newstyle.css
487 ms
jquery.min.js
695 ms
jquery-1.10.2.min.js
37 ms
owl.carousel.min.js
722 ms
bootstrap.min.js
726 ms
holder.js
780 ms
all.js
152 ms
1498287718-logo.png
322 ms
banner_new1.png
1522 ms
banner_new2.png
2261 ms
banner_new3.png
2464 ms
banner_new4.png
945 ms
banner-bottom.png
529 ms
watermark.php
1048 ms
watermark.php
1756 ms
watermark.php
1699 ms
watermark.php
2544 ms
watermark.php
1788 ms
watermark.php
1955 ms
watermark.php
2518 ms
watermark.php
2051 ms
watermark.php
2456 ms
watermark.php
2572 ms
watermark.php
3219 ms
photo-protected-female.png
2697 ms
watermark.php
2701 ms
watermark.php
2773 ms
watermark.php
3297 ms
watermark.php
3089 ms
watermark.php
2967 ms
watermark.php
3183 ms
watermark.php
3282 ms
watermark.php
3470 ms
male-200.png
3333 ms
watermark.php
3422 ms
watermark.php
3702 ms
watermark.php
3533 ms
watermark.php
3557 ms
watermark.php
3848 ms
all.js
6 ms
glyphicons-halflings-regular.woff
3422 ms
watermark.php
3740 ms
watermark.php
3558 ms
watermark.php
3752 ms
watermark.php
3813 ms
watermark.php
4452 ms
watermark.php
3617 ms
watermark.php
3348 ms
watermark.php
2704 ms
watermark.php
2640 ms
watermark.php
3114 ms
photo-protected-male100.png
2673 ms
watermark.php
2636 ms
watermark.php
2638 ms
watermark.php
2461 ms
watermark.php
2364 ms
watermark.php
2642 ms
female-200.png
2424 ms
watermark.php
2927 ms
watermark.php
2510 ms
watermark.php
2417 ms
watermark.php
2511 ms
watermark.php
2456 ms
watermark.php
2366 ms
watermark.php
2530 ms
watermark.php
2444 ms
watermark.php
2271 ms
watermark.php
2709 ms
watermark.php
2556 ms
watermark.php
2385 ms
watermark.php
2346 ms
watermark.php
2674 ms
watermark.php
2619 ms
watermark.php
2419 ms
watermark.php
2382 ms
watermark.php
3425 ms
watermark.php
2716 ms
watermark.php
2409 ms
watermark.php
2361 ms
watermark.php
2615 ms
watermark.php
2308 ms
watermark.php
2313 ms
watermark.php
2248 ms
watermark.php
2548 ms
watermark.php
2295 ms
watermark.php
2238 ms
watermark.php
2272 ms
watermark.php
2502 ms
watermark.php
2545 ms
watermark.php
2491 ms
watermark.php
2254 ms
watermark.php
2486 ms
watermark.php
2434 ms
watermark.php
2574 ms
watermark.php
2350 ms
watermark.php
2400 ms
watermark.php
2342 ms
watermark.php
2470 ms
watermark.php
2620 ms
watermark.php
2246 ms
watermark.php
2275 ms
watermark.php
2175 ms
watermark.php
2284 ms
watermark.php
2294 ms
watermark.php
2483 ms
watermark.php
2170 ms
watermark.php
2083 ms
watermark.php
2183 ms
watermark.php
2166 ms
watermark.php
2191 ms
watermark.php
2675 ms
watermark.php
2078 ms
watermark.php
2107 ms
watermark.php
2011 ms
watermark.php
2262 ms
watermark.php
2084 ms
watermark.php
2040 ms
watermark.php
2609 ms
watermark.php
2002 ms
watermark.php
2100 ms
watermark.php
1999 ms
watermark.php
2086 ms
watermark.php
2442 ms
watermark.php
1970 ms
watermark.php
1918 ms
watermark.php
2185 ms
watermark.php
1970 ms
watermark.php
1969 ms
watermark.php
1946 ms
watermark.php
2108 ms
watermark.php
2063 ms
watermark.php
2056 ms
watermark.php
1976 ms
watermark.php
2012 ms
watermark.php
2101 ms
watermark.php
2359 ms
watermark.php
2054 ms
watermark.php
2258 ms
watermark.php
1992 ms
watermark.php
1976 ms
watermark.php
2047 ms
watermark.php
2054 ms
watermark.php
2285 ms
watermark.php
2315 ms
watermark.php
2078 ms
watermark.php
2042 ms
watermark.php
2036 ms
watermark.php
1974 ms
watermark.php
2128 ms
watermark.php
2093 ms
watermark.php
2067 ms
watermark.php
1956 ms
watermark.php
1978 ms
watermark.php
1960 ms
watermark.php
1964 ms
watermark.php
2061 ms
watermark.php
1964 ms
watermark.php
1868 ms
watermark.php
1900 ms
watermark.php
1778 ms
watermark.php
2050 ms
watermark.php
1866 ms
watermark.php
1868 ms
watermark.php
1870 ms
watermark.php
1979 ms
watermark.php
1829 ms
watermark.php
1969 ms
watermark.php
1900 ms
watermark.php
1973 ms
watermark.php
1892 ms
facebook.png
1793 ms
twitter.png
1912 ms
gplus.jpg
1828 ms
index_download_btn_arrow.png
1792 ms
social-media2.png
1758 ms
sweethomemarriage.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweethomemarriage.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 Sweethomemarriage.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.
sweethomemarriage.com
Open Graph description is not detected on the main page of Sweet Home Marriage. 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: