SUPREMELAW.ORG Supreme Law Firm

supremelaw.org Website Information

Daily Unique Visits: 2,264

Daily Page Views: 6,792

Income Per Day: $20

Estimated Value: $7,200

This website is located in Sweden and is using following IP address 93.90.146.107. See the complete list of popular websites hosted in Sweden.

supremelaw.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

Website supremelaw.org is using the following name servers:

  • ns05.servage.net
  • ns01.servage.net
  • ns04.servage.net
  • ns02.servage.net
  • ns03.servage.net

and is probably hosted by Loopia AB. See the full list of other websites hosted by Loopia AB.

The highest website supremelaw.org position in Alexa rank database was 28539 and the lowest rank position was 998976. Current position of supremelaw.org in Alexa rank database is 475102.

Desktop speed score of supremelaw.org (97/100) is better than the results of 95.04% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of supremelaw.org (66/100) is better than the results of 14.96% of other sites and means that the page is not mobile-friendly.

Mobile speed score of supremelaw.org (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.

Advertisement

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


supremelaw.org 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: supremelaw.org
Registry Domain ID: e12c3c939c8c4a68ae8fa41103da6a82-LROR
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2022-03-24T08:17:15Z
Creation Date: 2001-03-31T02:45:12Z
Registry Expiry Date: 2023-03-31T02:45:12Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email: abuse@enom.com
Registrar Abuse Contact Phone: +1.4252982646
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Whois Privacy Protection Service, Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: WA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns01.servage.net
Name Server: ns02.servage.net
Name Server: ns03.servage.net
Name Server: ns04.servage.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-07-01T00:42:57Z

supremelaw.org server information

Servers Location

supremelaw.org desktop page speed rank

Last tested: 2019-07-03


Desktop Speed Good
97/100

supremelaw.org 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://supremelaw.org/background.gif (expiration not specified)
http://supremelaw.org/spacer.gif (expiration not specified)

priority - 1Enable 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 5.9KiB (63% reduction).

Compressing http://supremelaw.org/ could save 5.9KiB (63% 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 2.3KiB (25% reduction).

Minifying http://supremelaw.org/ could save 2.3KiB (25% reduction).

priority - 0Optimize images

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

Optimize the following images to reduce their size by 149B (25% reduction).

Compressing http://supremelaw.org/background.gif could save 149B (25% reduction).

supremelaw.org Desktop Resource Breakdown

Total Resources3
Number of Hosts1
Static Resources2

supremelaw.org mobile page speed rank

Last tested: 2019-11-28


Mobile Speed Good
97/100

supremelaw.org 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:

http://supremelaw.org/background.gif (expiration not specified)
http://supremelaw.org/spacer.gif (expiration not specified)

priority - 1Enable 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 5.9KiB (63% reduction).

Compressing http://supremelaw.org/ could save 5.9KiB (63% 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 2.3KiB (25% reduction).

Minifying http://supremelaw.org/ could save 2.3KiB (25% reduction).

priority - 0Optimize images

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

Optimize the following images to reduce their size by 149B (25% reduction).

Compressing http://supremelaw.org/background.gif could save 149B (25% reduction).

supremelaw.org Mobile Resource Breakdown

Total Resources3
Number of Hosts1
Static Resources2

supremelaw.org mobile page usability

Last tested: 2019-11-28


Mobile Usability Medium
66/100

supremelaw.org Mobile Usability Test Quick Summary


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

All Rights Res…hout Prejudice renders only 7 pixels tall (18 CSS pixels).

The Federal…ternal Revenue and 35 others render only 6 pixels tall (16 CSS pixels).

Judging from t…tal libraries. and 42 others render only 6 pixels tall (16 CSS pixels).

31 Questions a…about the IRS and 1 others render only 6 pixels tall (16 CSS pixels).

answers to que…lease read our and 2 others render only 6 pixels tall (16 CSS pixels).

pro bono and 1 others render only 6 pixels tall (16 CSS pixels).

support policy renders only 6 pixels tall (16 CSS pixels).

et al. and 2 others render only 6 pixels tall (16 CSS pixels).

A.D. and 2 others render only 6 pixels tall (16 CSS pixels).

, Mitchell has…umented in his and 3 others render only 6 pixels tall (16 CSS pixels).

[Home]   [ and 6 others render only 6 pixels tall (16 CSS pixels).
Contact Us and 6 others render only 6 pixels tall (16 CSS pixels).
Common Law renders only 6 pixels tall (16 CSS pixels).
P.O. Box 3097 and 4 others render only 6 pixels tall (16 CSS pixels).
Last Update:   January 1, 2017 and 3 others render only 6 pixels tall (16 CSS pixels).
A.D. and 1 others render only 6 pixels tall (16 CSS pixels).
Supreme Law Firm renders only 6 pixels tall (16 CSS pixels).

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.

priority - 3Size 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="egroups/donate.htm">Make a…Donation</a> and 14 others are close to other tap targets.

The tap target <a href="contact.htm">Contact Us</a> and 5 others are close to other tap targets.

supremelaw.org HTML validation

Errors

Quirky doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 49
"...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <!--l..."

Bogus comment.

Line: 7 Column: - 3
"...ML> <HEAD> <! -- There shoul..."

Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).

Line: 9 Column: 4 - 74
".... --> <META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1"> <T..."

Bad value “text/html;CHARSET=iso-8859-1” for attribute “content” on element “meta”: “iso-8859-1” is not a preferred encoding name. The preferred label for this encoding is “windows-1252”.

Line: 9 Column: 4 - 74
".... --> <META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1"> <T..."

The “background” attribute on the “body” element is obsolete. Use CSS instead.

Line: 15 Column: 1 - 52
"...</HEAD> <BODY BACKGROUND="background.gif" BGCOLOR="#FFFFFF"> <P><..."

The “bgcolor” attribute on the “body” element is obsolete. Use CSS instead.

Line: 15 Column: 1 - 52
"...</HEAD> <BODY BACKGROUND="background.gif" BGCOLOR="#FFFFFF"> <P><..."

Element “table” not allowed as child of element “p” in this context. (Suppressing further errors from this subtree.)

Line: 18 Column: 1 - 46
"...Table--> <TABLE BORDER="0" CELLPADDING="0" WIDTH="550"> <TR>..."

The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.

Line: 18 Column: 1 - 46
"...Table--> <TABLE BORDER="0" CELLPADDING="0" WIDTH="550"> <TR>..." Line: 41 Column: 4 - 65
"... <P> <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="5" WIDTH="80%"> <..."

The “width” attribute on the “table” element is obsolete. Use CSS instead.

Line: 18 Column: 1 - 46
"...Table--> <TABLE BORDER="0" CELLPADDING="0" WIDTH="550"> <TR>..." Line: 41 Column: 4 - 65
"... <P> <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="5" WIDTH="80%"> <..."

The “border” attribute on the “table” element is obsolete. Use CSS instead.

Line: 18 Column: 1 - 46
"...Table--> <TABLE BORDER="0" CELLPADDING="0" WIDTH="550"> <TR>..." Line: 41 Column: 4 - 65
"... <P> <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="5" WIDTH="80%"> <..."

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Line: 20 Column: 6 - 31
"...50"> <TR> <TD WIDTH="120" VALIGN="TOP"><IMG S..." Line: 23 Column: 11 - 46
"... </TD> <TD WIDTH="450" ALIGN="CENTER" VALIGN="TOP"> <!--<..." Line: 38 Column: 6 - 44
".../TR> <TR> <TD WIDTH="120" ALIGN="LEFT" VALIGN="TOP"> <!--S..." Line: 43 Column: 9 - 57
"...> <TR> <TD WIDTH="100%"> ..." Line: 70 Column: 8 - 18
"...> </TD> <TD WIDTH="450"> <P..."

The “valign” attribute on the “td” element is obsolete. Use CSS instead.

Line: 20 Column: 6 - 31
"...50"> <TR> <TD WIDTH="120" VALIGN="TOP"><IMG S..." Line: 23 Column: 11 - 46
"... </TD> <TD WIDTH="450" ALIGN="CENTER" VALIGN="TOP"> <!--<..." Line: 38 Column: 6 - 44
".../TR> <TR> <TD WIDTH="120" ALIGN="LEFT" VALIGN="TOP"> <!--S..."

The “align” attribute on the “img” element is obsolete. Use CSS instead.

Line: 20 Column: 32 - 117
"...IGN="TOP"><IMG SRC="spacer.gif" WIDTH="110" HEIGHT="30" ALIGN="BOTTOM" ALT="sidebar" BORDER="0"> <B..."

The “clear” attribute on the “br” element is obsolete. Use CSS instead.

Line: 21 Column: 4 - 21
"...R="0"> <BR clear = "all"> ..."

The “align” attribute on the “td” element is obsolete. Use CSS instead.

Line: 23 Column: 11 - 46
"... </TD> <TD WIDTH="450" ALIGN="CENTER" VALIGN="TOP"> <!--<..." Line: 38 Column: 6 - 44
".../TR> <TR> <TD WIDTH="120" ALIGN="LEFT" VALIGN="TOP"> <!--S..."

The “center” element is obsolete. Use CSS instead.

Line: 25 Column: 4 - 11
"...o">--> <CENTER> <P..." Line: 30 Column: 4 - 11
"...ENTER> <CENTER> <FONT..." Line: 141 Column: 1 - 8
"...DE> </P> <CENTER> <P> [..." Line: 150 Column: 1 - 8
"...NOSHADE> <CENTER> <b><a..." Line: 162 Column: 1 - 8
".../CENTER> <center> <b><..."

The “noshade” attribute on the “hr” element is obsolete. Use CSS instead.

Line: 27 Column: 1 - 12
"...R> <P> <HR NOSHADE> </CE..." Line: 33 Column: 1 - 24
"...B></FONT> <HR WIDTH="90%" NOSHADE> </CEN..." Line: 98 Column: 1 - 12
"...> <P> <HR NOSHADE> ..." Line: 138 Column: 1 - 21
"...-> <P> <HR SIZE="1" NOSHADE> </P> ..." Line: 148 Column: 1 - 21
"...R> <P> <HR SIZE="1" NOSHADE> <CEN..." Line: 158 Column: 1 - 21
"...>A.D.</i> <HR SIZE="1" NOSHADE> <BR> ..."

The “font” element is obsolete. Use CSS instead.

Line: 31 Column: 1 - 15
"... <CENTER> <FONT SIZE="6"><B>Sup..." Line: 32 Column: 1 - 15
"...FONT><BR> <FONT SIZE="4"><B>All..." Line: 78 Column: 75 - 93
"...sic book "<font color="red""><b>The..." Line: 79 Column: 94 - 111
"... popular "<font color="red"><b>31 ..."

The “width” attribute on the “hr” element is obsolete. Use CSS instead.

Line: 33 Column: 1 - 24
"...B></FONT> <HR WIDTH="90%" NOSHADE> </CEN..."

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.

Line: 41 Column: 4 - 65
"... <P> <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="5" WIDTH="80%"> <..."

No space between attributes.

Line: 78 Column: - 92
"...ont color="red""><b>The Federa..."

Saw “"” when expecting an attribute name. Probable cause: “=” missing immediately before.

Line: 78 Column: - 92
"...ont color="red""><b>The Federa..."

No “p” element in scope but a “p” end tag seen.

Line: 130 Column: 351 - 354
"...LY briefs.</p> ..." Line: 139 Column: 1 - 4
"... NOSHADE> </P> <CEN..."

Stray end tag “blockquot”.

Line: 134 Column: 4 - 15
"...aries. </BLOCKQUOT> <!--..."

The “size” attribute on the “hr” element is obsolete. Use CSS instead.

Line: 138 Column: 1 - 21
"...-> <P> <HR SIZE="1" NOSHADE> </P> ..." Line: 148 Column: 1 - 21
"...R> <P> <HR SIZE="1" NOSHADE> <CEN..." Line: 158 Column: 1 - 21
"...>A.D.</i> <HR SIZE="1" NOSHADE> <BR> ..."

End tag “td” seen, but there were open elements.

Line: 172 Column: 3 - 7
"...enter> </TD> </T..."

Unclosed element “blockquote”.

Line: 102 Column: 4 - 15
"...DE> <BLOCKQUOTE> ..."

Warnings

The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

Line: 7 Column: - 5
"...> <HEAD> <! -- There should ..." Line: 7 Column: - 44
"...ASCRIPT here. --> <META HT..."

The document is not mappable to XML 1.0 due to a trailing hyphen in a comment.

Line: 7 Column: - 45
"...SCRIPT here. --> <META HTT..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 20 Column: 32 - 117
"...IGN="TOP"><IMG SRC="spacer.gif" WIDTH="110" HEIGHT="30" ALIGN="BOTTOM" ALT="sidebar" BORDER="0"> <B..."

Attribute “"” is not serializable as XML 1.0.

Line: 78 Column: 75 - 93
"...sic book "<font color="red""><b>The..."

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

Line: 82 Column: 25 - 42
"... <a name="probono"></a> ..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 3 Column: 58 - 6
"...7:35 PM--> <HTML> <HEA..."

supremelaw.org similar domains

Similar domains:
www.supremelaw.com
www.supremelaw.net
www.supremelaw.org
www.supremelaw.info
www.supremelaw.biz
www.supremelaw.us
www.supremelaw.mobi
www.upremelaw.org
www.supremelaw.org
www.wupremelaw.org
www.swupremelaw.org
www.wsupremelaw.org
www.eupremelaw.org
www.seupremelaw.org
www.esupremelaw.org
www.dupremelaw.org
www.sdupremelaw.org
www.dsupremelaw.org
www.zupremelaw.org
www.szupremelaw.org
www.zsupremelaw.org
www.xupremelaw.org
www.sxupremelaw.org
www.xsupremelaw.org
www.aupremelaw.org
www.saupremelaw.org
www.asupremelaw.org
www.spremelaw.org
www.sypremelaw.org
www.suypremelaw.org
www.syupremelaw.org
www.shpremelaw.org
www.suhpremelaw.org
www.shupremelaw.org
www.sjpremelaw.org
www.sujpremelaw.org
www.sjupremelaw.org
www.sipremelaw.org
www.suipremelaw.org
www.siupremelaw.org
www.suremelaw.org
www.suoremelaw.org
www.suporemelaw.org
www.suopremelaw.org
www.sulremelaw.org
www.suplremelaw.org
www.sulpremelaw.org
www.supemelaw.org
www.supeemelaw.org
www.supreemelaw.org
www.superemelaw.org
www.supdemelaw.org
www.suprdemelaw.org
www.supdremelaw.org
www.supfemelaw.org
www.suprfemelaw.org
www.supfremelaw.org
www.suptemelaw.org
www.suprtemelaw.org
www.suptremelaw.org
www.suprmelaw.org
www.suprwmelaw.org
www.suprewmelaw.org
www.suprwemelaw.org
www.suprsmelaw.org
www.supresmelaw.org
www.suprsemelaw.org
www.suprdmelaw.org
www.supredmelaw.org
www.suprrmelaw.org
www.suprermelaw.org
www.suprremelaw.org
www.supreelaw.org
www.suprenelaw.org
www.supremnelaw.org
www.suprenmelaw.org
www.suprejelaw.org
www.supremjelaw.org
www.suprejmelaw.org
www.suprekelaw.org
www.supremkelaw.org
www.suprekmelaw.org
www.supremlaw.org
www.supremwlaw.org
www.supremewlaw.org
www.supremwelaw.org
www.supremslaw.org
www.supremeslaw.org
www.supremselaw.org
www.supremdlaw.org
www.supremedlaw.org
www.supremdelaw.org
www.supremrlaw.org
www.supremerlaw.org
www.supremrelaw.org
www.supremeaw.org
www.supremepaw.org
www.supremelpaw.org
www.supremeplaw.org
www.supremeoaw.org
www.supremeloaw.org
www.supremeolaw.org
www.supremekaw.org
www.supremelkaw.org
www.supremeklaw.org
www.supremelw.org
www.supremelqw.org
www.supremelaqw.org
www.supremelqaw.org
www.supremelww.org
www.supremelaww.org
www.supremelwaw.org
www.supremelsw.org
www.supremelasw.org
www.supremelsaw.org
www.supremelzw.org
www.supremelazw.org
www.supremelzaw.org
www.supremela.org
www.supremelaq.org
www.supremelawq.org
www.supremelaa.org
www.supremelawa.org
www.supremelaaw.org
www.supremelas.org
www.supremelaws.org
www.supremelae.org
www.supremelawe.org
www.supremelaew.org

supremelaw.org Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


supremelaw.org TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.