<p>That kind of site is called a "SCRAPER."  It's great that you brought it to our attention.  It is spoofing the entirety of SE, not just stats.  (I investigated using a browser in a virtual machine.)  The recommended response is described in two answers to the meta SO post <a href="https://meta.stackexchange.com/questions/200177/updated-procedure-for-reporting-scrapers">A site (or scraper) is copying content from Stack Exchange. What do I do?</a>.  Briefly,</p>

<blockquote>
  <p>Send all reports of SCRAPERs to us via the form on the contact us page, linked at the bottom of every page.</p>
  
  <p>Use the "Other" reason on the form (fortunately, we don't get enough of these reports to justify making SCRAPERs their own category/reason). Please include:</p>
  
  <ul>
  <li><p>the URL of the copied post</p></li>
  <li><p>the URL of the original post on SE</p></li>
  <li><p>for high-rankers, the search string you used (and the name of the search engine, if not Google)</p></li>
  <li><p>any other details you noticed and want to share, because you're awesome</p></li>
  </ul>
</blockquote>

<p>and</p>

<blockquote>
  <p>If you see a scraper URL outranking the original source of content in Google, please tell us about it: <a href="http://bit.ly/scraperspamreport" rel="nofollow noreferrer">http://bit.ly/scraperspamreport</a></p>
</blockquote>

<p>I haven't seen the latter, so I haven't reported to Google, but I did contact the SE team with this info.</p>

<h2>Update</h2>

<p>I have received these messages from the SE team and want to reproduce them here because their thanks really apply to the OP and everyone else reading this thread and helping out.</p>

<h3>Message 1</h3>

<blockquote>
  <p>Thank you for reporting this content. I've passed the information along to the person at our company who handles such issues. It's the diligence of users like you that helps us stay valuable!</p>
  
  <p>Please note, bringing these sites into compliance (or getting them to no longer serve our content) is often a long and arduous process. You may not see immediate results. However, rest assured that we're working on it.</p>
</blockquote>

<h3>Message 2</h3>

<blockquote>
  <p>I checked with our network engineers and they blocked the IP that was proxying our sites. Anything they haven't cached already will show a CloudFlare error.</p>
  
  <p>Thanks for the report,</p>
  
  <p>The Stack Exchange Team</p>
</blockquote>
