Tools & Wizards About Us
e2m.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e2m.com

E2M has merged with Haskell

Page Load Speed

961 ms in total

First Response

145 ms

Resources Loaded

719 ms

Page Rendered

97 ms

e2m.com screenshot

About Website

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

Visit e2m.com

Key Findings

We analyzed E2m.com page load time and found that the first response time was 145 ms and then it took 816 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

e2m.com performance score

0

Network Requests Diagram

e2m.com

145 ms

index.html

224 ms

WF-016195-001650.css

122 ms

normalize.css

155 ms

main.css

157 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original E2m.com, 50% (8 requests) were made to Haskell.com and 19% (3 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (224 ms) relates to the external source Haskell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.1 kB (37%)

Content Size

91.6 kB

After Optimization

57.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E2m.com main page is 91.6 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. Javascripts take 33.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 4.3 kB

  • Original 6.1 kB
  • After minification 3.9 kB
  • After compression 1.8 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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 4.3 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 449 B

  • Original 30.3 kB
  • After minification 29.8 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. E2M images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 9.9 kB

  • Original 33.3 kB
  • After minification 32.6 kB
  • After compression 23.4 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 9.9 kB or 30% of the original size.

CSS Optimization

-88%

Potential reduce by 19.4 kB

  • Original 21.9 kB
  • After minification 9.9 kB
  • After compression 2.6 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. E2m.com needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e2m.com

e2m.com

145 ms

index.html

index.html

224 ms

WF-016195-001650.css

WF-016195-001650.css

122 ms

normalize.css

normalize.css

155 ms

main.css

main.css

157 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

189 ms

jquery.min.js

jquery.min.js

32 ms

plugins.js

plugins.js

76 ms

main.js

main.js

107 ms

ga.js

ga.js

55 ms

e2m-logo.png

e2m-logo.png

84 ms

haskell-logo.png

haskell-logo.png

65 ms

WF-016195-001650-000449-1373434084.woff

WF-016195-001650-000449-1373434084.woff

90 ms

WF-016195-001650-000447-1373434084.woff

WF-016195-001650-000447-1373434084.woff

142 ms

WF-016195-001650-000450-1373434084.woff

WF-016195-001650-000450-1373434084.woff

99 ms

__utm.gif

__utm.gif

25 ms

SEO Factors

e2m.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E2m.com 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 E2m.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

e2m.com

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