names.com Website Information

Daily Unique Visits: 3,511

Daily Page Views: 14,044

Income Per Day: $39

Estimated Value: $21,060

names.com is registered under .COM top-level domain. Please check other sites in .COM zone.

No name server records were found.

and is probably hosted by INMOTI-1 - InMotion Hosting, Inc., US. See the full list of other websites hosted by INMOTI-1 - InMotion Hosting, Inc., US.

The highest website names.com position in Alexa rank database was 13436 and the lowest rank position was 998380. Current position of names.com in Alexa rank database is 357484.

Desktop speed score of names.com (92/100) is better than the results of 90.97% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of names.com (97/100) is better than the results of 49.9% of other sites and means that the page is mobile-friendly.

Mobile speed score of names.com (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

names.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

names.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain Name: NAMES.COM
Registry Domain ID: 3868293_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2021-09-24T21:56:37Z
Creation Date: 1995-08-15T04:00:00Z
Registry Expiry Date: 2030-08-14T04:00:00Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.INMOTIONHOSTING.COM
Name Server: NS2.INMOTIONHOSTING.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-12-29T07:27:00Z

names.com server information

Servers Location

names.com desktop page speed rank

Last tested: 2019-08-22

Desktop Speed Good

92/100

names.com Desktop Speed Test Quick Summary

priority - 7Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 67.3KiB (55% reduction).

Compressing https://sep.yimg.com/ty/cdn/familycrests/Banner.jpg?t=1565806066& could save 67.3KiB (55% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.3KiB (24% reduction).

Minifying https://player.vimeo.com/video/267455540 could save 1.3KiB (24% reduction) after compression.

names.com Desktop Resource Breakdown

Total Resources	44
Number of Hosts	10
Static Resources	36
JavaScript Resources	4
CSS Resources	1

names.com mobile page speed rank

Last tested: 2017-12-19

Mobile Speed Bad

63/100

names.com Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://cdn.shopify.com/s/files/1/2404/4545/t/5/as…s?16389658742705475628
https://fonts.googleapis.com/css?family=Work+Sans:400,700
https://fonts.googleapis.com/css?family=Work+Sans:600
https://productreviews.shopifycdn.com/assets/v4/sp…07c76740d012641514.css

priority - 12Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 116.7KiB (30% reduction).

Compressing https://cdn.shopify.com/s/files/1/2404/4545/produc…0x300.jpg?v=1512512655 could save 22.9KiB (52% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/produc…_540x.jpg?v=1512513051 could save 19.5KiB (20% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/files/…1080x.jpg?v=1512512227 could save 17.6KiB (12% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/produc…0x300.jpg?v=1511374945 could save 16.4KiB (51% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/produc…0x300.jpg?v=1512515093 could save 16.3KiB (52% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/produc…0x300.jpg?v=1512513051 could save 16KiB (52% reduction).
Compressing https://cdn.shopify.com/s/files/1/2404/4545/files/…0x200.jpg?v=1512512134 could save 7.9KiB (57% reduction).

priority - 8Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://in.visitors.live/ajax (expiration not specified)
https://names.com/cart.js (expiration not specified)
https://d1liekpayvooaz.cloudfront.net/apps/customi…ames-com.myshopify.com (2 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/167186…56049?v=2.8.6&r=stable (20 minutes)
https://cdn.shopify.com/s/javascripts/tricorder/tr….min.js?v=2017.09.05.1 (30 minutes)
https://d10lpsik1i8c69.cloudfront.net/graphics/blink_green.png (60 minutes)
https://d10lpsik1i8c69.cloudfront.net/graphics/logo-light.png (60 minutes)
https://d10lpsik1i8c69.cloudfront.net/graphics/sound-on-white.png (60 minutes)
https://d10lpsik1i8c69.cloudfront.net/js/clickstream.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.luckyorange.com/w.js?shop=names-com.myshopify.com (4 hours)

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 35% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 6.2KiB (34% reduction).

Minifying https://cdn.shopify.com/s/files/1/2404/4545/t/5/as…s?16389658742705475628 could save 6.2KiB (34% reduction) after compression.

names.com Mobile Resource Breakdown

Total Resources	61
Number of Hosts	19
Static Resources	46
JavaScript Resources	21
CSS Resources	6

names.com mobile page usability

Last tested: 2017-12-19

Mobile Usability Good

97/100

names.com Mobile Usability Test Quick Summary

priority - 2Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <li id="slickDot00" class="slick-active">Slide 1</li> and 1 others are close to other tap targets.
The tap target <button type="button">Slide 1</button> and 5 others are close to other tap targets.
The tap target <li id="slickDot01">Slide 2</li> and 3 others are close to other tap targets.

names.com HTML validation

Errors

The character encoding was not declared. Proceeding using “windows-1252”.

Line: Column: -
"......"

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 6
"...<html><head>..."

No space between attributes.

Line: 1 Column: - 69
"...rds" content=""</head><framese..." Line: 1 Column: - 97
"...set rows="100%", *" border="0"..."

Saw “<” when expecting an attribute name. Probable cause: Missing “>” immediately before.

Line: 1 Column: - 69
"...rds" content=""</head><framese..."

A slash was not immediately followed by “>”.

Line: 1 Column: - 71
"...s" content=""</head><frameset ..."

Attribute “<” not allowed on element “meta” at this point.

Line: 1 Column: 37 - 75
"...OM</title><meta name="keywords" content=""</head><frame..."

Attribute “head” not allowed on element “meta” at this point.

Line: 1 Column: 37 - 75
"...OM</title><meta name="keywords" content=""</head><frame..."