Tools & Wizards About Us
ecso.ws screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ecso.ws

ecso.ws

Page Load Speed

1.5 sec in total

First Response

220 ms

Resources Loaded

1.1 sec

Page Rendered

171 ms

ecso.ws screenshot

About Website

Welcome to ecso.ws homepage info - get ready to check Ecso best content right away, or after learning these important things about ecso.ws

Forsale Lander

Visit ecso.ws

Key Findings

We analyzed Ecso.ws page load time and found that the first response time was 220 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

ecso.ws performance score

0

Network Requests Diagram

ecso.ws

220 ms

construct.dhtml

281 ms

layout.css

177 ms

jquery-1.3.2.min.js

341 ms

tools.tabs-1.0.4.min.js

137 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ecso.ws, 93% (27 requests) were made to Website.ws and 3% (1 request) were made to My.ws. The less responsive or slowest element that took the longest time to load (341 ms) relates to the external source Website.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.0 kB (43%)

Content Size

286.5 kB

After Optimization

164.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ecso.ws main page is 286.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. Only 10% of websites need less resources to load. Javascripts take 145.9 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 260 B

  • Original 527 B
  • After minification 521 B
  • After compression 267 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 260 B or 49% of the original size.

Image Optimization

-19%

Potential reduce by 25.1 kB

  • Original 131.8 kB
  • After minification 106.7 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. Obviously, Ecso needs image optimization as it can save up to 25.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 95.4 kB

  • Original 145.9 kB
  • After minification 136.6 kB
  • After compression 50.5 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 95.4 kB or 65% of the original size.

CSS Optimization

-15%

Potential reduce by 1.2 kB

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

Requests Breakdown

Number of requests can be reduced by 8 (30%)

Requests Now

27

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecso.ws

ecso.ws

220 ms

construct.dhtml

construct.dhtml

281 ms

layout.css

layout.css

177 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

341 ms

tools.tabs-1.0.4.min.js

tools.tabs-1.0.4.min.js

137 ms

cufon-yui.js

cufon-yui.js

273 ms

Rockwell_400.font.js

Rockwell_400.font.js

273 ms

roboto.cufonfonts.js

roboto.cufonfonts.js

274 ms

iepngfix_tilebg.js

iepngfix_tilebg.js

204 ms

thickbox.js

thickbox.js

241 ms

jquery.md5.js

jquery.md5.js

272 ms

menu.js

menu.js

309 ms

sample_btn.jpg

sample_btn.jpg

144 ms

body-bg.jpg

body-bg.jpg

275 ms

metal-bg.png

metal-bg.png

70 ms

header-bg.jpg

header-bg.jpg

207 ms

main-logo.png

main-logo.png

208 ms

nav-login.png

nav-login.png

70 ms

nav-whois.png

nav-whois.png

71 ms

h-motto.png

h-motto.png

140 ms

nav-bg.png

nav-bg.png

140 ms

nav-home.png

nav-home.png

141 ms

nav-the-ws-story.png

nav-the-ws-story.png

207 ms

nav-for-registrars.png

nav-for-registrars.png

208 ms

nav-premium-domains.png

nav-premium-domains.png

209 ms

nav-faq.png

nav-faq.png

271 ms

nav-pricing.png

nav-pricing.png

272 ms

edit_webbuid.gif

edit_webbuid.gif

276 ms

blank.gif

blank.gif

250 ms

SEO Factors

ecso.ws SEO score

0

Language and Encoding

  • Language Detected

    EN

  • 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 Ecso.ws can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ecso.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

ecso.ws

Open Graph description is not detected on the main page of Ecso. 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: