Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | Build.com Smarter Home Improvement - Plumbing, Lighting, HVAC, Door Hardware & More | Search engines recommend title length of around 50-60 characters. The length of this title is 83. |
Meta description | Huge Savings on over 500,000 Home Improvement products, Knowledgeable Customer Service 7 Days a Week, and FREE shipping offers on Faucets, Lighting, Door Hardware, Venting, Appliances, and much more. | To make sure all the meta description is visible in search results page, Google recommends length of up to 320 characters at the most. This description has exactly 199 characters. |
Load time | 1.6683 seconds on average | Load speed is a concern and should be improved if and when possible. |
Total links on homepage | We found 410 links | Honestly, this is a strange amount of links for a homepage. |
Page HTML size | 168KB | How do we put this... improvement is quite necessary. Load speed is a very important factor in so many ways! |
Website server | Server appears to be online. The IP address for the server is 151.101.113.23. | It's unfortunate, but despite our best attempts, we failed to gather enough data to provide a meaningful insight at this time. |
What, all that information was not enough? You want... more? Right, then. You asked for it.
Similarly to how a hard drive or a modern SSD device holds your files, a server holds all the files the website needs to operate. To load a webpage, your browser needs to contact the said server and request files - strings of code that make up the website into what it is, including images, text and database entries. Each physical server has a unique IP address that is used by the browser to contact it.
Let's see what technical information we've managed to gather:
Header in detail |
---|
HTTP/1.1 200 OK Server: nginx Set-Cookie: abEnableVizury=true; path=/; domain=.build.com; expires=Sun, 19-Nov-2017 13:50:10 GMT Set-Cookie: SSLB_S=1; path=/; domain=.build.com; expires=Tue, 19-Dec-2017 13:25:10 GMT Set-Cookie: SSID=CAATxh0cAAAAAAAKhRFayWJCGwqFEVoBAAAAAAA2EzlaCoURWgAutbGAAANmpw4ACoURWgEA7H8AAxqcDgAKhRFaAQA; path=/; domain=.build.com; expires=Mon, 19-Nov-2018 13:20:10 GMT Set-Cookie: SSSC=322.G6490114816471098057.1|32748.957466:32945.960358; path=/; domain=.build.com Set-Cookie: SSRT=CoURWgIBAQ; path=/; domain=.build.com; expires=Mon, 19-Nov-2018 13:20:10 GMT Set-Cookie: SSOD=0; path=/; domain=.build.com; expires=Thu, 01-Jan-1970 00:00:00 GMT RTSS: 1-2-109 VFC: S Content-Type: text/html; charset=utf-8 X-DPT: Sunday, 19-Nov-2017 13:20:10 GMT X-Powered-By: Build.com x-xss-protection: 1; mode=block Cache-Control: private, max-age=0, proxy-revalidate, no-store, no-cache, must-revalidate x-ruta-top_app_priority: 251 x-ruta-top_app: nodestore Content-Security-Policy-Report-Only: default-src https:; connect-src https:; font-src https: data:; frame-src https:; img-src https: data:; media-src https:; object-src https:; script-src 'unsafe-inline' 'unsafe-eval' https:; style-src 'unsafe-inline' https:; report-uri /app/api/cspViolation; Timing-Allow-Origin: * Accept-Ranges: bytes Via: 1.1 varnish Age: 0 x-host-original: fastly-www.build.com x-host-postregsub: www.build.com x-reqbackend: shield__cache_ord1725_ORD__ord_il_us Pragma: no-cache Expires: Mon, 22 May 2017 22:26:41 GMT Set-Cookie: CID=bdf7b4e403bb41c2a5c6634be145ded5; Max-Age=315360000; Path=/; Expires=Wed, 17 Nov 2027 13:20:10 GMT; HttpOnly;Secure Transfer-Encoding: chunked Accept-Ranges: bytes Date: Sun, 19 Nov 2017 13:20:10 GMT Via: 1.1 varnish Connection: keep-alive X-UUID: f11b8b644c46eb6fd936926c5c41e184d1e02a87 X-UA-Device: desktop x-blacklist: x-host: fastly-www.build.com X-Served-By: cache-ord1725-ORD, cache-hhn1551-HHN X-Cache: MISS, MISS X-Cache-Hits: 0, 0 X-Timer: S1511097610.001703,VS0,VE639 Vary: Accept-Encoding,User-Agent |
A good domain address is usually one that is easy to spell, resulting in the smallest amount of mistypes possible. Still, such a thing inevitably happens. Here is a list with the most frequent 1743 mistypes, associated with rugshowplace.com:
If you are curious about what TLD extensions could also match the domain name of rugshowplace.com well, we have prepared an extensive list for you to look through:
We are glad you have finished this report. Hopefully, you found what you were looking for. In case you need more information to compare, here is a list of some other detailed overviews we have prepared: