PRINCE.ORG prince.org: where fans of Prince music meet and stay up-to-date


prince.org website information.

prince.org domain name is registered by .ORG top-level domain registry. See the other sites registred in .ORG domain zone.

Following name servers are specified for prince.org domain:

  • c.dns.gandi.net
  • a.dns.gandi.net
  • b.dns.gandi.net

and probably website prince.org is hosted by CHINA169-BJ China Unicom Beijing Province Network, CN web hosting company. Check the complete list of other most popular websites hosted by CHINA169-BJ China Unicom Beijing Province Network, CN hosting company.

According to Alexa traffic rank the highest website prince.org position was 16382 (in the world). The lowest Alexa rank position was 801256. Now website prince.org ranked in Alexa database as number 47692 (in the world).

Website prince.org Desktop speed measurement score (91/100) is better than the results of 90.07% of other sites and shows that the page is performing great on desktop computers.

prince.org Mobile usability score (62/100) is better than the results of 7.29% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of prince.org (77/100) is better than the results of 86.05% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-28-2024 47,692404
Apr-27-2024 48,0961,029
Apr-26-2024 49,125-879
Apr-25-2024 48,2460
Apr-24-2024 48,2460
Apr-23-2024 48,246163
Apr-22-2024 48,409-555

Advertisement

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



prince.org 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: PRINCE.ORG
Registry Domain ID: D3486659-LROR
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2020-08-30T06:41:12Z
Creation Date: 1998-09-28T04:00:00Z
Registry Expiry Date: 2025-09-27T04:00:00Z
Registrar Registration Expiration Date:
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Tog Dog Enterprises
Registrant State/Province: CA
Registrant Country: US
Name Server: NS-40-B.GANDI.NET
Name Server: NS-92-A.GANDI.NET
Name Server: NS-150-C.GANDI.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2021-05-03T08:50:47Z

prince.org server information

Servers Location

IP Address
173.13.130.193
Region
California
City
San Francisco

prince.org desktop page speed rank

Last tested: 2016-11-21


Desktop Speed Good
91/100

prince.org Desktop Speed Test Quick Summary


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

Your page has 5 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://prince.org/_js/all_1.js
http://prince.org/_js/org_v1.js
http://google.com/coop/cse/brand?form=searchbox_00…78458986%3Acneoimw0ggu
http://translate.google.com/translate_a/element.js…leTranslateElementInit

Use asynchronous versions of the following scripts:

http://www.google-analytics.com/urchin.js

Optimize CSS Delivery of the following:

http://prince.org/_css/main_5.css
https://translate.googleapis.com/translate_static/css/translateelement.css

priority - 2 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://prince.org:81/img/t9a7f16c52c.jpg (expiration not specified)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/…ent/44/element_main.js (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 3.6KiB (53% reduction).

Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 1.6KiB (57% reduction).
Compressing https://www.google.com/cse/static/en/google_custom_search_watermark.gif could save 1.4KiB (69% reduction).
Compressing http://prince.org/i/logo4.gif could save 670B (32% 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 975B (15% reduction).

Minifying http://www.google-analytics.com/urchin.js could save 975B (15% reduction) after compression.

prince.org Desktop Resources

Total Resources25
Number of Hosts10
Static Resources20
JavaScript Resources8
CSS Resources2

prince.org Desktop Resource Breakdown

prince.org mobile page speed rank

Last tested: 2017-06-08


Mobile Speed Medium
77/100

prince.org Mobile Speed Test Quick Summary


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

Your page has 4 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://prince.org/_js/all_1.js
http://prince.org/_js/org_v1.js
http://google.com/coop/cse/brand?form=searchbox_00…78458986%3Acneoimw0ggu
http://translate.google.com/translate_a/element.js…leTranslateElementInit

Optimize CSS Delivery of the following:

http://prince.org/main.css
https://translate.googleapis.com/translate_static/css/translateelement.css

priority - 4 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://prince.org/main.css (expiration not specified)
http://prince.org:81/img/td37e09d437.jpg (expiration not specified)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

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

Minifying http://prince.org/main.css could save 1.2KiB (24% reduction) after compression.

prince.org Mobile Resources

Total Resources26
Number of Hosts10
Static Resources22
JavaScript Resources8
CSS Resources2

prince.org Mobile Resource Breakdown

prince.org mobile page usability

Last tested: 2017-06-08


Mobile Usability Bad
62/100

prince.org Mobile Usability Test Quick Summary


priority - 40 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

independent and unofficial and 1 others render only 5 pixels tall (13 CSS pixels).

Takes place on…nd March 31st. and 24 others render only 4 pixels tall (11 CSS pixels).

renders only 4 pixels tall (11 CSS pixels).

PRINCEPEDIA and 7 others render only 5 pixels tall (13 CSS pixels).

| and 6 others render only 4 pixels tall (11 CSS pixels).

Wed 7th Jun 2017 10:29pm renders only 4 pixels tall (11 CSS pixels).

or enter username and 4 others render only 4 pixels tall (11 CSS pixels).

Sign up renders only 4 pixels tall (11 CSS pixels).

PRINCE PASSED…MOURN HIS LOSS and 4 others render only 7 pixels tall (17 CSS pixels).

There is no wa…it to be -- by and 4 others render only 7 pixels tall (17 CSS pixels).

coming together and dancing and 1 others render only 7 pixels tall (17 CSS pixels).

human renders only 7 pixels tall (17 CSS pixels).

--Ben, founder…org, 4/22/2016 renders only 4 pixels tall (11 CSS pixels).

@princeorg renders only 4 pixels tall (11 CSS pixels).

Gigapixel Imag…taff, has made and 2 others render only 5 pixels tall (13 CSS pixels).

a super-cool '…ence and paths and 2 others render only 5 pixels tall (13 CSS pixels).

, showing the…. Big props to renders only 5 pixels tall (13 CSS pixels).

send us a story renders only 4 pixels tall (11 CSS pixels).

PRNFamily Pres…017 [SOLD OUT] and 34 others render only 5 pixels tall (12 CSS pixels).

(973 comments) and 44 others render only 4 pixels tall (11 CSS pixels).

Associated artists & people and 29 others render only 4 pixels tall (11 CSS pixels).

Stay in touch via and 1 others render only 4 pixels tall (11 CSS pixels).

Facebook and 1 others render only 5 pixels tall (12 CSS pixels).

12 people are…ntly chatting. and 13 others render only 4 pixels tall (11 CSS pixels).

on June 7th in…nce history... renders only 5 pixels tall (14 CSS pixels).
2002 and 9 others render only 4 pixels tall (11 CSS pixels).
and 2 others render only 4 pixels tall (11 CSS pixels).
yes, i even dr…undane topics. and 6 others render only 4 pixels tall (11 CSS pixels).
, 7/16 in the and 5 others render only 4 pixels tall (11 CSS pixels).
Rising up when I thought and 27 others render only 4 pixels tall (11 CSS pixels).
opinion poll and 3 others render only 7 pixels tall (17 CSS pixels).

General forums…e related talk and 1 others render only 5 pixels tall (14 CSS pixels).

Where they're…13,784 topics) and 17 others render only 4 pixels tall (11 CSS pixels).

Handle: renders only 4 pixels tall (11 CSS pixels).

Is the Estate…r and respect? renders only 5 pixels tall (12 CSS pixels).

A randomly-sel…our gallery... renders only 4 pixels tall (11 CSS pixels).

Vanity 6 poster renders only 4 pixels tall (11 CSS pixels).

copyright © 19…ghts reserved. renders only 4 pixels tall (11 CSS pixels).
terms of service and 3 others render only 4 pixels tall (11 CSS pixels).
· and 2 others render only 4 pixels tall (11 CSS pixels).

priority - 15 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="/"></a> is close to 1 other tap targets.

The tap target <input type="text" name="q"> is close to 2 other tap targets.

The tap target <input type="submit" name="sa"> and 3 others are close to other tap targets.

The tap target <div id=":0.targetLanguage" class="goog-te-gadget-simple">Select Language​▼</div> is close to 1 other tap targets.

The tap target <a href="javascript:void(0)" class="goog-te-menu-value">Select Language​▼</a> is close to 1 other tap targets.

The tap target <a href="javascript:void(0)" class="goog-te-menu-value">Select Language​▼</a> and 1 others are close to other tap targets.

The tap target <a href="javascript:void(0)" class="goog-te-menu-value">Select Language​▼</a> is close to 1 other tap targets.

The tap target <a href="javascript:void(0)" class="goog-te-menu-value">Select Language​▼</a> is close to 1 other tap targets.

The tap target <a href="/">HOME</a> and 6 others are close to other tap targets.

The tap target <a href="/login.html?lo…st=/index.html">Sign up</a> is close to 1 other tap targets.

The tap target <input id="login_un" type="text" name="login_un"> and 2 others are close to other tap targets.

The tap target <input id="remember" type="checkbox" name="remember"> and 1 others are close to other tap targets.

The tap target <a href="/msg/7/441628/…IRMED-by-APPLE">Purple Rain De…RMED by APPLE.</a> and 25 others are close to other tap targets.

The tap target <a href="/profile/Militant">Militant</a> and 30 others are close to other tap targets.

The tap target <a href="http://twitter.com/princeorg">Twitter</a> is close to 1 other tap targets.

The tap target <a href="/profile/SquirrelMeat">SquirrelMeat</a> and 3 others are close to other tap targets.

The tap target <a href="/faq/1_prince.org_Site_FAQ">about</a> and 1 others are close to other tap targets.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

prince.org similar domains

Similar domains:
www.prince.com
www.prince.net
www.prince.org
www.prince.info
www.prince.biz
www.prince.us
www.prince.mobi
www.rince.org
www.prince.org
www.orince.org
www.porince.org
www.oprince.org
www.lrince.org
www.plrince.org
www.lprince.org
www.pince.org
www.peince.org
www.preince.org
www.perince.org
www.pdince.org
www.prdince.org
www.pdrince.org
www.pfince.org
www.prfince.org
www.pfrince.org
www.ptince.org
www.prtince.org
www.ptrince.org
www.prnce.org
www.prunce.org
www.priunce.org
www.pruince.org
www.prjnce.org
www.prijnce.org
www.prjince.org
www.prknce.org
www.priknce.org
www.prkince.org
www.pronce.org
www.prionce.org
www.proince.org
www.price.org
www.pribce.org
www.prinbce.org
www.pribnce.org
www.prihce.org
www.prinhce.org
www.prihnce.org
www.prijce.org
www.prinjce.org
www.primce.org
www.prinmce.org
www.primnce.org
www.prine.org
www.prinxe.org
www.princxe.org
www.prinxce.org
www.prinde.org
www.princde.org
www.prindce.org
www.prinfe.org
www.princfe.org
www.prinfce.org
www.prinve.org
www.princve.org
www.prinvce.org
www.princ.org
www.princw.org
www.princew.org
www.princwe.org
www.princs.org
www.princes.org
www.princse.org
www.princd.org
www.princed.org
www.princr.org
www.princer.org
www.princre.org

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


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