2.8 sec in total
189 ms
2.4 sec
200 ms
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.orgWe analyzed Enom.org page load time and found that the first response time was 189 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
enom.org performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value3.8 s
55/100
25%
Value10.7 s
7/100
10%
Value23,790 ms
0/100
30%
Value0.006
100/100
15%
Value31.9 s
0/100
10%
189 ms
510 ms
662 ms
915 ms
172 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Enom.org, 80% (37 requests) were made to Enom.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Enom.com.
Page size can be reduced by 560.9 kB (57%)
988.7 kB
427.8 kB
In fact, the total size of Enom.org main page is 988.7 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. 25% of websites need less resources to load. Javascripts take 607.8 kB which makes up the majority of the site volume.
Potential reduce by 101.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 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.
Potential reduce by 23.5 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.
Potential reduce by 435.7 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 435.7 kB or 72% of the original size.
Number of requests can be reduced by 8 (19%)
43
35
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.
enom.org
189 ms
www.enom.com
510 ms
css.ashx
662 ms
js.ashx
915 ms
css.ashx
172 ms
26241557.js
170 ms
WebResource.axd
324 ms
ScriptResource.axd
330 ms
ScriptResource.axd
257 ms
TopMenu.ascx.js
250 ms
event
26 ms
loader_small3.gif
289 ms
enom.png
291 ms
tld-family.png
289 ms
tld-social.png
290 ms
tld-rocks.png
292 ms
tld_live.png
291 ms
carousel_tld_ngo.png
295 ms
carousel_tld_gives.png
294 ms
carousel_tld_co.png
295 ms
carousel_tld_news.png
294 ms
carousel_tld_engineer.png
294 ms
carousel_tld_attorney.png
295 ms
carousel_tld_consulting.png
298 ms
carousel_tld_dentist.png
298 ms
carousel_tld_studio.png
296 ms
carousel_tld_band.png
297 ms
carousel_tld_actor.png
295 ms
carousel_tld_video.png
293 ms
hp-box-email-1.png
353 ms
hp-box-ssl-1.png
358 ms
hp-box-wsb-1.png
357 ms
enom-small.png
354 ms
rightside-small.png
357 ms
loading.gif
358 ms
hp_bg-generic_1600x600.jpg
730 ms
glyphicons-halflings-regular.woff
412 ms
shell-1.png
495 ms
analytics.js
227 ms
answerdash.min.js
633 ms
loader-2.gif
157 ms
collect
15 ms
verisign-seal.htm
88 ms
enom-64002064.png
106 ms
getseal
66 ms
getseal
113 ms
enom.org accessibility score
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
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
enom.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
enom.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
enom.org
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: