Tools & Wizards About Us
intimatematrimonial.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

intimatematrimonial.com

Intimate Matrimony | Kerala Matrimony | No.1 Matrimony in Kerala | Free Matrimonial Websites in Kerala | Kerala Marriage Websites| Free Marriage Websi...

Page Load Speed

11.3 sec in total

First Response

98 ms

Resources Loaded

10.2 sec

Page Rendered

984 ms

intimatematrimonial.com screenshot

About Website

Visit intimatematrimonial.com now to see the best up-to-date Intimate Matrimonial content and also check out these interesting facts you probably never knew about intimatematrimonial.com

No.1 Matrimonials in Kerala | Intimate Matrimony, One of the best Matrimonials in all of Kerala. Find Lakhs of Kerala Brides and Grooms on the most trusted Matrimonials in Kerala.

Visit intimatematrimonial.com

Key Findings

We analyzed Intimatematrimonial.com page load time and found that the first response time was 98 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

intimatematrimonial.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value23.8 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.51

15/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

intimatematrimonial.com

98 ms

www.intimatematrimony.com

2239 ms

gtm.js

285 ms

bootstrap.min.css

282 ms

main.css

874 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Intimatematrimonial.com, 62% (73 requests) were made to Intimatematrimony.com and 7% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Intimatematrimony.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.5 kB (6%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intimatematrimonial.com main page is 2.8 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. 75% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 88.4 kB

  • Original 106.4 kB
  • After minification 92.0 kB
  • After compression 18.0 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 14.4 kB, which is 14% 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 88.4 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 14.8 kB

  • Original 2.3 MB
  • After minification 2.3 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. Intimate Matrimonial images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 43.0 kB

  • Original 206.2 kB
  • After minification 206.0 kB
  • After compression 163.2 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 43.0 kB or 21% of the original size.

CSS Optimization

-33%

Potential reduce by 31.4 kB

  • Original 95.3 kB
  • After minification 95.3 kB
  • After compression 63.9 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. Intimatematrimonial.com needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (63%)

Requests Now

110

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intimatematrimonial.com

intimatematrimonial.com

98 ms

www.intimatematrimony.com

www.intimatematrimony.com

2239 ms

gtm.js

gtm.js

285 ms

bootstrap.min.css

bootstrap.min.css

282 ms

main.css

main.css

874 ms

select2.css

select2.css

1095 ms

datetime.picker.css

datetime.picker.css

1073 ms

responsive.css

responsive.css

1322 ms

jquery-ui.min.css

jquery-ui.min.css

1081 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

412 ms

js

js

376 ms

amp-analytics-0.1.js

amp-analytics-0.1.js

475 ms

api:client.js

api:client.js

474 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1174 ms

accordion.min.js

accordion.min.js

1159 ms

datetime.picker.min.js

datetime.picker.min.js

2339 ms

select2.min.js

select2.min.js

2324 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

457 ms

jquery-ui.min.js

jquery-ui.min.js

2605 ms

custom.min.js

custom.min.js

1905 ms

jquery.unobtrusive-ajax.js

jquery.unobtrusive-ajax.js

1904 ms

jquery.validate.min.js

jquery.validate.min.js

2324 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

2323 ms

conversion_async.js

conversion_async.js

194 ms

hotjar-1994462.js

hotjar-1994462.js

209 ms

tfa.js

tfa.js

141 ms

json

json

76 ms

183 ms

modules.2be88a2123e5e486752f.js

modules.2be88a2123e5e486752f.js

108 ms

cds-pips.js

cds-pips.js

30 ms

166 ms

7d8if1zzog

7d8if1zzog

1192 ms

fbevents.js

fbevents.js

1102 ms

json

json

740 ms

tfa.js

tfa.js

739 ms

logo-white.png

logo-white.png

983 ms

logo-black.png

logo-black.png

984 ms

21-06-2021.jpg

21-06-2021.jpg

3327 ms

m3_16032022031002.jpg

m3_16032022031002.jpg

1070 ms

e65f0bea-3c60-428d-9802-799b252118f6_01012022034111.jpg

e65f0bea-3c60-428d-9802-799b252118f6_01012022034111.jpg

1069 ms

gs1.png

gs1.png

1071 ms

gs2.png

gs2.png

1071 ms

gs3.png

gs3.png

1068 ms

gs4.png

gs4.png

1931 ms

gs5.png

gs5.png

1931 ms

logo-transparent.png

logo-transparent.png

1914 ms

android.png

android.png

1917 ms

ios.png

ios.png

1914 ms

footer-logo.png

footer-logo.png

2236 ms

45nm78inee

45nm78inee

1029 ms

676 ms

578 ms

down-arrow.svg

down-arrow.svg

1556 ms

help.svg

help.svg

1558 ms

search-blue.svg

search-blue.svg

1557 ms

user-blue.svg

user-blue.svg

1552 ms

password.svg

password.svg

1811 ms

fb.png

fb.png

1813 ms

google.png

google.png

1782 ms

ham-blue.svg

ham-blue.svg

1783 ms

pen.svg

pen.svg

1806 ms

down-arrow-blue.svg

down-arrow-blue.svg

2020 ms

search-yellow.svg

search-yellow.svg

2021 ms

branch-locator.png

branch-locator.png

2054 ms

story-bg.jpg

story-bg.jpg

2518 ms

tick-multi.svg

tick-multi.svg

2054 ms

pen-yellow.svg

pen-yellow.svg

2283 ms

featured-before.jpg

featured-before.jpg

2285 ms

royal-bg.jpg

royal-bg.jpg

2286 ms

diadem.png

diadem.png

2308 ms

step-right.png

step-right.png

2499 ms

caste-before.jpg

caste-before.jpg

2499 ms

reply-right.svg

reply-right.svg

2480 ms

about-bg.jpg

about-bg.jpg

2281 ms

about1.png

about1.png

2446 ms

about2.png

about2.png

2448 ms

panorama.js

panorama.js

57 ms

913 ms

893 ms

188587738521821

188587738521821

1191 ms

SourceSansPro-Regular.ttf

SourceSansPro-Regular.ttf

2945 ms

SourceSansPro-Light.ttf

SourceSansPro-Light.ttf

2661 ms

SourceSansPro-Bold.ttf

SourceSansPro-Bold.ttf

3079 ms

about3.png

about3.png

2489 ms

about4.png

about4.png

2602 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

725 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

717 ms

1fe3g9df2

1fe3g9df2

1231 ms

clarity.js

clarity.js

253 ms

sync.min.js

sync.min.js

514 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

566 ms

231 ms

premium1.svg

premium1.svg

1745 ms

premium2.svg

premium2.svg

2061 ms

premium3.svg

premium3.svg

2078 ms

premium4.svg

premium4.svg

2079 ms

right-arrow.svg

right-arrow.svg

2052 ms

iframe

iframe

346 ms

fb.svg

fb.svg

1895 ms

in.svg

in.svg

1898 ms

tw.svg

tw.svg

1900 ms

yt.svg

yt.svg

2041 ms

pn.svg

pn.svg

2089 ms

map

map

142 ms

bl.svg

bl.svg

1882 ms

totop.svg

totop.svg

1861 ms

cspreport

cspreport

44 ms

Intimate_Onam_Popup_05092022.png

Intimate_Onam_Popup_05092022.png

3275 ms

circle-filled.svg

circle-filled.svg

1888 ms

twk-event-polyfill.js

twk-event-polyfill.js

92 ms

twk-main.js

twk-main.js

65 ms

twk-vendor.js

twk-vendor.js

66 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

161 ms

twk-chunk-common.js

twk-chunk-common.js

160 ms

twk-runtime.js

twk-runtime.js

155 ms

twk-app.js

twk-app.js

122 ms

c.gif

c.gif

48 ms

Accessibility Review

intimatematrimonial.com accessibility score

77

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

intimatematrimonial.com best practices score

67

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

intimatematrimonial.com SEO score

91

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

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

intimatematrimonial.com

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