2.2 sec in total
96 ms
1.9 sec
187 ms
Welcome to oriyamatrimonials.com homepage info - get ready to check Oriyamatrimonials best content for India right away, or after learning these important things about oriyamatrimonials.com
Visit oriyamatrimonials.comWe analyzed Oriyamatrimonials.com page load time and found that the first response time was 96 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 40% of websites can load faster.
oriyamatrimonials.com performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.1 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.0 s
100/100
10%
96 ms
263 ms
70 ms
51 ms
48 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original Oriyamatrimonials.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (856 ms) belongs to the original domain Oriyamatrimonials.com.
Page size can be reduced by 170.3 kB (26%)
659.1 kB
488.8 kB
In fact, the total size of Oriyamatrimonials.com main page is 659.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 457.6 kB which makes up the majority of the site volume.
Potential reduce by 36.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 8.9 kB, which is 20% 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 36.9 kB or 84% of the original size.
Potential reduce by 19.8 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. Oriyamatrimonials images are well optimized though.
Potential reduce by 82.6 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 82.6 kB or 69% of the original size.
Potential reduce by 31.1 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. Oriyamatrimonials.com needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 83% of the original size.
Number of requests can be reduced by 19 (35%)
55
36
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oriyamatrimonials. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
oriyamatrimonials.com
96 ms
index.pl
263 ms
basestyles.css
70 ms
home.css
51 ms
memberInput.js
48 ms
help.js
51 ms
matrimQuickSearchCheck.js
51 ms
getCastes.js
48 ms
matrimajaxCastes.js
71 ms
utils.js
71 ms
selectPopulate.js
70 ms
slideshow.css
71 ms
jquery.min.js
64 ms
jquery.cycle.js
92 ms
slideshow.js
86 ms
home-supp.css
93 ms
mainmenu.css
94 ms
default.css
93 ms
nivo-slider.css
94 ms
style.css
105 ms
jquery.nivo.slider.js
141 ms
wz_tooltip.js
146 ms
ga.js
25 ms
__utm.gif
97 ms
showImage.pl
438 ms
bg.jpg
77 ms
floral_embellish.jpg
81 ms
top-bg.png
78 ms
rfree.jpg
78 ms
frame-bg.jpg
77 ms
discount.png
79 ms
loading.gif
80 ms
ss1.jpg
90 ms
ss2.jpg
89 ms
ss3.jpg
94 ms
red-couple.jpg
95 ms
bottom-bg.png
79 ms
trans.png
80 ms
displayImage.pl
438 ms
displayImage.pl
402 ms
displayImage.pl
449 ms
displayImage.pl
461 ms
displayImage.pl
518 ms
displayImage.pl
425 ms
displayImage.pl
770 ms
displayImage.pl
769 ms
displayImage.pl
723 ms
displayImage.pl
738 ms
displayImage.pl
777 ms
displayImage.pl
856 ms
rashmi200x40.jpg
772 ms
freebenefits.jpg
734 ms
privben.jpg
743 ms
fullbenefits.jpg
744 ms
arrows.png
24 ms
bullets.png
23 ms
index.pl
252 ms
oriyamatrimonials.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
oriyamatrimonials.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
oriyamatrimonials.com SEO score
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
Document uses legible font sizes
ZH
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oriyamatrimonials.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Oriyamatrimonials.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
oriyamatrimonials.com
Open Graph description is not detected on the main page of Oriyamatrimonials. 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: