Tools & Wizards About Us
en2.efax.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

en2.efax.com

Login | eFax

Page Load Speed

4.6 sec in total

First Response

1.2 sec

Resources Loaded

3.2 sec

Page Rendered

124 ms

en2.efax.com screenshot

About Website

Welcome to en2.efax.com homepage info - get ready to check En 2 EFax best content for United States right away, or after learning these important things about en2.efax.com

Login to your eFax account to view and send faxes, update account information and access our online help.

Visit en2.efax.com

Key Findings

We analyzed En2.efax.com page load time and found that the first response time was 1.2 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

en2.efax.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value8,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

en.efax.com

1195 ms

styles.less

477 ms

jqueryJS

302 ms

mbox.js

97 ms

mootools1-2_corenmore.js

107 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original En2.efax.com, 11% (7 requests) were made to Sassets.en.efax.com and 8% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source En.efax.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 532.6 kB (59%)

Content Size

900.0 kB

After Optimization

367.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of En2.efax.com main page is 900.0 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. 35% of websites need less resources to load. Javascripts take 418.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 36.7 kB

  • Original 51.8 kB
  • After minification 48.9 kB
  • After compression 15.1 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 36.7 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 160.2 kB
  • After minification 158.6 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. En 2 EFax images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 263.6 kB

  • Original 418.1 kB
  • After minification 406.0 kB
  • After compression 154.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 263.6 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 230.7 kB

  • Original 269.8 kB
  • After minification 222.7 kB
  • After compression 39.1 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. En2.efax.com needs all CSS files to be minified and compressed as it can save up to 230.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (67%)

Requests Now

57

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.efax.com

en.efax.com

1195 ms

styles.less

styles.less

477 ms

jqueryJS

jqueryJS

302 ms

mbox.js

mbox.js

97 ms

mootools1-2_corenmore.js

mootools1-2_corenmore.js

107 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

233 ms

bootstrap.css

bootstrap.css

293 ms

bootstrap.min.css

bootstrap.min.css

283 ms

main.css

main.css

209 ms

WebResource.axd

WebResource.axd

203 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

355 ms

ScriptResource.axd

ScriptResource.axd

346 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

314 ms

bootstrap.min.js

bootstrap.min.js

409 ms

internal.js

internal.js

97 ms

subcookieJS

subcookieJS

351 ms

bootstrapJS

bootstrapJS

369 ms

otherJS

otherJS

451 ms

widgetJS

widgetJS

389 ms

main

main

669 ms

j.php

j.php

38 ms

ScriptResource.axd

ScriptResource.axd

80 ms

pano_micro.jpg

pano_micro.jpg

225 ms

efax.gif

efax.gif

95 ms

efax_badge.png

efax_badge.png

166 ms

iphone-black.png

iphone-black.png

166 ms

galaxy-white.png

galaxy-white.png

223 ms

appstore_btn.gif

appstore_btn.gif

224 ms

playstore_btn.gif

playstore_btn.gif

225 ms

standard

standard

42 ms

v.gif

v.gif

4 ms

5-en-web-logo.gif

5-en-web-logo.gif

177 ms

standard

standard

7 ms

phone50-53.gif

phone50-53.gif

161 ms

standard

standard

22 ms

nr-885.min.js

nr-885.min.js

170 ms

banner-apps.png

banner-apps.png

235 ms

standard-footer.png

standard-footer.png

157 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

142 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

534 ms

gtm.js

gtm.js

113 ms

4aac183407

4aac183407

134 ms

34 ms

conversion_async.js

conversion_async.js

58 ms

analytics.js

analytics.js

36 ms

bat.js

bat.js

136 ms

linkid.js

linkid.js

13 ms

50 ms

collect

collect

19 ms

collect

collect

65 ms

40 ms

35 ms

44 ms

45 ms

collect

collect

23 ms

collect

collect

72 ms

53 ms

65 ms

67 ms

66 ms

70 ms

4aac183407

4aac183407

24 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

433 ms

Accessibility Review

en2.efax.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

en2.efax.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

en2.efax.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 En2.efax.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 En2.efax.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

en2.efax.com

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