linzag.at Website Information

Daily Unique Visits: 11,217

Daily Page Views: 56,085

Income Per Day: $140

Estimated Value: $84,000

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

linzag.at is registered under .AT top-level domain. Please check other sites in .AT zone.

Website linzag.at is using the following name servers:

ns2.linzag.at
ns1.linzag.at
dns1.linz.at

and is probably hosted by LINZ STROM GAS WAERME GmbH fuer Energiedienstleistungen und Telekommunikation. See the full list of other websites hosted by LINZ STROM GAS WAERME GmbH fuer Energiedienstleistungen und Telekommunikation.

The highest website linzag.at position in Alexa rank database was 38465 and the lowest rank position was 881738. Current position of linzag.at in Alexa rank database is 121464.

Desktop speed score of linzag.at (53/100) is better than the results of 27.05% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of linzag.at (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.

Mobile speed score of linzag.at (44/100) is better than the results of 24.22% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

linzag.at 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.

linzag.at 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.

% Copyright (c)2024 by NIC.AT (1)
%
% Restricted rights.
%
% Except for agreed Internet operational purposes, no part of this
% information may be reproduced, stored in a retrieval system, or
% transmitted, in any form or by any means, electronic, mechanical,
% recording, or otherwise, without prior permission of NIC.AT on behalf
% of itself and/or the copyright holders. Any use of this material to
% target advertising or similar activities is explicitly forbidden and
% can be prosecuted.
%
% It is furthermore strictly forbidden to use the Whois-Database in such
% a way that jeopardizes or could jeopardize the stability of the
% technical systems of NIC.AT under any circumstances. In particular,
% this includes any misuse of the Whois-Database and any use of the
% Whois-Database which disturbs its operation.
%
% Should the user violate these points, NIC.AT reserves the right to
% deactivate the Whois-Database entirely or partly for the user.
% Moreover, the user shall be held liable for any and all damage
% arising from a violation of these points.

% Quota exceeded

linzag.at server information

Servers Location

linzag.at desktop page speed rank

Last tested: 2018-11-16

Desktop Speed Bad

53/100

linzag.at Desktop Speed Test Quick Summary

priority - 91Optimize images

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

Optimize the following images to reduce their size by 886.4KiB (41% reduction).

Compressing https://www.linzag.at/media/bilder/baeder/Baeder_2for1_heroSlider.jpg could save 450.5KiB (76% reduction).
Compressing https://www.linzag.at/media/bilder/linien/klimafre…her-bus_heroSlider.jpg could save 78.7KiB (21% reduction).
Compressing https://www.linzag.at/media/bilder/linz_ag/messe-h…n-banner_newsImage.jpg could save 78.5KiB (78% reduction).
Compressing https://www.linzag.at/media/bilder/linien/grottenb…en-2018_heroSlider.jpg could save 75KiB (24% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/schwimme…-Dampf_imageTeaser.jpg could save 72.6KiB (80% reduction).
Compressing https://www.linzag.at/media/bilder/waerme/Ballwech…nenhalle_newsImage.jpg could save 20.1KiB (22% reduction).
Compressing https://www.linzag.at/media/bilder/linien/grottenb…hen-2018_newsImage.jpg could save 19.2KiB (24% reduction).
Compressing https://www.linzag.at/media/bilder/linien/fuhrpark…m_profil_newsImage.jpg could save 16.3KiB (20% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/sauna/sauna-gruppe_newsImage.jpg could save 10.6KiB (18% reduction).
Compressing https://www.linzag.at/media/bilder/trauer_1/sonnenuntergang_imageTeaser.jpg could save 10.6KiB (22% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/Baeder_2for1_newsImage.jpg could save 7.7KiB (20% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/eissport…islaufen_newsImage.jpg could save 7.1KiB (17% reduction).
Compressing https://www.linzag.at/media/bilder/linien/menschen…linien_imageTeaser.jpg could save 6.8KiB (19% reduction).
Compressing https://www.linzag.at/media/bilder/strom_1/mensche…mputer_imageTeaser.jpg could save 6.6KiB (19% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/eissport…ufschuhe_newsImage.jpg could save 6.5KiB (18% reduction).
Compressing https://www.linzag.at/media/bilder/linz_ag/gutschein_newsImage.jpg could save 6KiB (17% reduction).
Compressing https://www.linzag.at/media/bilder/baeder/veransta…fuehrung_newsImage.jpg could save 5.6KiB (17% reduction).
Compressing https://www.linzag.at/media/bilder/linien/tickets/…-mollner_newsImage.jpg could save 4.1KiB (17% reduction).
Compressing https://www.linzag.at/media/bilder/assets/plus24/login-panel.jpg could save 3.6KiB (16% reduction).
Compressing https://www.linzag.at//resources/img/page_logo.png could save 314B (20% reduction).

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

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

Remove render-blocking JavaScript:

https://www.linzag.at//resources/jquery/jquery-1.11.3.js

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:

https://www.etracker.de/dc/js/jquery-1.8.3.min.js (60 minutes)
https://static.etracker.com/code/e.js (4 hours)
https://et.twyn.com/js/ta.min.js (6 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 2.1KiB (13% reduction).

Minifying https://www.linzag.at/portal/de/privatkunden could save 2.1KiB (13% 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 543B (11% reduction).

Minifying https://code.etracker.com/t.js?v=2cd80c&et=YKgOBV could save 543B (11% reduction) after compression.

linzag.at Desktop Resource Breakdown

Total Resources	49
Number of Hosts	11
Static Resources	35
JavaScript Resources	11
CSS Resources	2

linzag.at mobile page speed rank

Last tested: 2018-11-16

Mobile Speed Bad

44/100

linzag.at Mobile Speed Test Quick Summary

priority - 91Optimize images

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

Optimize the following images to reduce their size by 886.4KiB (41% reduction).

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

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

Remove render-blocking JavaScript:

https://www.linzag.at//resources/jquery/jquery-1.11.3.js
https://www.linzag.at/portal/javax.faces.resource/…r.node2?ln=javax.faces
https://static.etracker.com/code/e.js
https://www.linzag.at/resources/js/forms.min.js
https://www.linzag.at//resources/js/plugin.min.js
https://www.linzag.at//resources/js/common.min.js

Optimize CSS Delivery of the following:

https://www.linzag.at/portal/javax.faces.resource/…f?ln=primefaces-aristo
https://www.linzag.at//resources/css/application.min.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.

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 36% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the 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:

https://www.etracker.de/dc/js/jquery-1.8.3.min.js (60 minutes)
https://static.etracker.com/code/e.js (4 hours)
https://et.twyn.com/js/ta.min.js (6 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 2.1KiB (13% reduction).

Minifying https://www.linzag.at/portal/de/privatkunden could save 2.1KiB (13% 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 544B (11% reduction).

Minifying https://code.etracker.com/t.js?v=2cd80c&et=YKgOBV could save 544B (11% reduction) after compression.

linzag.at Mobile Resource Breakdown

Total Resources	44
Number of Hosts	8
Static Resources	35
JavaScript Resources	11
CSS Resources	2

linzag.at mobile page usability

Last tested: 2018-11-16

Mobile Usability Good

96/100

linzag.at Mobile Usability Test Quick Summary

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 418 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <article class="lag-news-item…ws-color--blue">16.11.2018 | L…kten Geschenk?</article> falls outside the viewport.
The element <article class="lag-news-item…ws-color--blue">14.11.2018 | L…LINZ AG BÄDERN</article> falls outside the viewport.
The element <article class="lag-news-item…ws-color--blue">13.11.2018 | L…oase Ebelsberg</article> falls outside the viewport.
The element <article class="lag-news-item…ws-color--blue">11.11.2018 | L…aus und Wohnen</article> falls outside the viewport.
The element <article class="lag-news-item…ws-color--blue">10.11.2018 | L…ssoase Parkbad</article> falls outside the viewport.
The element <article class="lag-news-item…ws-color--blue">09.11.2018 | L…bastian am Eis</article> falls outside the viewport.
The element <div class="lag-news-loadmore">Alle News</div> falls outside the viewport.

priority - 0Size 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="https://www.li…er/datenschutz" class="lag-cookie-link">Mehr Informationen</a> is close to 1 other tap targets.

The tap target <button type="button" class="lag-btn lag-co…-cookie-policy">Verstanden</button> is close to 2 other tap targets.

The tap target <button type="button" class="lag-btn lag-co…-cookie-policy">Cookie Richtlinien schliessen</button> is close to 1 other tap targets.

linzag.at HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Line: 1 Column: - 2
"...<?xml version="1..."

A “charset” attribute on a “meta” element found after the first 1024 bytes.

Line: 33 Column: - 22
"... charset="utf-8" /> <meta na..."

Duplicate ID “fmSiteSearch”.

Line: 286 Column: 3 - 88
"...orm --> <form id="fmSiteSearch" method="get" action="https://www.linzag.at//portal/start.app"> <i..."

Duplicate ID “lag-site-search-input”.

Line: 293 Column: 7 - 55
"...an> <span id="lag-site-search-input" hidden="hidden">Suchbe..."

Duplicate ID “q”.

Line: 293 Column: 84 - 249
"...en.</span><input id="q" name="q" class="lag-site-search-input js-lag-search-input" autocomplete="off" placeholder="Seite durchsuchen" type="search" title="Seite durchsuchen" /><!-- ...."

An element with “role=tab” must be contained in, or owned by, an element with “role=tablist”.

Line: 669 Column: 5 - 54
"...ter"> <li class="lag-tab-item-mashup active" role="tab"> ..." Line: 672 Column: 5 - 47
"...</li> <li class="lag-tab-item-mashup" role="tab"> ..." Line: 675 Column: 5 - 47
"...</li> <li class="lag-tab-item-mashup" role="tab"> ..." Line: 678 Column: 5 - 47
"...</li> <li class="lag-tab-item-mashup" role="tab"> ..."

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

Line: 699 Column: 11 - 38
"... <time datetime="03.07.2018">03.07...." Line: 724 Column: 11 - 38
"... <time datetime="03.07.2018">03.07...." Line: 1098 Column: 11 - 38
"... <time datetime="03.07.2018">03.07...." Line: 1123 Column: 11 - 38
"... <time datetime="03.07.2018">03.07...."

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

Line: 749 Column: 11 - 38
"... <time datetime="01.07.2018">01.07...." Line: 1148 Column: 11 - 38
"... <time datetime="01.07.2018">01.07...."

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

Line: 774 Column: 11 - 38
"... <time datetime="29.06.2018">29.06...." Line: 1015 Column: 11 - 38
"... <time datetime="29.06.2018">29.06...."

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

Line: 799 Column: 11 - 38
"... <time datetime="27.06.2018">27.06...." Line: 1040 Column: 11 - 38
"... <time datetime="27.06.2018">27.06...."

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

Line: 824 Column: 11 - 38
"... <time datetime="25.06.2018">25.06...." Line: 1065 Column: 11 - 38
"... <time datetime="25.06.2018">25.06...."

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

Line: 857 Column: 11 - 38
"... <time datetime="21.06.2018">21.06...."

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

Line: 882 Column: 11 - 38
"... <time datetime="20.06.2018">20.06...."

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

Line: 907 Column: 11 - 38
"... <time datetime="19.06.2018">19.06...." Line: 932 Column: 11 - 38
"... <time datetime="19.06.2018">19.06...."

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

Line: 957 Column: 11 - 38
"... <time datetime="07.06.2018">07.06...."

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

Line: 982 Column: 11 - 38
"... <time datetime="09.05.2018">09.05...."

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

Line: 1173 Column: 11 - 38
"... <time datetime="01.06.2018">01.06...."

The “for” attribute of the “label” element must refer to a non-hidden form control.

Line: 467 Column: 9 - 54
"...> <label for="tbRoadmapStart" class="lag-label">Start<..." Line: 480 Column: 9 - 52
"...> <label for="tbRoadmapEnd" class="lag-label">Ziel</..." Line: 495 Column: 9 - 72
"...> <label id="j_idt23" class="lag-label" for="clRoadmapDate_input">Datum<..." Line: 512 Column: 9 - 53
"...> <label for="tbRoadmapTime" class="lag-label">Zeit</..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 34 Column: 2 - 108
"...f-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, user-scalable=no" /> ..." Line: 36 Column: 4 - 110
"...ta --> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, user-scalable=no" /> <m..."

The first occurrence of ID “fmSiteSearch” was here.

Line: 136 Column: 7 - 92
"...--> <form id="fmSiteSearch" method="get" action="https://www.linzag.at//portal/start.app"> <in..."

The first occurrence of ID “lag-site-search-input” was here.

Line: 292 Column: 7 - 55
"...--> <span id="lag-site-search-input" hidden="hidden">Suchbe..."

The first occurrence of ID “q” was here.

Line: 140 Column: 4 - 170
"...arch"> <input id="q" name="q" class="lag-input-text lag-input--sm lag-nav-search-input js-lag-nav-search-input" placeholder="Suchbegriff" type="search" title="Suchbegriff" /> ..."

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

Line: 368 Column: 1 - 32
"... </div> <a name="sommeroeffnungszeiten"></a> <..." Line: 1195 Column: 1 - 24
"...ashup --> <a name="bild_teaser_1"></a> <..."

linzag.at similar domains

Similar domains:

www.linzag.com
www.linzag.net
www.linzag.org
www.linzag.info
www.linzag.biz
www.linzag.us
www.linzag.mobi
www.inzag.at
www.linzag.at
www.pinzag.at
www.lpinzag.at
www.plinzag.at
www.oinzag.at
www.loinzag.at
www.olinzag.at
www.kinzag.at
www.lkinzag.at
www.klinzag.at
www.lnzag.at
www.lunzag.at
www.liunzag.at
www.luinzag.at
www.ljnzag.at
www.lijnzag.at
www.ljinzag.at
www.lknzag.at
www.liknzag.at
www.lonzag.at
www.lionzag.at
www.lizag.at
www.libzag.at
www.linbzag.at
www.libnzag.at
www.lihzag.at
www.linhzag.at
www.lihnzag.at
www.lijzag.at
www.linjzag.at
www.limzag.at
www.linmzag.at
www.limnzag.at
www.linag.at
www.linxag.at
www.linzxag.at
www.linxzag.at
www.linsag.at
www.linzsag.at
www.linszag.at
www.linaag.at
www.linzaag.at
www.linazag.at
www.linzg.at
www.linzqg.at
www.linzaqg.at
www.linzqag.at
www.linzwg.at
www.linzawg.at
www.linzwag.at
www.linzsg.at
www.linzasg.at
www.linzzg.at
www.linzazg.at
www.linzzag.at
www.linza.at
www.linzaf.at
www.linzagf.at
www.linzafg.at
www.linzav.at
www.linzagv.at
www.linzavg.at
www.linzat.at
www.linzagt.at
www.linzatg.at
www.linzab.at
www.linzagb.at
www.linzabg.at
www.linzay.at
www.linzagy.at
www.linzayg.at
www.linzah.at
www.linzagh.at
www.linzahg.at

linzag.at 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.

linzag.at 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.

LINZAG.AT LINZ AG

linzag.at Website Information

Advertisement

linzag.at Alexa Rank

linzag.at whois

linzag.at server information

Servers Location

linzag.at desktop page speed rank

linzag.at Desktop Speed Test Quick Summary

priority - 91Optimize images

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

Optimize the following images to reduce their size by 886.4KiB (41% reduction).

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

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

Remove render-blocking JavaScript:

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:

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2.1KiB (13% 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 543B (11% reduction).

linzag.at Desktop Resource Breakdown

linzag.at mobile page speed rank

linzag.at Mobile Speed Test Quick Summary

priority - 91Optimize images

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

Optimize the following images to reduce their size by 886.4KiB (41% reduction).

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

Your page has 6 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.

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 - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2.1KiB (13% 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 544B (11% reduction).

linzag.at Mobile Resource Breakdown

linzag.at mobile page usability

linzag.at Mobile Usability Test Quick Summary

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 418 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

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

linzag.at HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

A “charset” attribute on a “meta” element found after the first 1024 bytes.

Duplicate ID “fmSiteSearch”.

Duplicate ID “lag-site-search-input”.

Duplicate ID “q”.

An element with “role=tab” must be contained in, or owned by, an element with “role=tablist”.

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

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

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

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

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

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

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

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

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

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

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

The “for” attribute of the “label” element must refer to a non-hidden form control.

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

The first occurrence of ID “fmSiteSearch” was here.

The first occurrence of ID “lag-site-search-input” was here.

The first occurrence of ID “q” was here.

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