ODCR.COM On Demand Court Records

odcr.com Website Information

Daily Unique Visits: 1,419

Daily Page Views: 2,838

Income Per Day: $9

Estimated Value: $2,160

This website is located in United States and is using following IP address 96.45.82.91. See the complete list of popular websites hosted in United States.

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

Website odcr.com is using the following name servers:

  • ns11.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com
  • ns10.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com

and is probably hosted by ATT-INTERNET4 - AT&T Services, Inc., US. See the full list of other websites hosted by ATT-INTERNET4 - AT&T Services, Inc., US.

The highest website odcr.com position in Alexa rank database was 71846 and the lowest rank position was 942203. Current position of odcr.com in Alexa rank database is 505501.

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

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

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

Advertisement

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


odcr.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: ODCR.COM
Registry Domain ID: 89368787_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2023-08-16T12:09:12Z
Creation Date: 2002-08-15T16:14:10Z
Registry Expiry Date: 2025-08-15T16:14:10Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS10.DNSMADEEASY.COM
Name Server: NS11.DNSMADEEASY.COM
Name Server: NS12.DNSMADEEASY.COM
Name Server: NS13.DNSMADEEASY.COM
Name Server: NS14.DNSMADEEASY.COM
Name Server: NS15.DNSMADEEASY.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-11-03T20:39:49Z

odcr.com server information

Servers Location

odcr.com desktop page speed rank

Last tested: 2017-12-16


Desktop Speed Good
89/100

odcr.com Desktop Speed Test Quick Summary


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

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

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Coda+Caption:800
http://www1.odcr.com/styles/compiled/application.css?cache-bust=3

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 13.7KiB (36% reduction).

Minifying http://www1.odcr.com/javascripts/jquery/qtip.js could save 12.3KiB (41% reduction) after compression.
Minifying http://www1.odcr.com/javascripts/application.js?bu…4077-85f4-efde7fdd4127 could save 1.4KiB (17% reduction) after compression.

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://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 0Optimize images

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

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

Compressing http://www1.odcr.com/images/advertisements/okcr-advertisement.png could save 3.1KiB (17% 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 985B (13% reduction).

Minifying http://www1.odcr.com/ could save 985B (13% reduction) after compression.

odcr.com Desktop Resource Breakdown

Total Resources32
Number of Hosts9
Static Resources24
JavaScript Resources13
CSS Resources3

odcr.com mobile page speed rank

Last tested: 2017-11-30


Mobile Speed Medium
67/100

odcr.com Mobile Speed Test Quick Summary


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

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

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Coda+Caption:800
http://www1.odcr.com/styles/compiled/application.css?cache-bust=3

priority - 11Reduce server response time

priority - 4Optimize images

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

Optimize the following images to reduce their size by 38KiB (34% reduction).

Compressing https://tpc.googlesyndication.com/daca_images/simgad/9819911660680812427 could save 33.5KiB (33% reduction).
Compressing http://www1.odcr.com/images/advertisements/41480-1383759624.png could save 4.5KiB (52% reduction).

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 13.7KiB (36% reduction).

Minifying http://www1.odcr.com/javascripts/jquery/qtip.js could save 12.3KiB (41% reduction) after compression.
Minifying http://www1.odcr.com/javascripts/application.js?bu…4077-85f4-efde7fdd4127 could save 1.4KiB (17% reduction) after compression.

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://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

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.1KiB (14% reduction).

Minifying http://www1.odcr.com/ could save 1.1KiB (14% reduction) after compression.

odcr.com Mobile Resource Breakdown

Total Resources45
Number of Hosts11
Static Resources33
JavaScript Resources19
CSS Resources3

odcr.com mobile page usability

Last tested: 2017-11-30


Mobile Usability Medium
75/100

odcr.com Mobile Usability Test Quick Summary


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

Pricing and 2 others render only 5 pixels tall (13 CSS pixels).

Full case number and 6 others render only 5 pixels tall (14 CSS pixels).

Plaintiffs & Defendants and 1 others render only 5 pixels tall (13 CSS pixels).

Last, First renders only 5 pixels tall (13 CSS pixels).

Select a Case Type... renders only 5 pixels tall (13 CSS pixels).

to renders only 5 pixels tall (14 CSS pixels).

or renders only 5 pixels tall (13 CSS pixels).

Reset all of the fields renders only 5 pixels tall (13 CSS pixels).

Work Smarter.…ross Oklahoma! renders only 5 pixels tall (12 CSS pixels).

Court Update Information renders only 8 pixels tall (20 CSS pixels).

New records ar…ate regularly. and 1 others render only 5 pixels tall (13 CSS pixels).

View the full list of courts renders only 5 pixels tall (13 CSS pixels).

courts up to date and 1 others render only 5 pixels tall (13 CSS pixels).

Contact Us renders only 6 pixels tall (16 CSS pixels).

Advertise your business renders only 6 pixels tall (16 CSS pixels).

Like us on Facebook renders only 6 pixels tall (16 CSS pixels).

Follow us on Twitter renders only 6 pixels tall (16 CSS pixels).

© renders only 5 pixels tall (14 CSS pixels).

2017 - renders only 5 pixels tall (14 CSS pixels).

Terms of Service and 1 others render only 5 pixels tall (14 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 - 4Size 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 <input id="search-party" type="text" name="party"> is close to 2 other tap targets.

The tap target <div id="search_party_type_chzn" class="chzn-container…ntainer-single">Plaintiffs &amp; D…ntsAll Parties</div> and 3 others are close to other tap targets.

The tap target <a href="javascript:void(0)" class="chzn-single">Plaintiffs &amp; Defendants</a> is close to 1 other tap targets.

The tap target <a href="javascript:void(0)" class="chzn-single chzn-default">Select a Case Type...</a> and 2 others are close to other tap targets.

The tap target <input id="search-case-number-number" type="text" name="case-number-number"> is close to 2 other tap targets.

The tap target <input id="search-filed-start" type="date" name="filed-start"> and 1 others are close to other tap targets.

The tap target <a href="http://faceboo…ndCourtRecords" class="facebook">Like us on Facebook</a> is close to 1 other tap targets.

The tap target <a href="http://twitter.com/kellpro" class="twitter">Follow us on Twitter</a> is close to 1 other tap targets.

The tap target <a href="http://www.kellpro.com">KellPro, Inc.</a> and 1 others are close to other tap targets.

odcr.com HTML validation

Errors

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 5 Column: 2 - 57
"...</title> <meta http-equiv="X-UA-Compatible" content="chrome=IE8"> <lin..."

Element “option” without attribute “label” must not be empty.

Line: 284 Column: 23 - 31
"... value=""></option> ..." Line: 401 Column: 23 - 31
"... value=""></option> ..." Line: 1290 Column: 23 - 31
"... value=""></option> ..."

Warnings

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Line: 61 Column: 3 - 6
"...arfix"> <h1>Search..."

The “date” input type is not supported in all browsers. Please be sure to test, and consider using a polyfill.

Line: 1500 Column: 5 - 66
"...abel> <input type="date" name="filed-start" id="search-filed-start"> t..." Line: 1502 Column: 5 - 62
"... to <input type="date" name="filed-end" id="search-filed-end"> ..." Line: 1508 Column: 5 - 60
"...abel> <input type="date" name="activity" id="search-activity"> ..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 1528 Column: 4 - 12
"...info"> <section> <..." Line: 1537 Column: 4 - 12
"...ction> <section> <..." Line: 1527 Column: 3 - 39
"... </p> <section id="main-court-status-info"> <s..." Line: 53 Column: 1 - 36
"...ntainer"> <section id="search-form-container"> <sec..."

odcr.com similar domains

Similar domains:
www.odcr.com
www.odcr.net
www.odcr.org
www.odcr.info
www.odcr.biz
www.odcr.us
www.odcr.mobi
www.dcr.com
www.odcr.com
www.idcr.com
www.oidcr.com
www.iodcr.com
www.kdcr.com
www.okdcr.com
www.kodcr.com
www.ldcr.com
www.oldcr.com
www.lodcr.com
www.pdcr.com
www.opdcr.com
www.podcr.com
www.ocr.com
www.oxcr.com
www.odxcr.com
www.oxdcr.com
www.oscr.com
www.odscr.com
www.osdcr.com
www.oecr.com
www.odecr.com
www.oedcr.com
www.orcr.com
www.odrcr.com
www.ordcr.com
www.ofcr.com
www.odfcr.com
www.ofdcr.com
www.occr.com
www.odccr.com
www.ocdcr.com
www.odr.com
www.odxr.com
www.odcxr.com
www.oddr.com
www.odcdr.com
www.oddcr.com
www.odfr.com
www.odcfr.com
www.odvr.com
www.odcvr.com
www.odvcr.com
www.odc.com
www.odce.com
www.odcre.com
www.odcer.com
www.odcd.com
www.odcrd.com
www.odcf.com
www.odcrf.com
www.odct.com
www.odcrt.com
www.odctr.com
www.odcr.con

odcr.com 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.


odcr.com 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.