Tools & Wizards About Us
2012.ws screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

4.3 sec in total

First Response

228 ms

Resources Loaded

3.9 sec

Page Rendered

211 ms

2012.ws screenshot

About Website

Click here to check amazing 2012 content. Otherwise, check out these important facts you probably never knew about 2012.ws

Visit 2012.ws

Key Findings

We analyzed 2012.ws page load time and found that the first response time was 228 ms and then it took 4.1 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

2012.ws performance score

0

Network Requests Diagram

2012.ws

228 ms

index.dhtml

2614 ms

all.min.css

206 ms

coinmill.js

269 ms

all.min.js

610 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original 2012.ws, 87% (20 requests) were made to Worldsite.ws and 9% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Worldsite.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.1 kB (39%)

Content Size

292.5 kB

After Optimization

179.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2012.ws main page is 292.5 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. 20% of websites need less resources to load. Images take 143.1 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 294 B

  • Original 575 B
  • After minification 569 B
  • After compression 281 B

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 294 B or 51% of the original size.

Image Optimization

-6%

Potential reduce by 9.1 kB

  • Original 143.1 kB
  • After minification 134.0 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. 2012 images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 4.4 kB

  • Original 25.0 kB
  • After minification 25.0 kB
  • After compression 20.6 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 4.4 kB or 18% of the original size.

CSS Optimization

-80%

Potential reduce by 99.3 kB

  • Original 123.8 kB
  • After minification 123.8 kB
  • After compression 24.5 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. 2012.ws needs all CSS files to be minified and compressed as it can save up to 99.3 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2012. According to our analytics all requests are already optimized.

Network Requests Diagram

2012.ws

2012.ws

228 ms

index.dhtml

index.dhtml

2614 ms

all.min.css

all.min.css

206 ms

coinmill.js

coinmill.js

269 ms

all.min.js

all.min.js

610 ms

main-bg.gif

main-bg.gif

79 ms

main-header-bg.jpg

main-header-bg.jpg

270 ms

main-logo.png

main-logo.png

78 ms

global-nav-bg.png

global-nav-bg.png

147 ms

global-nav-sep.png

global-nav-sep.png

144 ms

video.jpg

video.jpg

408 ms

loader-inner.gif

loader-inner.gif

277 ms

logo-inc500.png

logo-inc500.png

279 ms

logo-dsa.png

logo-dsa.png

212 ms

premium-logo.png

premium-logo.png

213 ms

check-premium.png

check-premium.png

280 ms

ico-cart.png

ico-cart.png

271 ms

langs.png

langs.png

392 ms

btn-norm.png

btn-norm.png

333 ms

price-t-h.png

price-t-h.png

333 ms

ga.js

ga.js

44 ms

btn-cur-symbols.png

btn-cur-symbols.png

271 ms

__utm.gif

__utm.gif

11 ms

SEO Factors

2012.ws SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2012.ws 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 2012.ws main page’s claimed encoding is iso-8859-1. 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

2012.ws

Open Graph description is not detected on the main page of 2012. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: