Tools & Wizards About Us
enom.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

enom.com

Enom - Reseller Platform for Domains, Email, and SSL

Page Load Speed

3.1 sec in total

First Response

562 ms

Resources Loaded

2.4 sec

Page Rendered

168 ms

enom.com screenshot

About Website

Welcome to enom.com homepage info - get ready to check Enom best content for United States right away, or after learning these important things about enom.com

Want to offer domains, email and SSL? See why leading website builders and tech companies use Enom’s white-label platform.

Visit enom.com

Key Findings

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

Performance Metrics

enom.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value5,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

www.enom.com

562 ms

css.ashx

698 ms

js.ashx

970 ms

css.ashx

180 ms

26241557.js

105 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 82% of them (37 requests) were addressed to the original Enom.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Cdn.optimizely.com. The less responsive or slowest element that took the longest time to load (970 ms) belongs to the original domain Enom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 705.1 kB (44%)

Content Size

1.6 MB

After Optimization

885.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 101.8 kB

  • Original 115.7 kB
  • After minification 87.7 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 28.1 kB, which is 24% 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 101.8 kB or 88% of the original size.

Image Optimization

-7%

Potential reduce by 49.1 kB

  • Original 708.5 kB
  • After minification 659.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. Enom images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 543.0 kB

  • Original 752.6 kB
  • After minification 723.2 kB
  • After compression 209.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 543.0 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 11.2 kB

  • Original 13.7 kB
  • After minification 8.4 kB
  • After compression 2.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. Enom.com needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enom. 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

www.enom.com

www.enom.com

562 ms

css.ashx

css.ashx

698 ms

js.ashx

js.ashx

970 ms

css.ashx

css.ashx

180 ms

26241557.js

26241557.js

105 ms

WebResource.axd

WebResource.axd

355 ms

ScriptResource.axd

ScriptResource.axd

364 ms

ScriptResource.axd

ScriptResource.axd

268 ms

TopMenu.ascx.js

TopMenu.ascx.js

272 ms

event

event

16 ms

loader_small3.gif

loader_small3.gif

160 ms

enom.png

enom.png

161 ms

tld-family.png

tld-family.png

160 ms

tld-video.png

tld-video.png

161 ms

tld_live.png

tld_live.png

161 ms

tld-studio.png

tld-studio.png

161 ms

carousel_tld_ngo.png

carousel_tld_ngo.png

195 ms

carousel_tld_ong.png

carousel_tld_ong.png

193 ms

carousel_tld_gives.png

carousel_tld_gives.png

195 ms

carousel_tld_news.png

carousel_tld_news.png

198 ms

carousel_tld_engineer.png

carousel_tld_engineer.png

196 ms

carousel_tld_attorney.png

carousel_tld_attorney.png

199 ms

carousel_tld_consulting.png

carousel_tld_consulting.png

289 ms

carousel_tld_dentist.png

carousel_tld_dentist.png

294 ms

carousel_tld_studio.png

carousel_tld_studio.png

290 ms

carousel_tld_band.png

carousel_tld_band.png

289 ms

carousel_tld_actor.png

carousel_tld_actor.png

291 ms

carousel_tld_video.png

carousel_tld_video.png

295 ms

hp-box-email-1.png

hp-box-email-1.png

384 ms

hp-box-ssl-1.png

hp-box-ssl-1.png

386 ms

hp-box-wsb-1.png

hp-box-wsb-1.png

388 ms

enom-small.png

enom-small.png

386 ms

rightside-small.png

rightside-small.png

387 ms

loading.gif

loading.gif

390 ms

hp_bg-generic_1600x600.jpg

hp_bg-generic_1600x600.jpg

809 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

456 ms

shell-1.png

shell-1.png

539 ms

analytics.js

analytics.js

118 ms

answerdash.min.js

answerdash.min.js

513 ms

loader-2.gif

loader-2.gif

327 ms

collect

collect

14 ms

verisign-seal.htm

verisign-seal.htm

98 ms

enom-64002064.png

enom-64002064.png

131 ms

getseal

getseal

48 ms

getseal

getseal

25 ms

Accessibility Review

enom.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

enom.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

SEO Factors

enom.com SEO score

93

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

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 Enom.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 Enom.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

enom.com

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