worldcourts.com Website Information

Daily Unique Visits: 3,614

Daily Page Views: 14,456

Income Per Day: $40

Estimated Value: $21,600

worldcourts.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 AS17378 - TIERPOINT PENNSYLVANIA TWO LLC, US. See the full list of other websites hosted by AS17378 - TIERPOINT PENNSYLVANIA TWO LLC, US.

The highest website worldcourts.com position in Alexa rank database was 27845 and the lowest rank position was 999209. Current position of worldcourts.com in Alexa rank database is 347227.

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

Mobile usability score of worldcourts.com (58/100) is better than the results of 1.7% of other sites and means that the page is not mobile-friendly.

Mobile speed score of worldcourts.com (97/100) is better than the results of 95.14% of other sites and shows that the landing page performance on mobile devices is excellent.

worldcourts.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.

worldcourts.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: WORLDCOURTS.COM
Registry Domain ID: 34428234_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.publicdomainregistry.com
Updated Date: 2023-09-15T02:41:09Z
Creation Date: 2000-09-11T12:39:31Z
Registry Expiry Date: 2024-09-11T12:39:31Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.DIGITALOCEAN.COM
Name Server: NS2.DIGITALOCEAN.COM
Name Server: NS3.DIGITALOCEAN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2023-09-23T16:19:26Z

worldcourts.com server information

Servers Location

worldcourts.com desktop page speed rank

Last tested: 2019-03-10

Desktop Speed Good

98/100

worldcourts.com Desktop Speed Test Quick Summary

priority - 1Leverage 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://worldcourts.com/index/images/logo_right.gif (expiration not specified)
http://www.worldcourts.com/index/images/logo.gif (expiration not specified)
http://www.google-analytics.com/ga.js (2 hours)

worldcourts.com Desktop Resource Breakdown

Total Resources	5
Number of Hosts	3
Static Resources	3
JavaScript Resources	1

worldcourts.com mobile page speed rank

Last tested: 2019-03-10

Mobile Speed Good

97/100

worldcourts.com Mobile Speed Test Quick Summary

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

worldcourts.com Mobile Resource Breakdown

Total Resources	5
Number of Hosts	3
Static Resources	3
JavaScript Resources	1

worldcourts.com mobile page usability

Last tested: 2019-03-10

Mobile Usability Bad

58/100

worldcourts.com Mobile Usability Test Quick Summary

priority - 40Use 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.

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

TO REFINE YOUR…CHECK BOX(ES) and 2 others render only 6 pixels tall (16 CSS pixels).

| renders only 6 pixels tall (16 CSS pixels).

Committee on t…against Women and 35 others render only 6 pixels tall (16 CSS pixels).

(2199) and 33 others render only 6 pixels tall (16 CSS pixels).

terms & conditions and 2 others render only 5 pixels tall (13 CSS pixels).

priority - 28Size 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="index.htm">eng</a> and 1 others are close to other tap targets.

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

The tap target <input type="checkbox" name="zoom_cat[]"> and 35 others are close to other tap targets.

The tap target <a href="achpr/eng/index.htm">African Commis…eoples' Rights</a> and 54 others are close to other tap targets.

The tap target <a href="http://www.worldcourts.com">home</a> and 2 others are close to other tap targets.

priority - 10Configure 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.

worldcourts.com HTML validation

Errors

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

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

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 4 Column: 1 - 52
"...> <head> <meta http-equiv="Content-Language" content="en-us"> <meta..."

Internal encoding declaration “windows-1252” disagrees with the actual encoding of the document (“utf-8”).

Line: 5 Column: 1 - 74
"...="en-us"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <titl..."