Site Performance and Stats
In Detail

Website Performance – The Geeky Part

What, all that information was not enough? You want... more? Right, then. You asked for it.

games.espn.com In Detail

As we've mentioned before, traffic is not a key metric. However, the target audience does say a lot about what's been done to optimize the website, as well as what should be done going forwards. Let's see if we have any useful information here.

games.espn.com Visitor Information

Absolute accuracy is accessible only by the webmasters. If you keep that in mind, perhaps you will find out approximate numbers of some use.
Where appropriate, we'll add an insight, but the numbers themselves speak clearly enough, eh?

Website load speed analysis

• The homepage takes approximately 1.4398 seconds to load. Load speed (and overall responsiveness) is such an important factor for both search engines and user experience, would you not agree? With that in mind, this is a very good result.
• The HTML of the website weighs in at around 157.1 kilobytes. We don't think 157.1 KBs is something to worry about.
• There are at least 3 images on the homepage of this website. We are glad to say that such an amount should not impact the load speed of the website. Great result!
• We've counted at least 77 server requests before the homepage was fully loaded. Oh my, this needs to be worked on. The more server requests are made, the longer it takes to load the page. Not a good result by any measure.

Detailed Host Server Information

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.

• The website's server IP address is 54.72.7.190.
• Server appears to be online.

HTTP header and WHOIS information

Let's see what technical information we've managed to gather:

HTTP/1.1 200 OK
Date: Fri, 27 Oct 2017 16:03:10 GMT
Content-Type: text/html;charset=UTF-8
Connection: close
X-Application-Context: sCoreTc:AWS:8080
Access-Control-Allow-Origin: *
X-UA-Compatible: IE=Edge
ETag: W/"6ef6e078141c279e2e04ae5511d93640b2706c7f"
X-Varnish-Backend: sCoreTc
X-Age: 0
x-chained-ha-request: yes
Vary: Accept-Encoding
Accept-Ranges: bytes
Cache-Control: max-age=0, must-revalidate
Set-Cookie: SWID=1C83AB52-D3F1-4B07-CBF4-6CA8460657F0; path=/; Expires=Tue, 27 Oct 2037 16:03:10 GMT; domain=espn.com;
Set-Cookie: connectionspeed=full; path=/; Expires=Fri, 03 Nov 2017 16:03:10 GMT;
Set-Cookie: edition-view=espn-en-us; path=/; Expires=Fri, 03 Nov 2017 16:03:10 GMT;
Set-Cookie: country=de; path=/;
Set-Cookie: edition=espn-en-us; path=/; Expires=Fri, 03 Nov 2017 16:03:10 GMT;