Tools & Wizards About Us
enom.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

enom.org

Enom - Reseller Platform for Domains, Email, and SSL

Page Load Speed

2.6 sec in total

First Response

151 ms

Resources Loaded

955 ms

Page Rendered

1.5 sec

enom.org screenshot

About Website

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

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

Visit enom.org

Key Findings

We analyzed Enom.org page load time and found that the first response time was 151 ms and then it took 2.4 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.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

enom.org

151 ms

www.enom.com

23 ms

www.enom.com

27 ms

gtm.js

106 ms

style.min.css

63 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Enom.org, 55% (46 requests) were made to 149463845.v2.pressablecdn.com and 32% (27 requests) were made to Enom.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source 149463845.v2.pressablecdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.3 kB (4%)

Content Size

3.8 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Enom.org main page is 3.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 64.3 kB

  • Original 77.5 kB
  • After minification 73.0 kB
  • After compression 13.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 64.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 62.5 kB

  • Original 3.5 MB
  • After minification 3.4 MB

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

-6%

Potential reduce by 9.5 kB

  • Original 160.9 kB
  • After minification 160.6 kB
  • After compression 151.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 933 B

  • Original 65.5 kB
  • After minification 65.5 kB
  • After compression 64.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. Enom.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (42%)

Requests Now

64

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 64 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 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

enom.org

enom.org

151 ms

www.enom.com

www.enom.com

23 ms

www.enom.com

www.enom.com

27 ms

gtm.js

gtm.js

106 ms

style.min.css

style.min.css

63 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

78 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

79 ms

front.css

front.css

137 ms

front.css

front.css

133 ms

socialshare.css

socialshare.css

130 ms

frontend.js

frontend.js

136 ms

react.min.js

react.min.js

72 ms

react-dom.min.js

react-dom.min.js

99 ms

escape-html.min.js

escape-html.min.js

79 ms

element.min.js

element.min.js

92 ms

front.js

front.js

210 ms

front.js

front.js

209 ms

socialshare.js

socialshare.js

224 ms

e-202434.js

e-202434.js

96 ms

Tucows_enom_navycolour.svg

Tucows_enom_navycolour.svg

64 ms

digicert-logo-1-300x128-1-1-e1614010673758-1.png

digicert-logo-1-300x128-1-1-e1614010673758-1.png

180 ms

menu-b2.svg

menu-b2.svg

160 ms

menu-b1.svg

menu-b1.svg

163 ms

x-nav.svg

x-nav.svg

162 ms

search.svg

search.svg

161 ms

outline_slash.svg

outline_slash.svg

160 ms

monitor.svg

monitor.svg

141 ms

people.svg

people.svg

144 ms

calendar.svg

calendar.svg

149 ms

isp.svg

isp.svg

165 ms

chevron-left.svg

chevron-left.svg

237 ms

chevron-left-hover.svg

chevron-left-hover.svg

240 ms

chevron-left-press.svg

chevron-left-press.svg

237 ms

chevron-right.svg

chevron-right.svg

238 ms

chevron-right-hover.svg

chevron-right-hover.svg

234 ms

chevron-right-press.svg

chevron-right-press.svg

250 ms

an-icon-placeholder-4.svg

an-icon-placeholder-4.svg

241 ms

an-icon-placeholder-1-1.svg

an-icon-placeholder-1-1.svg

244 ms

an-icon-placeholder-2-1.svg

an-icon-placeholder-2-1.svg

242 ms

an-icon-placeholder-3-1.svg

an-icon-placeholder-3-1.svg

247 ms

store-tld-logo.svg

store-tld-logo.svg

246 ms

Logo_foot.svg

Logo_foot.svg

250 ms

twitter-white.svg

twitter-white.svg

300 ms

linkedin-white.svg

linkedin-white.svg

300 ms

icann.svg

icann.svg

252 ms

chevron-down-nav-b3.svg

chevron-down-nav-b3.svg

139 ms

img-1.png

img-1.png

142 ms

front-b1-1.png

front-b1-1.png

139 ms

greengeeks_logo-300x96.png

greengeeks_logo-300x96.png

43 ms

whmcs-logo-300x68-1.png

whmcs-logo-300x68-1.png

137 ms

bandzoogle_reversed-300x104.png

bandzoogle_reversed-300x104.png

42 ms

domain-search-on-laptop.jpg

domain-search-on-laptop.jpg

143 ms

working-on-laptop-at-desk.jpg

working-on-laptop-at-desk.jpg

142 ms

armored-guard.jpg

armored-guard.jpg

141 ms

image-6.png

image-6.png

169 ms

couponcodes-store.jpeg

couponcodes-store.jpeg

138 ms

image-7.png

image-7.png

149 ms

citychew-biz-enom.jpeg

citychew-biz-enom.jpeg

150 ms

adventurepro-us-enom.jpeg

adventurepro-us-enom.jpeg

149 ms

image-4.png

image-4.png

168 ms

image-2.png

image-2.png

172 ms

teachfromhome-online.jpeg

teachfromhome-online.jpeg

166 ms

com-tld-logo.png

com-tld-logo.png

165 ms

online-tld-logo-enom.png

online-tld-logo-enom.png

165 ms

shop-tld-logo-1.png

shop-tld-logo-1.png

171 ms

dotCLOUD_logo.png

dotCLOUD_logo.png

172 ms

happy-guy-through-yellow-shelf.jpg

happy-guy-through-yellow-shelf.jpg

173 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

174 ms

proximanova-semibold-webfont.woff

proximanova-semibold-webfont.woff

173 ms

proximanova-thin-webfont.woff

proximanova-thin-webfont.woff

243 ms

proximanova-light-webfont.woff

proximanova-light-webfont.woff

345 ms

proximanova-bold-webfont.woff

proximanova-bold-webfont.woff

173 ms

proximanova-medium-webfont.woff

proximanova-medium-webfont.woff

172 ms

proximanova-extrabold-webfont.woff

proximanova-extrabold-webfont.woff

247 ms

proximanova-black-webfont.woff

proximanova-black-webfont.woff

269 ms

SharpSansDispNo1-Bold.woff

SharpSansDispNo1-Bold.woff

35 ms

SharpSansDispNo1-Extrabold.woff

SharpSansDispNo1-Extrabold.woff

131 ms

SharpSansDispNo1-Black.woff

SharpSansDispNo1-Black.woff

130 ms

SharpSansDispNo1-Semibold.woff

SharpSansDispNo1-Semibold.woff

107 ms

SharpSansDispNo1-Medium.woff

SharpSansDispNo1-Medium.woff

178 ms

SharpSansDispNo1-Book.woff

SharpSansDispNo1-Book.woff

380 ms

SharpSansDispNo1-Thin.woff

SharpSansDispNo1-Thin.woff

154 ms

SharpSansDispNo1-Ultrathin.woff

SharpSansDispNo1-Ultrathin.woff

178 ms

SharpSansDispNo1-Hairline.woff

SharpSansDispNo1-Hairline.woff

395 ms

Accessibility Review

enom.org accessibility score

81

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

High

[role] values are not valid

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.org best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enom.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Enom.org 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.org

Open Graph data is detected on the main page of Enom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: