wida.us Website Information

Daily Unique Visits: 2,228

Daily Page Views: 6,684

Income Per Day: $20

Estimated Value: $7,200

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

wida.us is registered under .US top-level domain. Please check other sites in .US zone.

Website wida.us is using the following name servers:

ns10.worldnic.com
ns9.worldnic.com

and is probably hosted by WISC-MADISON-AS - University of Wisconsin Madison, US. See the full list of other websites hosted by WISC-MADISON-AS - University of Wisconsin Madison, US.

The highest website wida.us position in Alexa rank database was 26118 and the lowest rank position was 980286. Current position of wida.us in Alexa rank database is 482784.

Desktop speed score of wida.us (75/100) is better than the results of 59.78% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of wida.us (63/100) is better than the results of 9.16% of other sites and means that the page is not mobile-friendly.

Mobile speed score of wida.us (57/100) is better than the results of 48.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

wida.us 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.

wida.us 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: wida.us
Registry Domain ID: D4904821-US
Registrar WHOIS Server:
Registrar URL: whois.biz
Updated Date: 2023-09-23T15:56:55Z
Creation Date: 2003-10-24T18:57:35Z
Registry Expiry Date: 2025-10-23T23:59:59Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: renewPeriod https://icann.org/epp#renewPeriod
Registry Registrant ID: C06882E884A0549C1B4F72861ED75D5C8-NSR
Registrant Name: Univ of WI-Madison, WCER Univ of WI-Madison, WCER
Registrant Organization: Univ of WI-Madison, WCER
Registrant Street: 1025 W JOHNSON ST RM 370
Registrant Street:
Registrant Street:
Registrant City: MADISON
Registrant State/Province: WI
Registrant Postal Code: 53706-1706
Registrant Country: US
Registrant Phone: +1.6082634333
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: purchasing@wcer.wisc.edu
Registrant Application Purpose: P2
Registrant Nexus Category: C32/US
Registry Admin ID: C552D85013ED84C38AA86834A8FEBA00B-NSR
Admin Name: WCER Infrastructure
Admin Organization: Univ of WI-Madison, WCER
Admin Street: 1025 W JOHNSON ST STE 370
Admin Street: Suite 370
Admin Street:
Admin City: Madison
Admin State/Province: WI
Admin Postal Code: 53706-1706
Admin Country: US
Admin Phone: +1.6082634333
Admin Phone Ext:
Admin Fax: +1.8886429675
Admin Fax Ext:
Admin Email: infrastructure@wcer.wisc.edu
Registry Tech ID: C552D85013ED84C38AA86834A8FEBA00B-NSR
Tech Name: WCER Infrastructure
Tech Organization: Univ of WI-Madison, WCER
Tech Street: 1025 W JOHNSON ST STE 370
Tech Street: Suite 370
Tech Street:
Tech City: Madison
Tech State/Province: WI
Tech Postal Code: 53706-1706
Tech Country: US
Tech Phone: +1.6082634333
Tech Phone Ext:
Tech Fax: +1.8886429675
Tech Fax Ext:
Tech Email: infrastructure@wcer.wisc.edu
Name Server: ns1-04.azure-dns.com
Name Server: ns4-04.azure-dns.info
Name Server: ns2-04.azure-dns.net
Name Server: ns3-04.azure-dns.org
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-10-19T00:01:38Z

wida.us server information

Servers Location

wida.us desktop page speed rank

Last tested: 2018-07-01

Desktop Speed Medium

75/100

wida.us Desktop Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

https://www.wida.us/WebResource.axd?d=pynGkmcFUV13…2&t=636475798140000000
https://www.wida.us/WebResource.axd?d=x2nkrMJGXkME…1&t=636475798140000000

Optimize CSS Delivery of the following:

https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css
https://www.wida.us/styles/bootstrap2-min.css
https://www.wida.us/styles/template-min.css
https://fonts.googleapis.com/css?family=Open+Sans:400,600,700
https://www.wida.us/styles/insidePages-min.css
https://www.wida.us/styles/homePage-min.css

