Page Authority Authority 79%

Moz Rank 6.1/10

Bounce Rate Rate 28%

Charset Encoding

Title Tag 59 Characters

Meta Description 156 Characters

Effective URL 20 Characters

Excerpt Page content

Meta Keywords 7 Detected

nazwa.pl najlepszy hosting rejestracja domen darmowe strony WWW certyfikaty ssl profesjonalna poczta sklepy internetowe

Google Preview Your look like this in google search result

Robots.txt File Detected

http://nazwa.pl/robots.txt

Sitemap.xml File Detected

http://nazwa.pl/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: 2

Facebook Total: 2,574

Google Total: 0

Linkedin Total: 0

Pinterest Total: 0

Stumbleupon Total: 1

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.

Compacting CSS code can save many bytes of data and speed up download and parse times.

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

Compacting CSS code can save many bytes of data and speed up download and parse times.

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 25 blocking script resources and 11 blocking CSS resources. This causes a delay in rendering your page.

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

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold 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
Server: nginx
Date: Wed, 02 May 2018 04:01:28 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 67875
Connection: keep-alive
Content-Language: pl
Expires: Wed, 02 May 2018 12:08:22 GMT
ETag: "73cd2cf8759732d76a1b5965a36654d1"
Cache-Control: max-age=86400
Pragma: public
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Lbl: 4
Accept-Ranges: bytes
Age: 57186
X-Cache: HIT
Set-Cookie: sticky=71789859.377_185.13.5.47; path=/; HttpOnly

Response Server Information regarding a specific transfer

URL: https://www.nazwa.pl/
Content Type: text/html; charset=utf-8
Http Code: 200
Header Size: 491 B
Request Size: 74 B
Total Time: 0.155488 seconds
Name Lookup Time: 1.3E-5 seconds
Pretransfer Time: 0.092371 seconds
Download Size: 66.28 KB
Speed Download: 66.28 KB Per seconds
Start Trransfer Time: 0.134483 seconds