wicourts.gov Website Information

Daily Unique Visits: 54,876

Daily Page Views: 329,256

Income Per Day: $659

Estimated Value: $474,480

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

wicourts.gov is registered under .GOV top-level domain. Please check other sites in .GOV zone.

Website wicourts.gov is using the following name servers:

dns.wicourts.gov
dns2.wicourts.gov

and is probably hosted by STATE-OF-WISCONSIN-AS1 - State of WI Dept. of Administration, US. See the full list of other websites hosted by STATE-OF-WISCONSIN-AS1 - State of WI Dept. of Administration, US.

The highest website wicourts.gov position in Alexa rank database was 25063 and the lowest rank position was 26589. Current position of wicourts.gov in Alexa rank database is 26136.

Desktop speed score of wicourts.gov (82/100) is better than the results of 74.03% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of wicourts.gov (62/100) is better than the results of 7.29% of other sites and means that the page is not mobile-friendly.

Mobile speed score of wicourts.gov (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.

wicourts.gov 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.

wicourts.gov 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.

% DOTGOV WHOIS Server ready
Domain Name: WICOURTS.GOV
Status: ACTIVE
Security Contact Email: Technical.Operations@wicourts.gov

>>> Last update of whois database: 2021-04-25T11:38:20Z

wicourts.gov server information

Servers Location

wicourts.gov desktop page speed rank

Last tested: 2019-12-08

Desktop Speed Medium

82/100

wicourts.gov Desktop Speed Test Quick Summary

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

https://wicourts.gov/SpryAssets/SpryTabbedPanels.css (expiration not specified)
https://wicourts.gov/SpryAssets/SpryTabbedPanels.js (expiration not specified)
https://wicourts.gov/css/master.css (expiration not specified)
https://wicourts.gov/css/navigation.css (expiration not specified)
https://wicourts.gov/css/print.css (expiration not specified)
https://wicourts.gov/images/backtab.png (expiration not specified)
https://wicourts.gov/images/cdpp_icon-01.png (expiration not specified)
https://wicourts.gov/images/chiefwelcome4.png (expiration not specified)
https://wicourts.gov/images/chiefwelcomebg.png (expiration not specified)
https://wicourts.gov/images/fronttab.png (expiration not specified)
https://wicourts.gov/images/header.png (expiration not specified)
https://wicourts.gov/images/magnifier.png (expiration not specified)
https://wicourts.gov/images/more.png (expiration not specified)
https://wicourts.gov/images/pdf.gif (expiration not specified)
https://wicourts.gov/images/slide-left-shorter.png (expiration not specified)
https://wicourts.gov/images/slide-right-shorter.png (expiration not specified)
https://wicourts.gov/js/dropdowntabs.js (expiration not specified)
https://wicourts.gov/type/ubuntu-b-webfont.woff (expiration not specified)
https://wicourts.gov/type/ubuntu-i-webfont.woff (expiration not specified)
https://wicourts.gov/type/ubuntu-r-webfont.woff (expiration not specified)
https://ssl.google-analytics.com/ga.js (2 hours)

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

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

Remove render-blocking JavaScript:

https://wicourts.gov/js/dropdowntabs.js
https://wicourts.gov/SpryAssets/SpryTabbedPanels.js

Optimize CSS Delivery of the following:

https://wicourts.gov/css/master.css
https://wicourts.gov/css/fonts.css
https://wicourts.gov/css/navigation.css
https://wicourts.gov/SpryAssets/SpryTabbedPanels.css

priority - 1Optimize images

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

Optimize the following images to reduce their size by 8.9KiB (77% reduction).

Compressing https://wicourts.gov/images/fronttab.png could save 2.8KiB (84% reduction).
Compressing https://wicourts.gov/images/more.png could save 2.8KiB (81% reduction).
Compressing https://wicourts.gov/images/backtab.png could save 2.4KiB (74% reduction).
Compressing https://wicourts.gov/images/pdf.gif could save 739B (82% reduction).
Compressing https://wicourts.gov/images/cdpp_icon-01.png could save 128B (24% reduction).

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

Minifying https://wicourts.gov/SpryAssets/SpryTabbedPanels.css could save 1.8KiB (76% reduction) after compression.
Minifying https://wicourts.gov/css/master.css could save 1.4KiB (30% reduction) after compression.
Minifying https://wicourts.gov/css/print.css could save 343B (31% reduction) after compression.
Minifying https://wicourts.gov/css/navigation.css could save 279B (28% reduction) after compression.

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

Minifying https://wicourts.gov/SpryAssets/SpryTabbedPanels.js could save 1.4KiB (44% reduction) after compression.
Minifying https://wicourts.gov/js/dropdowntabs.js could save 578B (27% reduction) after compression.

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 772B (14% reduction).

Minifying https://wicourts.gov/ could save 772B (14% reduction) after compression.

wicourts.gov Desktop Resource Breakdown

Total Resources	25
Number of Hosts	2
Static Resources	21
JavaScript Resources	3
CSS Resources	4

wicourts.gov mobile page speed rank

Last tested: 2019-12-07

Mobile Speed Medium

67/100

wicourts.gov Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

https://wicourts.gov/js/dropdowntabs.js
https://wicourts.gov/SpryAssets/SpryTabbedPanels.js

Optimize CSS Delivery of the following:

https://wicourts.gov/css/master.css
https://wicourts.gov/css/fonts.css
https://wicourts.gov/css/navigation.css
https://wicourts.gov/SpryAssets/SpryTabbedPanels.css

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

priority - 1Optimize images

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

Optimize the following images to reduce their size by 8.9KiB (77% reduction).

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

priority - 0Minify 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 2KiB (37% 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 772B (14% reduction).

Minifying https://wicourts.gov/ could save 772B (14% reduction) after compression.

wicourts.gov Mobile Resource Breakdown

Total Resources	25
Number of Hosts	2
Static Resources	21
JavaScript Resources	3
CSS Resources	4

wicourts.gov mobile page usability

Last tested: 2019-12-07

Mobile Usability Bad

62/100

wicourts.gov Mobile Usability Test Quick Summary

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

contact the court and 3 others render only 5 pixels tall (13 CSS pixels).

about the courts and 7 others render only 5 pixels tall (14 CSS pixels).

Recent Supreme Court opinions renders only 5 pixels tall (14 CSS pixels).

Justice Rebecc…opinion filed. and 11 others render only 5 pixels tall (12 CSS pixels).

State of Wisco…y J. Rodriguez and 9 others render only 5 pixels tall (12 CSS pixels).

The decision o…s is affirmed. and 1 others render only 5 pixels tall (12 CSS pixels).

news and events renders only 5 pixels tall (14 CSS pixels).

court closures and 2 others render only 5 pixels tall (14 CSS pixels).

Learn about the Commercial and 1 others render only 5 pixels tall (13 CSS pixels).

State of the J…, Nov. 6, 2019 and 8 others render only 5 pixels tall (14 CSS pixels).

October 18, 20…Appeals Access and 27 others render only 5 pixels tall (14 CSS pixels).

Supreme Court…Access website and 21 others render only 5 pixels tall (14 CSS pixels).

State of the Judiciary renders only 5 pixels tall (14 CSS pixels).

For more news items check the and 1 others render only 5 pixels tall (14 CSS pixels).

Updated: December 3, 2019 and 7 others render only 5 pixels tall (12 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 - 10Size 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="/contact/feedback.htm">contact the court</a> and 3 others are close to other tap targets.

The tap target <div id="headtitle">Wisconsin Court System</div> is close to 1 other tap targets.

The tap target <a href="/courts/index.htm">about the courts</a> and 6 others are close to other tap targets.

The tap target <img src="/images/magnifier.png"> is close to 2 other tap targets.

The tap target <li class="TabbedPanelsTab">court closures</li> is close to 1 other tap targets.

The tap target <a href="services/attor…courtpilot.htm" class="cdppButton">Learn about th…Pilot Project</a> is close to 1 other tap targets.

The tap target <a href="https://www.wi…/oac120919.pdf">here</a> and 15 others are close to other tap targets.

The tap target <a href="/siteindex.htm">a-z index</a> and 3 others are close to other tap targets.

priority - 6Size 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 1,000 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="/contact/feedback.htm">contact the court</a> falls outside the viewport.
The element <a href="/contact/directories.htm">directories</a> falls outside the viewport.
The element <a href="/courts/employment/index.jsp">employment</a> falls outside the viewport.
The element <a href="/news/index.htm">news</a> falls outside the viewport.
The element <img src="/images/magnifier.png"> falls outside the viewport.
The element <img src="images/chiefwelcome4.png"> falls outside the viewport.
The element <h4>Recent Supreme Court opinions</h4> falls outside the viewport.
The element <span class="opinion">12/03/19 - 201…opinion filed.</span> falls outside the viewport.
The element <a href="https://www.wi…f&seqNo=250724">State of Wisco…y J. Rodriguez</a> falls outside the viewport.
The element <a href="/staff/index.htm">court system staff</a> falls outside the viewport.
The element <p>Questions abou…cember 3, 2019</p> falls outside the viewport.

wicourts.gov HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

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

Line: 7 Column: 1 - 74
"... <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <titl..."

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: 7 Column: 1 - 74
"... <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <titl..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 13 Column: 1 - 67
"...n.css" /> <meta http-equiv="Content-Script-Type" content="text/javascript" /> <scri..."

Bad value “menu1” for attribute “rel” on element “a”: The string “menu1” is not a registered keyword.

Line: 68 Column: 7 - 46
"...ul> <li><a href="/courts/index.htm" rel="menu1"><span>..."

Bad value “menu2” for attribute “rel” on element “a”: The string “menu2” is not a registered keyword.

Line: 69 Column: 7 - 44
"...li> <li><a href="/casesearch.htm" rel="menu2"><span>..."

Bad value “menu3” for attribute “rel” on element “a”: The string “menu3” is not a registered keyword.

Line: 70 Column: 7 - 48
"...li> <li><a href="/opinions/index.htm" rel="menu3"><span>..."

Bad value “menu4” for attribute “rel” on element “a”: The string “menu4” is not a registered keyword.

Line: 71 Column: 7 - 47
"...li> <li><a href="/scrules/index.htm" rel="menu4"><span>..."

Bad value “menu5” for attribute “rel” on element “a”: The string “menu5” is not a registered keyword.

Line: 72 Column: 7 - 46
"...i> <li><a href="/forms1/index.htm" rel="menu5"><span>..."

Bad value “menu6” for attribute “rel” on element “a”: The string “menu6” is not a registered keyword.

Line: 73 Column: 7 - 48
"...li> <li><a href="/services/index.htm" rel="menu6"><span>..."

Bad value “menu7” for attribute “rel” on element “a”: The string “menu7” is not a registered keyword.

Line: 74 Column: 7 - 47
"...i> <li><a href="/ecourts/index.htm" rel="menu7"><span>..."

Bad value “menu8” for attribute “rel” on element “a”: The string “menu8” is not a registered keyword.

Line: 75 Column: 7 - 52
"...li> <li><a href="/publications/index.htm" rel="menu8"><span>..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 184 Column: 25 - 111
"...exright"> <img src="images/chiefwelcome4.png" width="240" height="90" border="0" usemap="#Map" /> <..."

Element “area” is missing required attribute “alt”.

Line: 186 Column: 7 - 66
"...p"> <area shape="rect" coords="1,4,236,86" href="message.htm" /> ..."

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

Line: 281 Column: 49 - 152
"...p?id=947"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 292 Column: 49 - 152
"...p?id=946"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 303 Column: 49 - 152
"...p?id=945"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 314 Column: 49 - 152
"...p?id=944"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 358 Column: 49 - 152
"...p?id=940"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..."

Warnings

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

Line: 184 Column: 25 - 111
"...exright"> <img src="images/chiefwelcome4.png" width="240" height="90" border="0" usemap="#Map" /> <..." Line: 281 Column: 49 - 152
"...p?id=947"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 292 Column: 49 - 152
"...p?id=946"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 303 Column: 49 - 152
"...p?id=945"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 314 Column: 49 - 152
"...p?id=944"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..." Line: 358 Column: 49 - 152
"...p?id=940"><img src="images/more.png" alt="see full article" width="20" height="20" border="0" align="absbottom" /></a> <..."

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

Line: 2 Column: 122 - 43
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <h..."

wicourts.gov similar domains

Similar domains:

www.wicourts.com
www.wicourts.net
www.wicourts.org
www.wicourts.info
www.wicourts.biz
www.wicourts.us
www.wicourts.mobi
www.icourts.gov
www.wicourts.gov
www.qicourts.gov
www.wqicourts.gov
www.qwicourts.gov
www.aicourts.gov
www.waicourts.gov
www.awicourts.gov
www.sicourts.gov
www.wsicourts.gov
www.swicourts.gov
www.eicourts.gov
www.weicourts.gov
www.ewicourts.gov
www.wcourts.gov
www.wucourts.gov
www.wiucourts.gov
www.wuicourts.gov
www.wjcourts.gov
www.wijcourts.gov
www.wjicourts.gov
www.wkcourts.gov
www.wikcourts.gov
www.wkicourts.gov
www.wocourts.gov
www.wiocourts.gov
www.woicourts.gov
www.wiourts.gov
www.wixourts.gov
www.wicxourts.gov
www.wixcourts.gov
www.widourts.gov
www.wicdourts.gov
www.widcourts.gov
www.wifourts.gov
www.wicfourts.gov
www.wifcourts.gov
www.wivourts.gov
www.wicvourts.gov
www.wivcourts.gov
www.wicurts.gov
www.wiciurts.gov
www.wicoiurts.gov
www.wiciourts.gov
www.wickurts.gov
www.wicokurts.gov
www.wickourts.gov
www.wiclurts.gov
www.wicolurts.gov
www.wiclourts.gov
www.wicpurts.gov
www.wicopurts.gov
www.wicpourts.gov
www.wicorts.gov
www.wicoyrts.gov
www.wicouyrts.gov
www.wicoyurts.gov
www.wicohrts.gov
www.wicouhrts.gov
www.wicohurts.gov
www.wicojrts.gov
www.wicoujrts.gov
www.wicojurts.gov
www.wicoirts.gov
www.wicouirts.gov
www.wicouts.gov
www.wicouets.gov
www.wicourets.gov
www.wicouerts.gov
www.wicoudts.gov
www.wicourdts.gov
www.wicoudrts.gov
www.wicoufts.gov
www.wicourfts.gov
www.wicoufrts.gov
www.wicoutts.gov
www.wicourtts.gov
www.wicoutrts.gov
www.wicours.gov
www.wicourrs.gov
www.wicourtrs.gov
www.wicourrts.gov
www.wicourfs.gov
www.wicourtfs.gov
www.wicourgs.gov
www.wicourtgs.gov
www.wicourgts.gov
www.wicourys.gov
www.wicourtys.gov
www.wicouryts.gov
www.wicourt.gov
www.wicourtw.gov
www.wicourtsw.gov
www.wicourtws.gov
www.wicourte.gov
www.wicourtse.gov
www.wicourtes.gov
www.wicourtd.gov
www.wicourtsd.gov
www.wicourtds.gov
www.wicourtz.gov
www.wicourtsz.gov
www.wicourtzs.gov
www.wicourtx.gov
www.wicourtsx.gov
www.wicourtxs.gov
www.wicourta.gov
www.wicourtsa.gov
www.wicourtas.gov

wicourts.gov 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.

wicourts.gov 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.

WICOURTS.GOV Wisconsin Court System -

wicourts.gov Website Information

Advertisement

wicourts.gov Alexa Rank

wicourts.gov whois

wicourts.gov server information

Servers Location

wicourts.gov desktop page speed rank

wicourts.gov Desktop Speed Test Quick Summary

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

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 1Optimize images

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

Optimize the following images to reduce their size by 8.9KiB (77% reduction).

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

priority - 0Minify 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 2KiB (37% 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 772B (14% reduction).

wicourts.gov Desktop Resource Breakdown

wicourts.gov mobile page speed rank

wicourts.gov Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

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

priority - 1Optimize images

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

Optimize the following images to reduce their size by 8.9KiB (77% reduction).

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

priority - 0Minify 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 2KiB (37% 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 772B (14% reduction).

wicourts.gov Mobile Resource Breakdown

wicourts.gov mobile page usability

wicourts.gov Mobile Usability Test Quick Summary

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

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 - 10Size 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.

priority - 6Size 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 1,000 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

wicourts.gov HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

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

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

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Bad value “menu1” for attribute “rel” on element “a”: The string “menu1” is not a registered keyword.

Bad value “menu2” for attribute “rel” on element “a”: The string “menu2” is not a registered keyword.

Bad value “menu3” for attribute “rel” on element “a”: The string “menu3” is not a registered keyword.

Bad value “menu4” for attribute “rel” on element “a”: The string “menu4” is not a registered keyword.

Bad value “menu5” for attribute “rel” on element “a”: The string “menu5” is not a registered keyword.

Bad value “menu6” for attribute “rel” on element “a”: The string “menu6” is not a registered keyword.

Bad value “menu7” for attribute “rel” on element “a”: The string “menu7” is not a registered keyword.

Bad value “menu8” for attribute “rel” on element “a”: The string “menu8” is not a registered keyword.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Element “area” is missing required attribute “alt”.