kolumbus.no Website Information

Daily Unique Visits: 3,690

Daily Page Views: 14,760

Income Per Day: $41

Estimated Value: $22,140

kolumbus.no is registered under .NO top-level domain. Please check other sites in .NO zone.

No name server records were found.

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website kolumbus.no position in Alexa rank database was 14312 and the lowest rank position was 975508. Current position of kolumbus.no in Alexa rank database is 340110.

Desktop speed score of kolumbus.no (63/100) is better than the results of 39.87% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of kolumbus.no (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 kolumbus.no (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.

kolumbus.no 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.

kolumbus.no 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.

% By looking up information in the domain registration directory
% service, you confirm that you accept the terms and conditions of the
% service:
% https://www.norid.no/en/domeneoppslag/vilkar/
%
% Norid AS holds the copyright to the lookup service, content,
% layout and the underlying collections of information used in the
% service (cf. the Act on Intellectual Property of May 2, 1961, No.
% 2). Any commercial use of information from the service, including
% targeted marketing, is prohibited. Using information from the domain
% registration directory service in violation of the terms and
% conditions may result in legal prosecution.
%
% The whois service at port 43 is intended to contribute to resolving
% technical problems where individual domains threaten the
% functionality, security and stability of other domains or the
% internet as an infrastructure. It does not give any information
% about who the holder of a domain is. To find information about a
% domain holder, please visit our website:
% https://www.norid.no/en/domeneoppslag/

Domain Information

NORID Handle...............: KOL1418D-NORID
Domain Name................: kolumbus.no
Registrar Handle...........: REG974-NORID
Tech-c Handle..............: NR184R-NORID
Name Server Handle.........: DNSN2051H-NORID
Name Server Handle.........: DNSN2052H-NORID
Name Server Handle.........: DNSN2410H-NORID

Additional information:
Created: 2016-03-10
Last updated: 2024-02-09

kolumbus.no server information

Servers Location

kolumbus.no desktop page speed rank

Last tested: 2018-12-17

Desktop Speed Bad

63/100

kolumbus.no Desktop Speed Test Quick Summary

priority - 38Optimize images

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

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

Compressing and resizing https://www.kolumbus.no/globalassets/images/imageg…&gstart=0,0&gend=0,150 could save 204.8KiB (86% reduction).
Compressing and resizing https://www.kolumbus.no/globalassets/images/imageg…776&height=0&mode=crop could save 106KiB (79% reduction).
Compressing and resizing https://www.kolumbus.no/globalassets/images/kolumb…776&height=0&mode=crop could save 53.8KiB (73% reduction).
Compressing https://www.kolumbus.no/globalassets/images/imageg…776&height=0&mode=crop could save 3KiB (11% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/sprites.png could save 1.2KiB (50% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/long-arrow-right.png could save 874B (87% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/white-long-arrow-right.png could save 114B (30% reduction).

priority - 9Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://kolumbus.no/
https://kolumbus.no/
https://www.kolumbus.no/

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

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

Remove render-blocking JavaScript:

https://www.kolumbus.no/public/js/manifest.js
https://www.kolumbus.no/public/js/modernizr.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700
https://www.kolumbus.no/public/vendor/css/v-636802…0000/jquery-ui.min.css
https://www.kolumbus.no/public/css/v-636802867880000000/kolumbus.css

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:

https://dc.services.visualstudio.com/v2/track (expiration not specified)
https://dl.episerver.net/13.0.5/epi-util/find.js (expiration not specified)
https://static.hotjar.com/c/hotjar-1059444.js?sv=5 (60 seconds)
https://az416426.vo.msecnd.net/scripts/a/ai.0.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-59XS78 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.kolumbus.no/globalassets/ikoner/kolumb…64&height=64&mode=crop (12 hours)
https://www.kolumbus.no/globalassets/ikoner/kortko…64&height=64&mode=crop (12 hours)
https://www.kolumbus.no/globalassets/ikoner/mobila…64&height=64&mode=crop (12 hours)

priority - 2Reduce server response time

In our test, your server responded in 0.36 seconds.

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 12.6KiB (69% reduction).

Compressing https://www.kolumbus.no/frontend/res/svg/site-footer-decorator.svg could save 9.2KiB (80% reduction).
Compressing https://www.kolumbus.no/frontend/res/svg/site-logo.svg could save 1.4KiB (56% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/kortko…64&height=64&mode=crop could save 1.1KiB (54% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/kolumb…64&height=64&mode=crop could save 368B (41% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/mobila…64&height=64&mode=crop could save 302B (38% reduction).
Compressing https://www.kolumbus.no/frontend/res/svg/green-checkmark.svg could save 252B (42% 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.1KiB (14% reduction).

Minifying https://www.kolumbus.no/ could save 1.1KiB (14% reduction) after compression.

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 886B (12% reduction).

Minifying https://www.kolumbus.no/public/vendor/css/v-636802…0000/jquery-ui.min.css could save 886B (12% reduction) after compression.

kolumbus.no Desktop Resource Breakdown

Total Resources	64
Number of Hosts	19
Static Resources	25
JavaScript Resources	29
CSS Resources	4

kolumbus.no mobile page speed rank

Last tested: 2018-12-17

Mobile Speed Bad

57/100

kolumbus.no Mobile Speed Test Quick Summary

priority - 34Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://kolumbus.no/
https://kolumbus.no/
https://www.kolumbus.no/

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

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

Remove render-blocking JavaScript:

https://www.kolumbus.no/public/js/manifest.js
https://www.kolumbus.no/public/js/modernizr.js

Optimize CSS Delivery of the following:

priority - 6Leverage 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 60.3KiB (13% reduction).

Compressing https://www.kolumbus.no/globalassets/images/imageg…&gstart=0,0&gend=0,150 could save 27.8KiB (12% reduction).
Compressing https://www.kolumbus.no/globalassets/images/imageg…776&height=0&mode=crop could save 18.9KiB (15% reduction).
Compressing https://www.kolumbus.no/globalassets/images/kolumb…776&height=0&mode=crop could save 8.4KiB (12% reduction).
Compressing https://www.kolumbus.no/globalassets/images/imageg…776&height=0&mode=crop could save 3KiB (11% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/sprites.png could save 1.2KiB (50% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/long-arrow-right.png could save 874B (87% reduction).
Compressing https://www.kolumbus.no/frontend/res/png/white-long-arrow-right.png could save 114B (30% reduction).

priority - 2Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 15.2KiB (71% reduction).

Compressing https://www.kolumbus.no/frontend/res/svg/site-footer-decorator.xs.svg could save 11.8KiB (80% reduction).
Compressing https://www.kolumbus.no/frontend/res/svg/site-logo.svg could save 1.4KiB (56% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/kortko…64&height=64&mode=crop could save 1.1KiB (54% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/kolumb…64&height=64&mode=crop could save 368B (41% reduction).
Compressing https://www.kolumbus.no/globalassets/ikoner/mobila…64&height=64&mode=crop could save 302B (38% reduction).
Compressing https://www.kolumbus.no/frontend/res/svg/green-checkmark.svg could save 252B (42% 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.1KiB (14% reduction).

Minifying https://www.kolumbus.no/ could save 1.1KiB (14% reduction) after compression.

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 886B (12% reduction).

Minifying https://www.kolumbus.no/public/vendor/css/v-636802…0000/jquery-ui.min.css could save 886B (12% reduction) after compression.

kolumbus.no Mobile Resource Breakdown

Total Resources	60
Number of Hosts	18
Static Resources	25
JavaScript Resources	27
CSS Resources	4

kolumbus.no mobile page usability

Last tested: 2018-12-17

Mobile Usability Good

94/100

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

The element <div class="block editoria…m-12 col-xs-12">Personvern</div> falls outside the viewport.

priority - 2Size 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 <form class="single-submit">Reis fra…Flere valg</form> and 1 others are close to other tap targets.

The tap target <label for="From" class="control-label">Reis fra</label> and 3 others are close to other tap targets.

The tap target <input id="From" type="text" name="From" class="form-control t…r-autocomplete"> and 1 others are close to other tap targets.

The tap target <input id="TravelDateTime_time" type="time" name="TravelDateTime_time" class="form-control"> is close to 1 other tap targets.

The tap target <label>Ankomst</label> is close to 1 other tap targets.

The tap target <input type="submit" class="btn btn-default btn-block"> is close to 1 other tap targets.

The tap target <a href="/reiseplanlegger/">Flere valg</a> and 1 others are close to other tap targets.

kolumbus.no HTML validation

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 8 Column: 1 - 104
"...E=edge"/> <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"/> <tit..."

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

Line: 99 Column: 1 - 52
"... </div> <header role="banner" class="navbar navbar-default"> <..."

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

Line: 169 Column: 1 - 99
"...n --> <nav id="sitenav" class="sitenav navbar-collapse collapse" role="navigation" aria-expanded="false"> <..."

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

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

Line: 441 Column: 49 - 289
"... <input Name="TravelDateTime_time" Value="17:58" class="form-control" id="TravelDateTime_time" name="TravelDateTime" pattern="^(?:(?:[0-1]{0,1}[0-9])|(?:2[0-3])):[0-5]{0,1}[0-9]$" placeholder="tt:mm" type="time" value="21.03.2018 17:58:39" /> ..."

The first occurrence of ID “Direction” was here.

Line: 459 Column: 53 - 189
"... <input checked="checked" data-val="true" data-val-required="Direction-Required" id="Direction" name="Direction" type="radio" value="1" /> ..."

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

Line: 564 Column: 17 - 50
"... <article class="common-list-item"> ..." Line: 597 Column: 17 - 50
"... <article class="common-list-item"> ..." Line: 643 Column: 17 - 50
"... <article class="common-list-item"> ..." Line: 684 Column: 13 - 46
"... <article class="common-list-item"> ..." Line: 703 Column: 13 - 46
"... <article class="common-list-item"> ..." Line: 722 Column: 13 - 46
"... <article class="common-list-item"> ..."

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

Line: 871 Column: 1 - 47
"...ooter --> <footer class="site-footer" role="contentinfo"> <..."

Errors

Element “div” is missing one or more of the following attributes: “role”.

Line: 88 Column: 1 - 98
"... --> <div id="mobileSearchbar" class="mobile-searchbar navbar-collapse collapse" aria-expanded="false"> <..."

Duplicate attribute “name”.

Line: 432 Column: - 471
"...Time_date" name="TravelDateTim..." Line: 441 Column: - 147
"...Time_time" name="TravelDateTim..."

Duplicate attribute “value”.

Line: 432 Column: - 531
"...pe="date" value="21.03.2018 17..." Line: 441 Column: - 265
"...pe="time" value="21.03.2018 17..."

Attribute “placeholder” is only allowed when the input type is “email”, “number”, “password”, “search”, “tel”, “text”, or “url”.

Line: 432 Column: 49 - 555
"... <input Name="TravelDateTime_date" Value="2018-03-21" class="form-control" data-format="YYYY-MM-DD" data-template="DD.MM.YYYY" data-val="true" data-val-date="The field Tidspunkt must be a date." data-val-datetime="TravelDateTime-BootstrapDateTime" data-val-datetime-date="TravelDateTime_date" data-val-datetime-time="TravelDateTime_time" data-val-required="Please enter a valid date and time." id="TravelDateTime_date" name="TravelDateTime" placeholder="dd.mm.åååå" type="date" value="21.03.2018 17:58:39" /> ..." Line: 441 Column: 49 - 289
"... <input Name="TravelDateTime_time" Value="17:58" class="form-control" id="TravelDateTime_time" name="TravelDateTime" pattern="^(?:(?:[0-1]{0,1}[0-9])|(?:2[0-3])):[0-5]{0,1}[0-9]$" placeholder="tt:mm" type="time" value="21.03.2018 17:58:39" /> ..."

Attribute “pattern” is only allowed when the input type is “email”, “password”, “search”, “tel”, “text”, or “url”.

Duplicate ID “Direction”.

Line: 470 Column: 53 - 116
"... <input id="Direction" name="Direction" type="radio" value="2" /> ..."

Attribute “loader” not allowed on element “div” at this point.

Line: 886 Column: 1 - 29
".../footer> <div loader class="ng-cloak">Vennli..."

kolumbus.no similar domains

Similar domains:

www.kolumbus.com
www.kolumbus.net
www.kolumbus.org
www.kolumbus.info
www.kolumbus.biz
www.kolumbus.us
www.kolumbus.mobi
www.olumbus.no
www.kolumbus.no
www.jolumbus.no
www.kjolumbus.no
www.jkolumbus.no
www.iolumbus.no
www.kiolumbus.no
www.ikolumbus.no
www.molumbus.no
www.kmolumbus.no
www.mkolumbus.no
www.lolumbus.no
www.klolumbus.no
www.lkolumbus.no
www.oolumbus.no
www.koolumbus.no
www.okolumbus.no
www.klumbus.no
www.kilumbus.no
www.koilumbus.no
www.kklumbus.no
www.koklumbus.no
www.kkolumbus.no
www.kllumbus.no
www.kollumbus.no
www.kplumbus.no
www.koplumbus.no
www.kpolumbus.no
www.koumbus.no
www.kopumbus.no
www.kolpumbus.no
www.kooumbus.no
www.koloumbus.no
www.kokumbus.no
www.kolkumbus.no
www.kolmbus.no
www.kolymbus.no
www.koluymbus.no
www.kolyumbus.no
www.kolhmbus.no
www.koluhmbus.no
www.kolhumbus.no
www.koljmbus.no
www.kolujmbus.no
www.koljumbus.no
www.kolimbus.no
www.koluimbus.no
www.koliumbus.no
www.kolubus.no
www.kolunbus.no
www.kolumnbus.no
www.kolunmbus.no
www.kolujbus.no
www.kolumjbus.no
www.kolukbus.no
www.kolumkbus.no
www.kolukmbus.no
www.kolumus.no
www.kolumvus.no
www.kolumbvus.no
www.kolumvbus.no
www.kolumgus.no
www.kolumbgus.no
www.kolumgbus.no
www.kolumhus.no
www.kolumbhus.no
www.kolumhbus.no
www.kolumnus.no
www.kolumbnus.no
www.kolumbs.no
www.kolumbys.no
www.kolumbuys.no
www.kolumbyus.no
www.kolumbhs.no
www.kolumbuhs.no
www.kolumbjs.no
www.kolumbujs.no
www.kolumbjus.no
www.kolumbis.no
www.kolumbuis.no
www.kolumbius.no
www.kolumbu.no
www.kolumbuw.no
www.kolumbusw.no
www.kolumbuws.no
www.kolumbue.no
www.kolumbuse.no
www.kolumbues.no
www.kolumbud.no
www.kolumbusd.no
www.kolumbuds.no
www.kolumbuz.no
www.kolumbusz.no
www.kolumbuzs.no
www.kolumbux.no
www.kolumbusx.no
www.kolumbuxs.no
www.kolumbua.no
www.kolumbusa.no
www.kolumbuas.no

kolumbus.no 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.

kolumbus.no 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.

KOLUMBUS.NO Kolumbus AS - mobilitet i Rogaland

kolumbus.no Website Information

Advertisement

kolumbus.no Alexa Rank

kolumbus.no whois

kolumbus.no server information

Servers Location

kolumbus.no desktop page speed rank

kolumbus.no Desktop Speed Test Quick Summary

priority - 38Optimize images

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

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

priority - 9Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

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

Your page has 2 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 - 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:

priority - 2Reduce server response time

In our test, your server responded in 0.36 seconds.

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 12.6KiB (69% 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.1KiB (14% 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 886B (12% reduction).

kolumbus.no Desktop Resource Breakdown

kolumbus.no mobile page speed rank

kolumbus.no Mobile Speed Test Quick Summary

priority - 34Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

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

Your page has 2 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 - 6Leverage 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 60.3KiB (13% reduction).

priority - 2Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 15.2KiB (71% 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.1KiB (14% 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 886B (12% reduction).

kolumbus.no Mobile Resource Breakdown

kolumbus.no mobile page usability

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

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

kolumbus.no HTML validation

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

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

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

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

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

The first occurrence of ID “Direction” was here.

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

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

Errors

Element “div” is missing one or more of the following attributes: “role”.

Duplicate attribute “name”.