Tools & Wizards About Us
statsaboutme.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

statsaboutme.com

IIS Windows Server

Page Load Speed

4.7 sec in total

First Response

394 ms

Resources Loaded

3.9 sec

Page Rendered

345 ms

statsaboutme.com screenshot

About Website

Welcome to statsaboutme.com homepage info - get ready to check Statsaboutme best content right away, or after learning these important things about statsaboutme.com

Dream Big

Visit statsaboutme.com

Key Findings

We analyzed Statsaboutme.com page load time and found that the first response time was 394 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

statsaboutme.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

statsaboutme.com

394 ms

www.statsaboutme.com

1256 ms

www.onoko.com

585 ms

common.css

162 ms

onoko.css

116 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Statsaboutme.com, 23% (13 requests) were made to Onoko.com and 16% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Statsaboutme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.7 kB (18%)

Content Size

507.1 kB

After Optimization

414.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Statsaboutme.com main page is 507.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 399.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 21.8 kB

  • Original 29.7 kB
  • After minification 29.3 kB
  • After compression 7.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.8 kB or 73% of the original size.

Image Optimization

-6%

Potential reduce by 24.5 kB

  • Original 399.9 kB
  • After minification 375.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Statsaboutme images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 13.6 kB

  • Original 35.7 kB
  • After minification 32.5 kB
  • After compression 22.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 13.6 kB or 38% of the original size.

CSS Optimization

-78%

Potential reduce by 32.9 kB

  • Original 41.9 kB
  • After minification 32.5 kB
  • After compression 9.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Statsaboutme.com needs all CSS files to be minified and compressed as it can save up to 32.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (27%)

Requests Now

52

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Statsaboutme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

statsaboutme.com

statsaboutme.com

394 ms

www.statsaboutme.com

www.statsaboutme.com

1256 ms

www.onoko.com

www.onoko.com

585 ms

common.css

common.css

162 ms

onoko.css

onoko.css

116 ms

jquery.min.js

jquery.min.js

109 ms

common.js

common.js

911 ms

onthefly

onthefly

45 ms

onthefly

onthefly

109 ms

CebqPxucTC9211ko2YBFA.js

CebqPxucTC9211ko2YBFA.js

65 ms

ga.js

ga.js

65 ms

Mx-s7mIi1qD61YaPyiahl8205VBa0mfk5MSXHqsX8q1bAMg6TeC6-PdilhfOivtA_4_IuPkJJ6g6culQ2Wpz

Mx-s7mIi1qD61YaPyiahl8205VBa0mfk5MSXHqsX8q1bAMg6TeC6-PdilhfOivtA_4_IuPkJJ6g6culQ2Wpz

64 ms

459893_389441557753544_476334383_o.jpg

459893_389441557753544_476334383_o.jpg

134 ms

IM96teRgfEyJ_e0pEDuF4J3D3RBJ85mjxdiw72XnAcCOubGzY88B9mOMe7acIOVLOp2D7wHIRGNSJtIrlzI

IM96teRgfEyJ_e0pEDuF4J3D3RBJ85mjxdiw72XnAcCOubGzY88B9mOMe7acIOVLOp2D7wHIRGNSJtIrlzI

144 ms

safe_image.php

safe_image.php

348 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

56 ms

XeyxoftutAiQme80qtpP6SyKiBTXOjL0L2UGHyrkuPUKzlCMAtKsIh6Q4cyltl5S-42IK3enF5lgQOkVneM

XeyxoftutAiQme80qtpP6SyKiBTXOjL0L2UGHyrkuPUKzlCMAtKsIh6Q4cyltl5S-42IK3enF5lgQOkVneM

114 ms

background.png

background.png

126 ms

diagonal-bg.png

diagonal-bg.png

112 ms

seperator.png

seperator.png

132 ms

11951179_1008072855890408_1532429998225318049_n.png

11951179_1008072855890408_1532429998225318049_n.png

307 ms

11949458_1007542322610128_1507928644552688394_n.png

11949458_1007542322610128_1507928644552688394_n.png

225 ms

69025_473357556028610_2304296_n.jpg

69025_473357556028610_2304296_n.jpg

108 ms

309153_454530401244659_1891007621_n.jpg

309153_454530401244659_1891007621_n.jpg

111 ms

10462_453388694692163_315494036_n.jpg

10462_453388694692163_315494036_n.jpg

122 ms

582684_389441557753544_476334383_n.jpg

582684_389441557753544_476334383_n.jpg

130 ms

safe_image.php

safe_image.php

355 ms

safe_image.php

safe_image.php

361 ms

safe_image.php

safe_image.php

345 ms

446 ms

147 ms

feed.png

feed.png

182 ms

facebook.png

facebook.png

167 ms

twitter.png

twitter.png

220 ms

googleplus.png

googleplus.png

184 ms

appstore.png

appstore.png

182 ms

androidmarket.png

androidmarket.png

195 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

98 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

59 ms

__utm.gif

__utm.gif

32 ms

like.php

like.php

85 ms

60x60bb.jpg

60x60bb.jpg

123 ms

EzBbrksUJho1rsRtJM0q-ceo6h7is2PNJtEoYLQNQyEIIcCxRKD7W_GBUe59ZMZR_A=w300-rw

EzBbrksUJho1rsRtJM0q-ceo6h7is2PNJtEoYLQNQyEIIcCxRKD7W_GBUe59ZMZR_A=w300-rw

127 ms

tiCqcyMdmoooJpl2Or4pw5FAqevTWDaomeD3g2Ennpf_G5m4cSx610xWfN1XK-Vz7_8O=w300-rw

tiCqcyMdmoooJpl2Or4pw5FAqevTWDaomeD3g2Ennpf_G5m4cSx610xWfN1XK-Vz7_8O=w300-rw

101 ms

427321_453389081358791_466256220_n.jpg

427321_453389081358791_466256220_n.jpg

10 ms

427036_453388678025498_1960481126_n.jpg

427036_453388678025498_1960481126_n.jpg

8 ms

fy8tT2klpgR.js

fy8tT2klpgR.js

75 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

76 ms

common.css

common.css

83 ms

onoko.css

onoko.css

93 ms

all.js

all.js

18 ms

__utm.gif

__utm.gif

40 ms

track.js

track.js

167 ms

21 ms

xd_arbiter.php

xd_arbiter.php

28 ms

xd_arbiter.php

xd_arbiter.php

47 ms

xd_arbiter.php

xd_arbiter.php

23 ms

Accessibility Review

statsaboutme.com accessibility score

91

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

statsaboutme.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

statsaboutme.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Statsaboutme.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Statsaboutme.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

statsaboutme.com

Open Graph data is detected on the main page of Statsaboutme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: