Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
norriq.com/assets/images/norriq_logo.svg	14400.0 s	16.6 KiB
norriq-it.activehosted.com/f/embed.php?id=116	120.0 s	10.4 KiB
scripts.clarity.ms/0.8.64/clarity.js	86400.0 s	25.1 KiB
sc.lfeeder.com/lftracker_v1_p1e024BYN1K7GB6d.js	3600.0 s	11.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/?sid=p1e024BYN1K7GB6d&data=eyJnYVRyYWNraW5nSWRzIjpbXSwiZ...	0.0 ms	319 B
norriq.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172786.0 s	1.0 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:106.896 source:map[column:59091 line:2 type:source-location url:https://scripts.clarity.ms/0.8.64/clarity.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:68.471 source:map[type:text value:[unattributed]]] map[reflowTime:0.586 source:map[column:22081 line:0 type:source-location url:https://norriq.com/_nuxt/DYtb03Hs.js urlProvider:network]] map[reflowTime:22.479 source:map[column:15443 line:17 type:source-location url:https://norriq.com/_nuxt/S8mCvV7s.js urlProvider:network]] map[reflowTime:24.405 source:map[column:59856 line:17 type:source-location url:https://norriq.com/_nuxt/S8mCvV7s.js urlProvider:network]] map[reflowTime:4.95 source:map[column:21126 line:17 type:source-location url:https://norriq.com/_nuxt/S8mCvV7s.js urlProvider:network]] map[reflowTime:106.896 source:map[column:23243 line:1 type:source-location url:https://scripts.clarity.ms/0.8.64/clarity.js urlProvider:network]] map[reflowTime:0.21 source:map[column:10 line:25 type:source-location url: urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
welcome to NORRIQ `div.absolute > div.responsive-picture > picture > img`	/images/proxy/_/rs:fill:768:320/g:fp:0.5314849134915338:0...	66.7 KiB	56.3 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:7959.242 label:Time to first byte subpart:timeToFirstByte] map[duration:1318.725 label:Resource load delay subpart:resourceLoadDelay] map[duration:918.541 label:Resource load duration subpart:resourceLoadDuration] map[duration:2233.261 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: welcome to NORRIQ

path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,6,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,1,PICTURE,3,IMG

selector: div.absolute > div.responsive-picture > picture > img

snippet: <img width="1920" height="800" alt="welcome to NORRIQ" loading="lazy" onerror="this.setAttribute('data-error', 1)" fetchpriority="high" data-nuxt-pic="" src="https://api.live.norriqmarketing.norriq.dev/images/proxy/_/rs:fill:768:320…" sizes="(max-width: 640px) 100vw, (max-width: 768px) 768px, (max-width: 1024px) 99…" srcset="https://api.live.norriqmarketing.norriq.dev/images/proxy/_/rs:fill:1:800/g…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: welcome to NORRIQ

path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,6,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,1,PICTURE,3,IMG

selector: div.absolute > div.responsive-picture > picture > img

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
norriq.com/_nuxt/swiper-vue.DCASaf05.css	5.1 KiB	1.2 s
norriq.com/_nuxt/BaseButton.BUAvN_sI.css	789 B	1.0 s
norriq.com/_nuxt/entry.nFDbE3da.css	922 B	717 ms
norriq.com/_nuxt/ResponsivePicture.CV_fKwNJ.css	648 B	1.0 s
norriq.com/_nuxt/ArticleItem.CfABJPLY.css	749 B	1.0 s
norriq.com/_nuxt/RelatedArticles.DOkUA6q1.css	745 B	1.0 s
norriq.com/_nuxt/TagList.Bbwuzi22.css	866 B	1.0 s
norriq.com/_nuxt/CaseItem.D0-8-OSo.css	1.0 KiB	1.0 s
norriq.com/_nuxt/VideoComponent.global.vqozfDpc.css	1.0 KiB	1.0 s
norriq.com/_nuxt/CmsContentRenderer.BejON6nm.css	1.0 KiB	1.0 s
norriq.com/_nuxt/default.CIcB7IDi.css	1.2 KiB	1.0 s

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.bunny.net/ibm-plex-sans/files/ibm-plex-sans-latin-400-normal.woff2	5.0 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 7.8 s

URL	Time Spent
norriq.com/	7.9 s

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.5 s 272.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-MLHMMTC	166.9 KiB	83.0 KiB
www.googletagmanager.com/gtag/js?id=G-S9W0724HET&cx=c&gtm=4e6581	157.9 KiB	68.2 KiB
www.googletagmanager.com/gtag/js?id=AW-693601342&cx=c&gtm=4e6581	147.2 KiB	66.7 KiB
norriq.com/_nuxt/CUaqHaYT.js	110.4 KiB	34.3 KiB
norriq.com/_nuxt/S8mCvV7s.js	58.9 KiB	20.2 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	2.5 s	942 ms	0.0 ms
norriq.com/	1.7 s	189 ms	3.5 ms
norriq.com/_nuxt/S8mCvV7s.js	870 ms	90 ms	1.6 ms
norriq.com/_nuxt/Dx4LfC2W.js	763 ms	751 ms	0.1 ms
www.googletagmanager.com/gtag/js?id=AW-693601342&cx=c&gtm=4e6581	409 ms	362 ms	43 ms
scripts.clarity.ms/0.8.64/clarity.js	371 ms	239 ms	7.7 ms
www.googletagmanager.com/gtm.js?id=GTM-MLHMMTC	366 ms	272 ms	87 ms
www.googletagmanager.com/gtag/js?id=G-S9W0724HET&cx=c&gtm=4e6581	287 ms	223 ms	60 ms
/uc.js?language=EN&gcmEnabledByConsentLibrary=false	257 ms	71 ms	7.4 ms
norriq.com/_nuxt/CUaqHaYT.js	114 ms	24 ms	1.6 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	82 ms	51 ms	3.2 ms
sc.lfeeder.com/lftracker_v1_p1e024BYN1K7GB6d.js	79 ms	72 ms	5.0 ms
policy.app.cookieinformation.com/latest/norriq.com/en.js	62 ms	7.9 ms	24 ms
norriq-it.activehosted.com/f/embed.php?id=116	51 ms	22 ms	13 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.7 s
Other	2.3 s
Style & Layout	1.5 s
Parse HTML & CSS	417 ms
Script Parsing & Compilation	264 ms
Garbage Collection	218 ms
Rendering	171 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 100.1 KiB

URL	Transfer Size	Est Savings
*,::backdrop,:after,:before{--tw-border-spacing-x:0;--tw-border-spacing-y:0;--tw-translate-x:0;--tw…	101.6 KiB	100.1 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/v3-1/playback/b68f7782-20d2-4e04-9a63-867e8f41b6a7/e3aa2...	18.0 MiB
www.googletagmanager.com/gtm.js?id=GTM-MLHMMTC	167.3 KiB
www.googletagmanager.com/gtag/js?id=G-S9W0724HET&cx=c&gtm=4e6581	158.0 KiB
/images/proxy/_/rs:fit:900:1400/g:ce/plain/https://cms.no...	152.2 KiB
norriq.com/	149.9 KiB
www.googletagmanager.com/gtag/js?id=AW-693601342&cx=c&gtm=4e6581	147.3 KiB
norriq.com/_nuxt/CUaqHaYT.js	110.9 KiB
/images/proxy/_/rs:fit:900:1400/g:ce/plain/https://cms.no...	82.1 KiB
/images/proxy/_/rs:fill:900:1200/g:ce/plain/https://cms.n...	77.5 KiB
/images/proxy/_/rs:fit:1200:0/g:ce/plain/https://cms.norr...	72.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
logo `div#coiPage-1 > div.coi-banner__summary > div.coi-banner__header > img`	cms.norriq.com/media/1p0bpdcv/norriq-logo_dark-blue2.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 16 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 3 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 560 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 1 layout shift found

○INP breakdown

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.lg:flex > div.flex > div.relative > div#headlessui-popover-button-v-0-2 `div.lg:flex > div.flex > div.relative > div#headlessui-popover-button-v-0-2`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
toggle-for-Strictly necessary `div.coi-banner-consent-field > div#switch-cookie_cat_necessary > div.coi-checkboxes > div.checkbox-toggle`
toggle-for-Functional `div.coi-banner-consent-field > div#switch-cookie_cat_functional > div.coi-checkboxes > div.checkbox-toggle`
toggle-for-Statistical `div.coi-banner-consent-field > div#switch-cookie_cat_statistic > div.coi-checkboxes > div.checkbox-toggle`
toggle-for-Marketing `div.coi-banner-consent-field > div#switch-cookie_cat_marketing > div.coi-checkboxes > div.checkbox-toggle`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.relative > div#headlessui-popover-button-v-0-2 > button.focus:outline-none `div.flex > div.relative > div#headlessui-popover-button-v-0-2 > button.focus:outline-none`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link `ul.navigation-grid-component > li.navigation-grid-item > article.navigation-grid-card-component > a.n-link`
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static `div.swiper-wrapper > div.swiper-slide > div.case-item > a.static`
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static `div.swiper-wrapper > div.swiper-slide > div.case-item > a.static`
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static `div.swiper-wrapper > div.swiper-slide > div.case-item > a.static`
div.swiper-wrapper > div.swiper-slide > div.case-item > a.static `div.swiper-wrapper > div.swiper-slide > div.case-item > a.static`
div.swiper-wrapper > div.swiper-slide > article.relative > a.static `div.swiper-wrapper > div.swiper-slide > article.relative > a.static`
div.swiper-wrapper > div.swiper-slide > article.relative > a.static `div.swiper-wrapper > div.swiper-slide > article.relative > a.static`
div.swiper-wrapper > div.swiper-slide > article.relative > a.static `div.swiper-wrapper > div.swiper-slide > article.relative > a.static`
div.swiper-wrapper > div.swiper-slide > article.relative > a.static `div.swiper-wrapper > div.swiper-slide > article.relative > a.static`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Industry knowledge. Business understanding. Technology insight. `div.flex > div > div.text-editor > h4`
Please contact us `div.lg:max-w-[475px] > div > div.text-editor > h4`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
norriq.com/favicon.png	`Failed to load resource: the server responded with a status of 404 ()`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
tools.google.com/dlpage/gaoptout	here
norriq.com/cases	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`