priority - 12Leverage 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://www.googletagmanager.com/gtm.js?id=GTM-PWQG4GZ (15 minutes)
https://cse.google.com/adsense/search/async-ads.js (60 minutes)
https://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://d2oh4tlt9mrke9.cloudfront.net/Record/js/sessioncam.recorder.js (4 hours)
https://www.wida.us/images/2018-Registration_Open.png (24 hours)
https://www.wida.us/images/2018SummerWorkshops.png (24 hours)
https://www.wida.us/images/2018_Score_Report_Banner.png (24 hours)
https://www.wida.us/images/WIDA%20logo.png (24 hours)
https://www.wida.us/images/blogger.gif (24 hours)
https://www.wida.us/images/divider.jpg (24 hours)
https://www.wida.us/images/downloadLibrary.jpg (24 hours)
https://www.wida.us/images/facebook.gif (24 hours)
https://www.wida.us/images/linkedIn.gif (24 hours)
https://www.wida.us/images/mapIcon.jpg (24 hours)
https://www.wida.us/images/moreArrow.gif (24 hours)
https://www.wida.us/images/nav_background.jpg (24 hours)
https://www.wida.us/images/news_line.gif (24 hours)
https://www.wida.us/images/online.png (24 hours)
https://www.wida.us/images/onlineStore.jpg (24 hours)
https://www.wida.us/images/subscribe.gif (24 hours)
https://www.wida.us/images/twitter.gif (24 hours)
https://www.wida.us/scripts/main.js (24 hours)
https://www.wida.us/styles/bootstrap2-min.css (24 hours)
https://www.wida.us/styles/homePage-min.css (24 hours)
https://www.wida.us/styles/insidePages-min.css (24 hours)
https://www.wida.us/styles/template-min.css (24 hours)

priority - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (37% reduction).

Compressing https://www.wida.us/images/2018_Score_Report_Banner.png could save 22.2KiB (23% reduction).
Compressing https://www.wida.us/images/mapIcon.jpg could save 21.6KiB (84% reduction).
Compressing https://www.wida.us/images/divider.jpg could save 8.1KiB (86% reduction).
Compressing https://www.wida.us/images/WIDA%20logo.png could save 3.5KiB (33% reduction).
Compressing https://www.wida.us/images/onlineStore.jpg could save 1.2KiB (15% reduction).
Compressing https://www.wida.us/images/blogger.gif could save 1.1KiB (56% reduction).
Compressing https://www.wida.us/images/downloadLibrary.jpg could save 669B (18% 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 4.5KiB (35% reduction).

Minifying https://www.google.com/uds/api/search/1.0/4aa07721…f2bca15/default+en.css could save 3.9KiB (40% reduction) after compression.
Minifying https://www.google.com/cse/static/style/look/v2/default.css could save 578B (19% 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 1.6KiB (16% reduction).

Minifying https://www.wida.us/WebResource.axd?d=x2nkrMJGXkME…1&t=636475798140000000 could save 778B (15% reduction) after compression.
Minifying https://www.wida.us/WebResource.axd?d=pynGkmcFUV13…2&t=636475798140000000 could save 620B (14% reduction) after compression.
Minifying https://www.wida.us/scripts/main.js could save 256B (39% 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 1.4KiB (20% reduction).

Minifying https://www.wida.us/ could save 1.4KiB (20% reduction) after compression.

wida.us Desktop Resource Breakdown

Total Resources	52
Number of Hosts	17
Static Resources	38
JavaScript Resources	15
CSS Resources	8

wida.us mobile page speed rank

Last tested: 2018-06-30

Mobile Speed Bad

57/100

wida.us Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

https://www.wida.us/WebResource.axd?d=pynGkmcFUV13…2&t=636475798140000000
https://www.wida.us/WebResource.axd?d=x2nkrMJGXkME…1&t=636475798140000000

Optimize CSS Delivery of the following:

priority - 18Leverage 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 - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (37% 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 4.5KiB (35% 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 1.6KiB (16% 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 1.4KiB (20% reduction).

Minifying https://www.wida.us/ could save 1.4KiB (20% reduction) after compression.

wida.us Mobile Resource Breakdown

Total Resources	52
Number of Hosts	17
Static Resources	38
JavaScript Resources	15
CSS Resources	8

wida.us mobile page usability

Last tested: 2018-06-30

Mobile Usability Bad

63/100

wida.us Mobile Usability Test Quick Summary

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

Recursos en Español and 3 others render only 5 pixels tall (12 CSS pixels).

STANDARDS & INSTRUCTION and 5 others render only 5 pixels tall (14 CSS pixels).

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

Previous and 1 others render only 8 pixels tall (20 CSS pixels).

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

Forgot Username or Password? renders only 4 pixels tall (11 CSS pixels).

Learn more renders only 4 pixels tall (11 CSS pixels).

39 U.S. State…ation Agencies and 3 others render only 5 pixels tall (14 CSS pixels).

WIDA Internati…ool Consortium and 4 others render only 5 pixels tall (14 CSS pixels).

for free Q&A Webinars. and 6 others render only 5 pixels tall (14 CSS pixels).

MORE renders only 5 pixels tall (12 CSS pixels).

LATEST NEWS renders only 6 pixels tall (15 CSS pixels).

2017-18 Score…w available on and 5 others render only 5 pixels tall (12 CSS pixels).

WIDA.us/ACCESSscores and 4 others render only 5 pixels tall (12 CSS pixels).

Posted 5/10/18 and 3 others render only 4 pixels tall (10 CSS pixels).

ACCESS for ELLs PRIVACY POLICY and 3 others render only 4 pixels tall (11 CSS pixels).

WIDA is housed within the and 6 others render only 4 pixels tall (11 CSS pixels).

Wisconsin Cent…Research and 3 others render only 4 pixels tall (11 CSS pixels).

priority - 16Size 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="http://www.fac…com/WIDAatWCER"></a> and 3 others are close to other tap targets.

The tap target <table id="gs_id50" class="gstl_50">×</table> is close to 1 other tap targets.

The tap target <input id="gsc-i-id1" type="text" name="search" class="gsc-input"> is close to 2 other tap targets.

The tap target <button class="gsc-search-but…arch-button-v2">search</button> is close to 1 other tap targets.

The tap target <a href="downloadLibrary.aspx">Download Library</a> and 3 others are close to other tap targets.

The tap target <a href="#" class="dropdown-toggle">ABOUT US</a> and 2 others are close to other tap targets.

The tap target <a href="research/research.aspx">RESEARCH</a> is close to 3 other tap targets.

The tap target <a href="#slider-wrapper" class="left carousel-control">Previous</a> and 1 others are close to other tap targets.

The tap target <label id="Login1_UserNameLabel" for="Login1_UserName">Username:</label> and 1 others are close to other tap targets.

The tap target <input id="Login1_UserName" type="text" name="Login1$UserName" class="loginField1"> is close to 2 other tap targets.

The tap target <input id="Login1_Password" type="password" name="Login1$Password" class="loginField2"> is close to 3 other tap targets.

The tap target <input id="Login1_LoginButton" type="submit" name="Login1$LoginButton" class="small gray button"> is close to 2 other tap targets.

The tap target <a id="Login1_PasswordRecoveryLink" href="ResetPasswordRequest.aspx">Forgot Username or Password?</a> is close to 3 other tap targets.

The tap target <a href="login.aspx">Learn more</a> is close to 2 other tap targets.

The tap target <a href="downloadLibrary.aspx"></a> is close to 1 other tap targets.

The tap target <a href="/assessment/Screener/">Learn more</a> and 3 others are close to other tap targets.

The tap target <a href="News/Subscribe/index.aspx" class="subscribe"></a> is close to 1 other tap targets.

The tap target <a href="News/index.aspx" class="moreNews more">MORE</a> is close to 1 other tap targets.

The tap target <a href="ProfessionalDe…haLambson.aspx">Read More</a> and 2 others are close to other tap targets.

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

The tap target <a href="mailto:help@wida.us" class="copyright">help@wida.us</a> and 3 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.

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

The element <div id="navGrayLinks">Download Libra…Online Store</div> falls outside the viewport.
The element <div id="navContainer" class="container">ABOUT US…tional Schools</div> falls outside the viewport.
The element <div id="itemContent">WIDA Screener…Posted 4/2/18</div> falls outside the viewport.
The element <p>HOME | SITE…sconsin System</p> falls outside the viewport.

wida.us HTML validation

Errors

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

Line: 2 Column: 1 - 109
"... <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."

When the attribute “xml:lang” in no namespace is specified, the element must also have the attribute “lang” present with the same value.

Line: 3 Column: 110 - 78
"...rict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" ng-app="widaWebsite"><!-- I..."

Attribute “ng-app” not allowed on element “html” at this point.

Line: 3 Column: 110 - 78
"...rict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" ng-app="widaWebsite"><!-- I..."

Element “link” is missing one or more of the following attributes: “href”, “itemprop”, “property”, “rel”.

Line: 17 Column: 1 - 8
"...creen" /> <link /> <link..."

Bad element name “gcse:searchbox-only”: Code point “U+003A” is not allowed

Line: 124 Column: 29 - 82
"... <gcse:searchbox-only resultsUrl="/searchResults.aspx"></gcse..."

Bad value “/Assessment/ACCESS 2.0/documents/ACCESSWebinarCalendar.pdf” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

Line: 234 Column: 26 - 109
"... <a href="/Assessment/ACCESS 2.0/documents/ACCESSWebinarCalendar.pdf" target="blank"><img..."

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

Line: 258 Column: 15 - 110
"... <table id="Login1" cellspacing="0" cellpadding="0" border="0" style="border-collapse:collapse;"> <tr..."

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

Line: 258 Column: 15 - 110
"... <table id="Login1" cellspacing="0" cellpadding="0" border="0" style="border-collapse:collapse;"> <tr..."

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

Line: 258 Column: 15 - 110
"... <table id="Login1" cellspacing="0" cellpadding="0" border="0" style="border-collapse:collapse;"> <tr..."

Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.

Line: 263 Column: 19 - 24
"... <div/> ..."

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

Line: 272 Column: 19 - 21
"... <p> ..." Line: 275 Column: 19 - 21
"... <p> <a hr..."

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

Line: 276 Column: 27 - 31
"... </span> </td> </t..."

Unclosed element “div”.

Line: 263 Column: 19 - 24
"... <div/> ..."

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

Line: 294 Column: 10 - 27
"... <p align="center"><a hre..." Line: 313 Column: 13 - 30
"... <p align="center"><a hre..." Line: 314 Column: 13 - 30
"... <p align="center"><stron..." Line: 316 Column: 13 - 30
"... <p align="center"><stron..."

Warnings

Element name “gcse:searchbox-only” cannot be represented as XML 1.0.

Line: 124 Column: 29 - 82
"... <gcse:searchbox-only resultsUrl="/searchResults.aspx"></gcse..."

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

Line: 403 Column: - 3
"...rketing Tag -----------------..." Line: 403 Column: - 49
"...--------------- Remarketing t..." Line: 406 Column: - 3
"...rketingsetup -----------------..."

wida.us similar domains

Similar domains:

www.wida.com
www.wida.net
www.wida.org
www.wida.info
www.wida.biz
www.wida.us
www.wida.mobi
www.ida.us
www.wida.us
www.qida.us
www.wqida.us
www.qwida.us
www.aida.us
www.waida.us
www.awida.us
www.sida.us
www.wsida.us
www.swida.us
www.eida.us
www.weida.us
www.ewida.us
www.wda.us
www.wuda.us
www.wiuda.us
www.wuida.us
www.wjda.us
www.wijda.us
www.wjida.us
www.wkda.us
www.wikda.us
www.wkida.us
www.woda.us
www.wioda.us
www.woida.us
www.wia.us
www.wixa.us
www.widxa.us
www.wixda.us
www.wisa.us
www.widsa.us
www.wisda.us
www.wiea.us
www.widea.us
www.wieda.us
www.wira.us
www.widra.us
www.wirda.us
www.wifa.us
www.widfa.us
www.wifda.us
www.wica.us
www.widca.us
www.wicda.us
www.wid.us
www.widq.us
www.widaq.us
www.widqa.us
www.widw.us
www.widaw.us
www.widwa.us
www.wids.us
www.widas.us
www.widz.us
www.widaz.us
www.widza.us

wida.us 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.

wida.us 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.

WIDA.US WIDA

wida.us Website Information

Advertisement

wida.us Alexa Rank

wida.us whois

wida.us server information

Servers Location

wida.us desktop page speed rank

wida.us Desktop Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 12Leverage 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 - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (37% 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 4.5KiB (35% 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 1.6KiB (16% 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 1.4KiB (20% reduction).

wida.us Desktop Resource Breakdown

wida.us mobile page speed rank

wida.us Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 18Leverage 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 - 6Optimize images

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

Optimize the following images to reduce their size by 58.4KiB (37% 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 4.5KiB (35% 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 1.6KiB (16% 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 1.4KiB (20% reduction).

wida.us Mobile Resource Breakdown

wida.us mobile page usability

wida.us Mobile Usability Test Quick Summary

priority - 32Use 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 - 16Size 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 - 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 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 987 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

wida.us HTML validation

Errors

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

When the attribute “xml:lang” in no namespace is specified, the element must also have the attribute “lang” present with the same value.

Attribute “ng-app” not allowed on element “html” at this point.

Element “link” is missing one or more of the following attributes: “href”, “itemprop”, “property”, “rel”.

Bad element name “gcse:searchbox-only”: Code point “U+003A” is not allowed

Bad value “/Assessment/ACCESS 2.0/documents/ACCESSWebinarCalendar.pdf” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

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

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

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

Self-closing syntax (“/>”) used on a non-void HTML element. Ignoring the slash and treating as a start tag.

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

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

Unclosed element “div”.

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