Website SEO Analysis
In-Depth

Detailed Website Analysis

The basic overview not enough? Let's dive deeper.

matrimonialcounsellor.com Data In-Depth

A website is not just Quantcast ranks and meta information. There is a whole lot more to it. Let's give it a proper look now, shall we?

Page speed overview

• It takes around 1.1891 seconds for the homepage to fully load. This is a very good result, as search engines prioritize websites that are quick to load.
• It's worth to note the HTML of the page is around 68.4 kilobytes in size. A good result that should not impact load speed in any negative way.
• Judging by tags, the homepage contains at least 12 images. A great amount! Not too many, at least. Images should not impact page load speed negatively.
• Our database tells us around 36 server requests are made before the homepage is loaded completely. This is a pleasingly low number of server requests and adds to the improvement of website load speed.

Host Server In-Depth

What is a server? It's basically a physical storage device (one that, sometimes, makes up several virtual servers for the cheaper shared hosting) that holds all the files and databases associated with a specific website or websites. Obviously, it's a touch more complicated than that (servers also have processors), but the essence is quite simple - your browser contacts the server, which then sends all the neccessary information and files to your computer. Each physical server has a unique IP address assigned to it, too, for easy recognition.

• The current IP address for this website's server is 103.53.40.92.
• Server seems to be online.

HTTP header and raw WHOIS entry

If you need more raw data, here's what we managed to gather:

HTTP/1.1 200 OK
Date: Sun, 19 Nov 2017 18:45:55 GMT
Server: Apache Phusion_Passenger/4.0.10 mod_bwlimited/1.4
X-Powered-By: PHP/5.6.31
Link: <http://matrimonialcounsellor.com/wp-json/>; rel="https://api.w.org/"
Set-Cookie: wfvt_1250332299=5a11d163c8d82; expires=Sun, 19-Nov-2017 19:15:55 GMT; Max-Age=1800; path=/; httponly
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8