Page Authority Authority 46%

Moz Rank 3.4/10

Bounce Rate Rate 25%

Title Tag 61 Characters

Meta Description 0 Characters

Effective URL 16 Characters

Google Preview Your look like this in google search result

Robots.txt File No Found

http://taleo.net/robots.txt

Sitemap.xml File No Found

http://taleo.net/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Page Size Code & Text Ratio

Delicious Total: 0

Facebook Total: 167

Google Total: 0

Linkedin Total: 0

Pinterest Total: 13

Stumbleupon Total: 0

Tumblr Total: 0

Vk Total: 0

Google Stats This test checks to see if a page has applied common performance best practices.

Your page has no redirects. Learn more about avoiding landing page redirects.

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Your server responded quickly. Learn more about server response time optimization.

Your CSS is minified. Learn more about minifying CSS.

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Your page has 4 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Properly formatting and compressing images can save many bytes of data.

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Your page has no redirects. Learn more about avoiding landing page redirects.

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Your server responded quickly. Learn more about server response time optimization.

Your CSS is minified. Learn more about minifying CSS.

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Your page has 4 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Properly formatting and compressing images can save many bytes of data.

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Date: Wed, 09 May 2018 22:03:11 GMT
Server:  
Last-Modified: Fri, 19 Feb 2016 16:04:25 GMT
Accept-Ranges: bytes
Content-Length: 350
Content-Type: text/html

Response Server Information regarding a specific transfer

URL: http://taleo.net/
Content Type: text/html
Http Code: 200
Header Size: 181 B
Request Size: 71 B
Total Time: 0.286389 seconds
Name Lookup Time: 1.5E-5 seconds
Pretransfer Time: 0.142879 seconds
Download Size: 350 B
Speed Download: 350 B Per seconds
Start Trransfer Time: 0.28637 seconds