anzam.org Website Information

Daily Unique Visits: 1,031

Daily Page Views: 2,062

Income Per Day: $6

Estimated Value: $1,440

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

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

Website anzam.org is using the following name servers:

ns1.panthur.com
ns2.panthur.com
ns3.panthur.com
ns4.panthur.com

and is probably hosted by DIGITAL PACIFIC PTY LTD. See the full list of other websites hosted by DIGITAL PACIFIC PTY LTD.

The highest website anzam.org position in Alexa rank database was 23579 and the lowest rank position was 997672. Current position of anzam.org in Alexa rank database is 695866.

Desktop speed score of anzam.org (67/100) is better than the results of 45.93% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of anzam.org (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed score of anzam.org (55/100) is better than the results of 43.86% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

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

anzam.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: anzam.org
Registry Domain ID: cee97606af7e461b8adb7399417fb866-LROR
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2024-10-27T04:48:56Z
Creation Date: 2007-11-20T02:56:15Z
Registry Expiry Date: 2025-11-20T02:56:15Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Data Protected
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Queensland
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: AU
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: ns1.panthur.com
Name Server: ns2.panthur.com
Name Server: ns3.panthur.com
Name Server: ns4.panthur.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-11-03T19:50:06Z

anzam.org server information

Servers Location

anzam.org desktop page speed rank

Last tested: 2017-12-04

Desktop Speed Medium

67/100

anzam.org Desktop Speed Test Quick Summary

priority - 24Optimize images

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

Optimize the following images to reduce their size by 238.9KiB (78% reduction).

Compressing http://www.anzam.org/wp-content/uploads/2014/04/jmo_900x374.jpg could save 238.9KiB (78% reduction).

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

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

Remove render-blocking JavaScript:

https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js
http://www.anzam.org/wp-content/plugins/swiftype-s…nstall_swiftype.min.js
http://www.anzam.org/wp-includes/js/wp-embed.min.js

Optimize CSS Delivery of the following:

http://www.anzam.org/wp-content/themes/anzam_template/style.css
http://www.anzam.org/wp-content/themes/anzam_template/library/css/style.css
http://www.anzam.org/wp-content/plugins/swiftype-s…ssets/autocomplete.css

priority - 8Reduce server response time

priority - 4Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 23% of the final above-the-fold content could be rendered with the full HTML response.

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://s.swiftypecdn.com/cc.js (5 minutes)
https://use.typekit.net/xer7yub.js (10 minutes)
https://www.eway.com.au/developer/payment-code/ver…4d40-8c5c-3519de1dd7f3 (15 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify 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 6.1KiB (38% reduction).

Minifying http://www.anzam.org/wp-content/themes/anzam_template/library/css/style.css could save 6.1KiB (38% reduction) after compression.

anzam.org Desktop Resource Breakdown

Total Resources	29
Number of Hosts	9
Static Resources	19
JavaScript Resources	8
CSS Resources	3

anzam.org mobile page speed rank

Last tested: 2017-05-04

Mobile Speed Bad

55/100

anzam.org Mobile Speed Test Quick Summary

priority - 30Reduce server response time

priority - 24Optimize images

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

Optimize the following images to reduce their size by 238.9KiB (78% reduction).

Compressing http://www.anzam.org/wp-content/uploads/2014/04/jmo_900x374.jpg could save 238.9KiB (78% reduction).

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

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

Remove render-blocking JavaScript:

http://www.anzam.org/wp-content/plugins/swiftype-s…nstall_swiftype.min.js

Optimize CSS Delivery of the following:

http://www.anzam.org/wp-content/cache/minify/00000…ult.include.d58e84.css
http://www.anzam.org/wp-content/plugins/swiftype-s…ssets/autocomplete.css

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

57.7KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.

Only about 33% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 4Leverage 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://s.swiftypecdn.com/cc.js (5 minutes)
http://use.typekit.net/aow0fxz.js (10 minutes)
https://www.eway.com.au/developer/payment-code/ver…4d40-8c5c-3519de1dd7f3 (15 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

anzam.org Mobile Resource Breakdown

Total Resources	27
Number of Hosts	8
Static Resources	16
JavaScript Resources	6
CSS Resources	2

anzam.org mobile page usability

Last tested: 2017-05-04

Mobile Usability Good

94/100

anzam.org Mobile Usability Test Quick Summary

priority - 5Size 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.anz…ty-of-waikato/">Master’s Schol…ity of Waikato</a> is close to 1 other tap targets.
The tap target <a href="http://www.anz…ns/newsletter/">Newsletter</a> and 1 others are close to other tap targets.
The tap target <a href="https://www.fa…k.com/anzamorg"></a> and 2 others are close to other tap targets.
The tap target <a href="http://www.anzam.org/events" class="alt">Events</a> and 2 others are close to other tap targets.
The tap target <a href="http://www.anz…ts-conference/">Conference</a> and 17 others are close to other tap targets.

anzam.org 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: 11 Column: 2 - 63
"...tf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <m..."

A document must not include both a “meta” element with an “http-equiv” attribute whose value is “content-type”, and a “meta” element with a “charset” attribute.

Line: 17 Column: 2 - 70
"....ico"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <met..." Line: 18 Column: 2 - 25
"...TF-8" /> <meta charset="UTF-8" /> <ti..."

A document must not include more than one “meta” element with a “charset” attribute.

Line: 18 Column: 2 - 25
"...TF-8" /> <meta charset="UTF-8" /> <ti..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 126 Column: 1 - 71
"...</script> <link rel='https://api.w.org/' href='https://www.anzam.org/wp-json/' /> <!-- ..."

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

Line: 182 Column: 67 - 90
"..._text"> <div class="textwidget"></div>..."

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

Line: 183 Column: 71 - 167
"... <form name="loginform" id="loginform" action="https://www.anzam.org/amember/login" method="POST"> ..."

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

Line: 192 Column: 13 - 15
"... <p> ..."

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

Line: 203 Column: 9 - 30
"...> <div class="clearfix"></div>..."

Duplicate ID “menu”.

Line: 297 Column: 2 - 111
"... <nav id="menu" class="menu-link oc" role="navigation" style="left: -14em; position: absolute; display: none;"> ..."

Bad value “11 Aug 2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Line: 350 Column: 5 - 54
"...span> <time itemprop="startDate" datetime="11 Aug 2018">11 Aug..." Line: 351 Column: 5 - 52
"...time> <time itemprop="endDate" datetime="11 Aug 2018"></time..."

Bad value “04 Dec 2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Line: 361 Column: 5 - 54
"...span> <time itemprop="startDate" datetime="04 Dec 2018">04 Dec..." Line: 362 Column: 5 - 52
"...time> <time itemprop="endDate" datetime="04 Dec 2018"></time..."

Attribute “pubdate” not allowed on element “time” at this point.

Line: 382 Column: 4 - 37
"...left"> <time pubdate datetime="20181215"> D..." Line: 393 Column: 4 - 37
"...left"> <time pubdate datetime="20181130"> D..." Line: 404 Column: 4 - 37
"...left"> <time pubdate datetime="20190320"> D..." Line: 437 Column: 4 - 37
"...left"> <time pubdate datetime="20180810"> D..." Line: 448 Column: 4 - 37
"...left"> <time pubdate datetime="20180831"> D..." Line: 518 Column: 6 - 56
"... <time pubdate datetime="2018-07-16T15:22:36+00:00"> ..." Line: 538 Column: 6 - 56
"... <time pubdate datetime="2018-06-20T12:02:32+00:00"> ..." Line: 558 Column: 6 - 56
"... <time pubdate datetime="2018-06-18T11:30:28+00:00"> ..." Line: 578 Column: 6 - 56
"... <time pubdate datetime="2018-05-29T21:00:22+00:00"> ..."

Duplicate ID “page”.

Line: 485 Column: 3 - 30
"...apper"> <div class="main" id="page"> <d..." Line: 497 Column: 2 - 45
"...rapper"> <section role="main" class="main" id="page"> <di..."

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

Line: 503 Column: 14 - 18
"... <h1>News</h2> <..."

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

Line: 660 Column: 6 - 11
"...</p> </div> <..." Line: 661 Column: 5 - 10
".../div> </div> ..."

Unclosed element “aside”.

Line: 658 Column: 6 - 35
"...om"> <aside class="footer_content"> ..."

Unclosed element “footer”.

Line: 595 Column: 3 - 49
"... <footer class="site_footer" role="contentinfo"> <d..."

Stray end tag “footer”.

Line: 662 Column: 6 - 14
"...div> </footer> <..."

Stray end tag “div”.

Line: 666 Column: 1 - 6
"...ader --> </div> <!-- ..."

Stray start tag “script”.

Line: 686 Column: 2 - 32
"...</html> <script type="text/javascript"> jQu..."

Cannot recover after last error. Any further errors will be ignored.

Line: 686 Column: 2 - 32
"...</html> <script type="text/javascript"> jQu..."

Warnings

The “banner” role is unnecessary for element “header”.

Line: 161 Column: 5 - 55
"..."> <header role="banner" id="top" class="site_header"> ..."

The first occurrence of ID “menu” was here.

Line: 207 Column: 8 - 22
"... <nav id="menu"> <di..."

The “navigation” role is unnecessary for element “nav”.

Line: 297 Column: 2 - 111
"... <nav id="menu" class="menu-link oc" role="navigation" style="left: -14em; position: absolute; display: none;"> ..."

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: 341 Column: 6 - 21
"...der> <h1 class="alt"><a hre..." Line: 373 Column: 6 - 21
"...der> <h1 class="alt"><a hre..." Line: 417 Column: 6 - 21
"...der> <h1 class="alt"><a hre..." Line: 461 Column: 6 - 21
"...der> <h1 class="alt"><a hre..." Line: 503 Column: 6 - 9
"...ck"> <h1>News</..." Line: 512 Column: 11 - 26
"... <h1 class="alt"> ..." Line: 532 Column: 11 - 26
"... <h1 class="alt"> ..." Line: 552 Column: 11 - 26
"... <h1 class="alt"> ..." Line: 572 Column: 11 - 26
"... <h1 class="alt"> ..."

Potentially bad value “20181215” for attribute “datetime” on element “time”: Year may be mistyped.

Line: 382 Column: 4 - 37
"...left"> <time pubdate datetime="20181215"> D..."

Potentially bad value “20181130” for attribute “datetime” on element “time”: Year may be mistyped.

Line: 393 Column: 4 - 37
"...left"> <time pubdate datetime="20181130"> D..."

Potentially bad value “20190320” for attribute “datetime” on element “time”: Year may be mistyped.

Line: 404 Column: 4 - 37
"...left"> <time pubdate datetime="20190320"> D..."

Potentially bad value “20180810” for attribute “datetime” on element “time”: Year may be mistyped.

Line: 437 Column: 4 - 37
"...left"> <time pubdate datetime="20180810"> D..."

Potentially bad value “20180831” for attribute “datetime” on element “time”: Year may be mistyped.

Line: 448 Column: 4 - 37
"...left"> <time pubdate datetime="20180831"> D..."

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

Line: 313 Column: 1 - 44
"...ript> <section role="main" class="main" id="page"> <div..." Line: 497 Column: 2 - 45
"...rapper"> <section role="main" class="main" id="page"> <di..."

The first occurrence of ID “page” was here.

Line: 313 Column: 1 - 44
"...ript> <section role="main" class="main" id="page"> <div..." Line: 313 Column: 1 - 44
"...ript> <section role="main" class="main" id="page"> <div..."

The “article” role is unnecessary for element “article”.

Line: 507 Column: 4 - 71
"...v> <article role="article" class="tab_4 desk_b_6 desk_a_8 margin_auto"> <div..." Line: 527 Column: 11 - 78
"...</article><article role="article" class="tab_4 desk_b_6 desk_a_8 margin_auto"> <div..." Line: 547 Column: 11 - 78
"...</article><article role="article" class="tab_4 desk_b_6 desk_a_8 margin_auto"> <div..." Line: 567 Column: 11 - 78
"...</article><article role="article" class="tab_4 desk_b_6 desk_a_8 margin_auto"> <div..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 595 Column: 3 - 49
"... <footer class="site_footer" role="contentinfo"> <d..."

anzam.org similar domains

Similar domains:

www.anzam.com
www.anzam.net
www.anzam.org
www.anzam.info
www.anzam.biz
www.anzam.us
www.anzam.mobi
www.nzam.org
www.anzam.org
www.qnzam.org
www.aqnzam.org
www.qanzam.org
www.wnzam.org
www.awnzam.org
www.wanzam.org
www.snzam.org
www.asnzam.org
www.sanzam.org
www.znzam.org
www.aznzam.org
www.zanzam.org
www.azam.org
www.abzam.org
www.anbzam.org
www.abnzam.org
www.ahzam.org
www.anhzam.org
www.ahnzam.org
www.ajzam.org
www.anjzam.org
www.ajnzam.org
www.amzam.org
www.anmzam.org
www.amnzam.org
www.anam.org
www.anxam.org
www.anzxam.org
www.anxzam.org
www.ansam.org
www.anzsam.org
www.anszam.org
www.anaam.org
www.anzaam.org
www.anazam.org
www.anzm.org
www.anzqm.org
www.anzaqm.org
www.anzqam.org
www.anzwm.org
www.anzawm.org
www.anzwam.org
www.anzsm.org
www.anzasm.org
www.anzzm.org
www.anzazm.org
www.anzzam.org
www.anza.org
www.anzan.org
www.anzamn.org
www.anzanm.org
www.anzaj.org
www.anzamj.org
www.anzajm.org
www.anzak.org
www.anzamk.org
www.anzakm.org

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

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

ANZAM.ORG ANZAM - Australian and New Zealand Academy of Management

anzam.org Website Information

Advertisement

anzam.org Alexa Rank

anzam.org whois

anzam.org server information

Servers Location

anzam.org desktop page speed rank

anzam.org Desktop Speed Test Quick Summary

priority - 24Optimize images

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

Optimize the following images to reduce their size by 238.9KiB (78% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 8Reduce server response time

priority - 4Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

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:

priority - 1Minify 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 6.1KiB (38% reduction).

anzam.org Desktop Resource Breakdown

anzam.org mobile page speed rank

anzam.org Mobile Speed Test Quick Summary

priority - 30Reduce server response time

priority - 24Optimize images

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

Optimize the following images to reduce their size by 238.9KiB (78% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

57.7KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.

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

anzam.org Mobile Resource Breakdown

anzam.org mobile page usability

anzam.org Mobile Usability Test Quick Summary

priority - 5Size 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.

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

A document must not include both a “meta” element with an “http-equiv” attribute whose value is “content-type”, and a “meta” element with a “charset” attribute.

A document must not include more than one “meta” element with a “charset” attribute.

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

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

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

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

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

Duplicate ID “menu”.

Bad value “11 Aug 2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “04 Dec 2018” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Attribute “pubdate” not allowed on element “time” at this point.

Duplicate ID “page”.

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

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

Unclosed element “aside”.

Unclosed element “footer”.

Stray end tag “footer”.

Stray end tag “div”.

Stray start tag “script”.

Cannot recover after last error. Any further errors will be ignored.

Warnings

The “banner” role is unnecessary for element “header”.

The first occurrence of ID “menu” was here.

The “navigation” role is unnecessary for element “nav”.

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

Potentially bad value “20181215” for attribute “datetime” on element “time”: Year may be mistyped.

Potentially bad value “20181130” for attribute “datetime” on element “time”: Year may be mistyped.

Potentially bad value “20190320” for attribute “datetime” on element “time”: Year may be mistyped.

Potentially bad value “20180810” for attribute “datetime” on element “time”: Year may be mistyped.