WHOWHERE.COM People Search, Yellow Pages, White Pages, Phone Directory – whowhere


whowhere.com website information.

whowhere.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for whowhere.com domain:

  • ns1.lycos.com
  • ns2.lycos.com
  • ns3.lycos.com
  • ns4.lycos.com

and probably website whowhere.com is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.

According to Alexa traffic rank the highest website whowhere.com position was 44110 (in the world). The lowest Alexa rank position was 999301. Now website whowhere.com ranked in Alexa database as number 46228 (in the world).

Website whowhere.com Desktop speed measurement score (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

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

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

Weekly Rank Report

DateRankChange
Nov-25-2024 46,228-798
Nov-24-2024 45,430383
Nov-23-2024 45,813277
Nov-22-2024 46,090135
Nov-21-2024 46,22579
Nov-20-2024 46,3044
Nov-19-2024 46,308-323

Advertisement

whowhere.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



whowhere.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: WHOWHERE.COM
Registry Domain ID: 1758191_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2023-12-31T10:23:30Z
Creation Date: 1996-01-02T05:00:00Z
Registry Expiry Date: 2025-01-01T05:00:00Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.HOVER.COM
Name Server: NS2.HOVER.COM
Name Server: NS3.HOVER.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-10-22T13:01:45Z

whowhere.com server information

Servers Location

IP Address
209.202.254.90
Region
Massachusetts
City
Waltham

whowhere.com desktop page speed rank

Last tested: 2015-09-16


Desktop Speed Medium
84/100

whowhere.com Desktop Speed Test Quick Summary


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

Your page has 7 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://scripts.lycos.com/jquery14/jquery-1.4.2.min.js
http://scripts.lycos.com/jquery14/jquery.corner.js
http://scripts.lycos.com/jquery14/jquery.autotab.js
http://ly.lygo.com/scripts/global/browserDetect.js
http://scripts.lycos.com/catman/init.js
http://scripts.lycos.com/catman/code/whowhere.com/homepage.js
http://ly.lygo.com/ly/whowhere/js/liverail.js

Optimize CSS Delivery of the following:

http://ly.lygo.com/ly/whowhere/css/whowhere.css
http://ly.lygo.com/ly/whowhere/css/home.css

priority - 3 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 32.2KiB (55% reduction).

Compressing http://delivery.e.switchadhub.com/adserver/sat.js?v=2 could save 25.6KiB (53% reduction).
Compressing http://ib.adnxs.com/tt?id=2540734&size=728x90 could save 4KiB (63% reduction).
Compressing http://delivery.e.switchadhub.com/adserver/sombrer…F&cfh=www.whowhere.com could save 1.9KiB (56% reduction).
Compressing http://delivery.e.switchadhub.com/adserver/meta_we…e_id=417&instance_id=0 could save 734B (56% reduction).

priority - 2 Optimize images

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

Optimize the following images to reduce their size by 17.3KiB (79% reduction).

Losslessly compressing http://ly.lygo.com/ly/whowhere/img/btn_green.jpg could save 16.5KiB (94% reduction).
Losslessly compressing http://ly.lygo.com/ly/whowhere/img/mobile_whowherehome.jpg could save 838B (19% reduction).

priority - 1 Leverage 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:

http://c.compete.com/bootstrap/667f89f26d96c30e997…6a608804d/bootstrap.js (60 minutes)
https://gum.criteo.com/sync?c=30&r=2&j=cr_handle_data_a (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 0 Minify 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 1.8KiB (39% reduction).

Minifying http://scripts.lycos.com/jquery14/jquery.corner.js could save 1KiB (33% reduction) after compression.
Minifying http://scripts.lycos.com/jquery14/jquery.autotab.js could save 800B (52% reduction) after compression.

whowhere.com Desktop Resources

Total Resources61
Number of Hosts23
Static Resources20
JavaScript Resources18
CSS Resources2

whowhere.com Desktop Resource Breakdown

whowhere.com mobile page speed rank

Last tested: 2019-06-26


Mobile Speed Medium
69/100

whowhere.com Mobile Speed Test Quick Summary


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

Your page has 6 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://ly.lygo.com/scripts/global/browserDetect.js
http://scripts.lycos.com/catman/init.js
http://scripts.lycos.com/catman3/code/yellowpages.whowhere.com/ros.js
https://scripts.lycos.com/jquery14/jquery-1.4.2.min.js
https://scripts.lycos.com/jquery14/jquery.corner.js
https://scripts.lycos.com/jquery14/jquery.autotab.js

Optimize CSS Delivery of the following:

https://ly.lygo.com/static/whowhere/css/whowhere.css
https://ly.lygo.com/static/whowhere/css/home.css

priority - 3 Leverage 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:

http://ly.lygo.com/scripts/global/browserDetect.js (expiration not specified)
http://www.google-analytics.com/ga.js (2 hours)
http://scripts.lycos.com/catman/init.js (6 hours)
http://scripts.lycos.com/catman3/code/yellowpages.whowhere.com/ros.js (6 hours)
https://scripts.lycos.com/jquery14/jquery-1.4.2.min.js (6 hours)
https://scripts.lycos.com/jquery14/jquery.autotab.js (6 hours)
https://scripts.lycos.com/jquery14/jquery.corner.js (6 hours)

priority - 2 Optimize images

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

Optimize the following images to reduce their size by 17KiB (97% reduction).

Compressing https://ly.lygo.com/static/whowhere/img/btn_green.jpg could save 17KiB (97% reduction).

priority - 0 Minify 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 1.9KiB (36% reduction).

Minifying https://scripts.lycos.com/jquery14/jquery.corner.js could save 1KiB (33% reduction) after compression.
Minifying https://scripts.lycos.com/jquery14/jquery.autotab.js could save 800B (52% reduction) after compression.
Minifying http://ly.lygo.com/scripts/global/browserDetect.js could save 117B (17% reduction) after compression.

priority - 0 Minify 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 226B (11% reduction).

Minifying http://whowhere.com/ could save 226B (11% reduction) after compression.

whowhere.com Mobile Resources

Total Resources14
Number of Hosts4
Static Resources10
JavaScript Resources7
CSS Resources2

whowhere.com Mobile Resource Breakdown

whowhere.com mobile page usability

Last tested: 2019-06-26


Mobile Usability Good
92/100

whowhere.com Mobile Usability Test Quick Summary


priority - 4 Size 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 <a href="#">(use my current location)</a> is close to 2 other tap targets.

The tap target <input type="submit" class="searchButton"> is close to 2 other tap targets.

The tap target <input type="submit" class="cancelButton"> is close to 1 other tap targets.

priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 964 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="back"></div> falls outside the viewport.
The element <div id="title">WhoWhere</div> falls outside the viewport.
The element <li class="current">Yellow Pages</li> falls outside the viewport.
The element <label>Find</label> falls outside the viewport.
The element <label>Near (use my current location)</label> falls outside the viewport.
The element <div> falls outside the viewport.
The element <p id="links">Desktop Whowhe…| Lycos Mobile</p> falls outside the viewport.
The element <p id="copyright">Copyright © 20…ghts Reserved.</p> falls outside the viewport.

whowhere.com similar domains

Similar domains:
www.whowhere.com
www.whowhere.net
www.whowhere.org
www.whowhere.info
www.whowhere.biz
www.whowhere.us
www.whowhere.mobi
www.howhere.com
www.whowhere.com
www.qhowhere.com
www.wqhowhere.com
www.qwhowhere.com
www.ahowhere.com
www.wahowhere.com
www.awhowhere.com
www.showhere.com
www.wshowhere.com
www.swhowhere.com
www.ehowhere.com
www.wehowhere.com
www.ewhowhere.com
www.wowhere.com
www.wbowhere.com
www.whbowhere.com
www.wbhowhere.com
www.wgowhere.com
www.whgowhere.com
www.wghowhere.com
www.wyowhere.com
www.whyowhere.com
www.wyhowhere.com
www.wuowhere.com
www.whuowhere.com
www.wuhowhere.com
www.wjowhere.com
www.whjowhere.com
www.wjhowhere.com
www.wnowhere.com
www.whnowhere.com
www.wnhowhere.com
www.whwhere.com
www.whiwhere.com
www.whoiwhere.com
www.whiowhere.com
www.whkwhere.com
www.whokwhere.com
www.whkowhere.com
www.whlwhere.com
www.wholwhere.com
www.whlowhere.com
www.whpwhere.com
www.whopwhere.com
www.whpowhere.com
www.whohere.com
www.whoqhere.com
www.whowqhere.com
www.whoqwhere.com
www.whoahere.com
www.whowahere.com
www.whoawhere.com
www.whoshere.com
www.whowshere.com
www.whoswhere.com
www.whoehere.com
www.whowehere.com
www.whoewhere.com
www.whowere.com
www.whowbere.com
www.whowhbere.com
www.whowbhere.com
www.whowgere.com
www.whowhgere.com
www.whowghere.com
www.whowyere.com
www.whowhyere.com
www.whowyhere.com
www.whowuere.com
www.whowhuere.com
www.whowuhere.com
www.whowjere.com
www.whowhjere.com
www.whowjhere.com
www.whownere.com
www.whowhnere.com
www.whownhere.com
www.whowhre.com
www.whowhwre.com
www.whowhewre.com
www.whowhwere.com
www.whowhsre.com
www.whowhesre.com
www.whowhsere.com
www.whowhdre.com
www.whowhedre.com
www.whowhdere.com
www.whowhrre.com
www.whowherre.com
www.whowhrere.com
www.whowhee.com
www.whowheee.com
www.whowheree.com
www.whowheere.com
www.whowhede.com
www.whowherde.com
www.whowhefe.com
www.whowherfe.com
www.whowhefre.com
www.whowhete.com
www.whowherte.com
www.whowhetre.com
www.whowher.com
www.whowherw.com
www.whowherew.com
www.whowherwe.com
www.whowhers.com
www.whowheres.com
www.whowherse.com
www.whowherd.com
www.whowhered.com
www.whowherr.com
www.whowherer.com
www.whowhere.con

whowhere.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


whowhere.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.