Skip to content
https://ntnu.no

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

70

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.

RequestCache TTLTransfer Size
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff20.0 ms115.6 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js1800.0 s115.6 KiB
chat.kindlycdn.com/kindly-chat.js600.0 s88.4 KiB
/src/assets/fonts/IBMPlexSans-Medium.c4877bdfa15aef22d925...60.0 s79.7 KiB
survey.skyra.no/skyra-survey.js36000.0 s92.6 KiB
/media/chatbubble-images/6d899ed855c242a8917e78af20f3716d...0.0 ms10.8 KiB
siteimproveanalytics.com/js/siteanalyze_6000120.js86400.0 s25.0 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff20.0 ms5.3 KiB
www.ntnu.no/o/ntnu-theme/images/logo_ntnu_tag_norsk.svg0.0 ms4.5 KiB
www.ntnu.no/o/ntnu-theme/images/ntnu-logo-web-v1.svg0.0 ms1.3 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.

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.

URLEst Savings
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff265 ms
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff255 ms
/src/assets/fonts/IBMPlexSans-Medium.c4877bdfa15aef22d925...45 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...35 ms

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.

URLResource SizeEst Savings
div.clearfix > div.card-grid > a.card-grid-card > img.img div.clearfix > div.card-grid > a.card-grid-card > img.img
/documents/1289651112/1308286184/s_effekt_1100_550.jpg/44...492.8 KiB484.3 KiB
Studenter foran NTNUs hovedbygg i Trondheim div.clearfix > figure.mb-0 > picture > img.h-100
/documents/10137/8737969/studiestart2025-foto-erik-betsha...554.1 KiB356.4 KiB
Bilde av forsker som har samlet reinsdyrbæsj div.clearfix > div.card-grid > a.card-grid-card > img.img
/documents/1289651112/1308286184/malin-andersson-stavridi...275.0 KiB266.5 KiB
Tre personer ser på et skjelett div.clearfix > article.row > div.col-12 > img
/documents/10137/0/vimu-DSCF3725-forside.jpg/9166cd17-c34...190.1 KiB180.1 KiB
Fire studenter på biblioteket div.clearfix > article.row > div.col-12 > img
/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...130.8 KiB118.0 KiB
Fem mennesker på scene. Paneldiskusjon om kunstig intelligens. div.clearfix > div.card-grid > a.card-grid-card > img.img
/documents/1289651112/1308286184/ntnu-kveld_ai-2726_53333...95.3 KiB84.8 KiB
Ung mann sitter ved en pendel i bevegelse i Realfagbygget på NTNU-campus på Glø… div.clearfix > div.card-grid > a.card-grid-card > img.img
/documents/1289651112/1308286184/image-1-2048x1366.jpeg/2...93.6 KiB84.0 KiB
Studenter som sitter rundt et bord og prater div.clearfix > article.row > div.col-12 > img
/documents/1289651112/1391671168/NTNU_Studentrekruttering...84.7 KiB63.4 KiB
div.sc-fYdXmo > button.sc-hjsqBW > div.sc-oQLfz > img.sc-gUrTyB div.sc-fYdXmo > button.sc-hjsqBW > div.sc-oQLfz > img.sc-gUrTyB
/media/chatbubble-images/6d899ed855c242a8917e78af20f3716d...10.2 KiB9.9 KiB

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-1-IMG
nodeLabel: Studenter foran NTNUs hovedbygg i Trondheim
path: 1,HTML,1,BODY,1,DIV,1,SECTION,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,1,SECTION,0,DIV,1,DIV,0,DIV,1,DIV,2,FIGURE,1,PICTURE,2,IMG
selector: div.clearfix > figure.mb-0 > picture > img.h-100
snippet: <img alt="Studenter foran NTNUs hovedbygg i Trondheim" class="h-100 w-100" data-fileentryid="1377145553" src="/documents/10137/8737969/studiestart2025-foto-erik-betshammar-dt1800.jpg/5…" style="object-fit:cover;object-position:center;max-width:2250px;">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.ntnu.no/http/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.jshttp/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.jshttp/1.1
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...http/1.1
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...http/1.1
/combo?browserId=other&minifierType=&themeId=ntnutheme_WA...http/1.1
www.ntnu.no/o/js_loader_modules?t=1776871995145http/1.1
www.ntnu.no/o/js_loader_config?t=1776871995412http/1.1
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...http/1.1
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...http/1.1
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...http/1.1
www.ntnu.no/o/frontend-js-web/loader/config.jshttp/1.1
www.ntnu.no/o/frontend-js-web/loader/loader.3.jshttp/1.1
www.ntnu.no/o/js_bundle_config?t=1776872028683http/1.1
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...http/1.1
/combo?browserId=other&minifierType=css&languageId=nb_NO&...http/1.1
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...http/1.1
www.ntnu.no/o/ntnu-theme/images/ntnu-logo-web-v1.svghttp/1.1
/documents/10137/8737969/studiestart2025-foto-erik-betsha...http/1.1
/documents/10137/8737969/studiestart2025-foto-erik-betsha...http/1.1
/documents/1289651112/1391671168/NTNU_Studentrekruttering...http/1.1
/documents/1289651112/1308286184/ntnu-kveld_ai-2726_53333...http/1.1
/documents/1289651112/1308286184/image-1-2048x1366.jpeg/2...http/1.1
/documents/1289651112/1308286184/malin-andersson-stavridi...http/1.1
/documents/1289651112/1308286184/s_effekt_1100_550.jpg/44...http/1.1
/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...http/1.1
/documents/10137/0/vimu-DSCF3725-forside.jpg/9166cd17-c34...http/1.1
www.ntnu.no/o/ntnu-theme/images/logo_ntnu_tag_norsk.svghttp/1.1
/o/ntnu-theme/js/main.js?browserId=other&minifierType=js&...http/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.tablesorter.jshttp/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.slider.js?v=4.2.17http/1.1
www.ntnu.no/o/ntnu-theme/images/lexicon/icons.svghttp/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2http/1.1
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/o/frontend-js-web/liferay/available_languages.jsp?browse...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...http/1.1
www.ntnu.no/o/ntnu-theme/images/logoicon.icohttp/1.1

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
value: No additional origins are good candidates for preconnecting

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.

URLTransfer SizeDuration
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...143.1 KiB912 ms
www.ntnu.no/o/js_loader_modules?t=1776871995145137.9 KiB1.1 s
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...835 B281 ms
www.ntnu.no/o/js_bundle_config?t=17768720286835.4 KiB281 ms
www.ntnu.no/o/frontend-js-web/loader/loader.3.js26.0 KiB461 ms
www.ntnu.no/o/frontend-js-web/loader/config.js900 B281 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js95.7 KiB912 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...72.9 KiB732 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...29.3 KiB461 ms
www.ntnu.no/o/js_loader_config?t=1776871995412646 B281 ms
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...99.1 KiB822 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.js885 B281 ms
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...25.8 KiB461 ms
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...18.7 KiB371 ms
/combo?browserId=other&minifierType=css&languageId=nb_NO&...4.4 KiB281 ms
/combo?browserId=other&minifierType=&themeId=ntnutheme_WA...2.2 KiB281 ms
fonts.googleapis.com/css?family=Open+Sans:400italic,400,300,600,7002.4 KiB271 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 359 ms
URLTime Spent
ntnu.no/359 ms
www.ntnu.no/0.0 ms

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 84.6 KiB
URLTransfer SizeEst Savings
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js95.3 KiB69.8 KiB
www.ntnu.no/o/frontend-js-web/loader/loader.3.js25.5 KiB14.8 KiB

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: 180 ms 138.8 KiB
URLTransfer SizeEst Savings
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...98.6 KiB96.7 KiB
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...25.3 KiB23.8 KiB
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...18.3 KiB18.3 KiB

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: 180 ms 296.8 KiB
URLTransfer SizeEst Savings
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...142.6 KiB74.8 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js115.2 KiB58.9 KiB
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...72.4 KiB55.6 KiB
survey.skyra.no/skyra-survey.js92.2 KiB49.1 KiB
chat.kindlycdn.com/kindly-chat.js87.6 KiB29.9 KiB
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js95.3 KiB28.4 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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.

URLTransfer Size
/documents/10137/8737969/studiestart2025-foto-erik-betsha...554.8 KiB
/documents/10137/8737969/studiestart2025-foto-erik-betsha...523.7 KiB
/documents/1289651112/1308286184/s_effekt_1100_550.jpg/44...493.6 KiB
/documents/1289651112/1308286184/malin-andersson-stavridi...275.4 KiB
/documents/10137/0/vimu-DSCF3725-forside.jpg/9166cd17-c34...190.5 KiB
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...143.1 KiB
www.ntnu.no/o/js_loader_modules?t=1776871995145137.9 KiB
/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...130.8 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2115.6 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js115.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
Studenter foran NTNUs hovedbygg i Trondheim div.clearfix > figure.mb-0 > picture > img.h-100
/documents/10137/8737969/studiestart2025-foto-erik-betsha...
NTNU logo footer#blue-footer > div.container > div.end > img.ntnu-logo
www.ntnu.no/o/ntnu-theme/images/logo_ntnu_tag_norsk.svg

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Optimize viewport for mobile
●Minify CSS
●JavaScript execution time 0.4 s
●Minimizes main-thread work 0.8 s
●Avoid long main-thread tasks 3 long tasks found
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 20 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 120 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
92

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Studier Studentliv Forskning og innovasjon Om NTNU header#banner > div#navigation > div.container > div#navigationCollapse
Søk header#banner > div#navigation > div.container > div#searchCollapse

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For ansatte | For studenter | Innsida | Blackboard footer#blue-footer > div.container > div > ul.horizontal-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
www.ntnu.no/o/js_loader_modules?t=1776871995145
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...
www.ntnu.no/o/frontend-js-web/loader/loader.3.jswww.ntnu.no/o/frontend-js-web/loader/loader.3.js.map
www.ntnu.no/o/frontend-js-web/loader/config.jswww.ntnu.no/o/frontend-js-web/loader/config.js.map
●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 browser errors logged to the console
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
62Disallow /blogger/Syntax not understood
63Allow /blogger/guide/Syntax not understood
64Allow /blogger/ub-adbbm/Syntax not understood
65Allow /blogger/ub-arkeologi/Syntax not understood
66Allow /blogger/ub-lokalhistorie/Syntax not understood
67Allow /blogger/ub-realfag/Syntax not understood
68Allow /blogger/ub-teknologi/Syntax not understood
69Allow /blogger/ub-okonomi/Syntax not understood
70Allow /blogger/ub-samfunn/Syntax not understood
71Allow /blogger/ub-musikk/Syntax not understood
72Allow /blogger/ub-filosofi/Syntax not understood
73Allow /blogger/ub-kunstogmedier/Syntax not understood
74Allow /blogger/ub-litteratur/Syntax not understood
75Allow /blogger/ub-mh/Syntax not understood
76Allow /blogger/ls/Syntax not understood
77Allow /blogger/elsa/Syntax not understood
78Allow /blogger/medialab/Syntax not understood
79Allow /blogger/andersarvesen/Syntax not understood
80Allow /blogger/reset/Syntax not understood
81Allow /blogger/ub-spesialsamlinger/Syntax not understood
82Allow /blogger/healthpromotion/Syntax not understood
83Allow /blogger/ub-ark4/Syntax not understood
84Allow /blogger/forsklab-universell-utforming/Syntax not understood
85Allow /blogger/ub-bibliometri/Syntax not understood
86Allow /blogger/lor-ved-ntnu/Syntax not understood
87Allow /blogger/the-materialities-of-the-modern-breakthrough/Syntax not understood
88Allow /blogger/monica-rolfsen/Syntax not understood
89Allow /blogger/ole-bjorn-roste/Syntax not understood
90Allow /blogger/hunt/Syntax not understood
91Allow /blogger/teamntnu/Syntax not understood
92Allow /blogger/sekom/Syntax not understood
93Allow /blogger/allmennmedisin/Syntax not understood
94Allow /blogger/norpart/Syntax not understood
95Allow /blogger/fysikkforfakirer/Syntax not understood
96Allow /blogger/cpslab/Syntax not understood
97Allow /blogger/link/Syntax not understood
98Allow /blogger/humsam/Syntax not understood
99Allow /blogger/came/Syntax not understood
100Allow /blogger/nakensnegler/Syntax not understood
101Allow /blogger/realsocialmedia/Syntax not understood
102Allow /blogger/folkehelsebloggen/Syntax not understood
103Allow /blogger/teknat/Syntax not understood
104Allow /blogger/menneskets-tidsalder/Syntax not understood
105Allow /blogger/ingrid-schjolberg-ie/Syntax not understood
106Allow /blogger/richard-hann/Syntax not understood
107Allow /blogger/konpas/Syntax not understood
108Allow /blogger/consense/Syntax not understood
109Allow /blogger/afino/Syntax not understood
110Allow /blogger/lkb/Syntax not understood
111Allow /blogger/helse/Syntax not understood
112Allow /blogger/realfag/Syntax not understood
113Allow /blogger/uavicing/Syntax not understood
114Allow /blogger/ihb/Syntax not understood
115Allow /blogger/most/Syntax not understood
116Allow /blogger/iik-edu/Syntax not understood
117Allow /blogger/cius/Syntax not understood
118Allow /blogger/literaturogsamfunn/Syntax not understood
119Allow /blogger/arkitektur5/Syntax not understood
120Allow /blogger/omsorgsforskning/Syntax not understood
121Allow /blogger/iap/Syntax not understood
122Allow /blogger/fagkomblogg/Syntax not understood
123Allow /blogger/sprakstotte/Syntax not understood
124Allow /blogger/eladda/Syntax not understood
125Allow /blogger/unikup/Syntax not understood
126Allow /blogger/lotteryfantasy/Syntax not understood
127Allow /blogger/talkinnovation/Syntax not understood

To appear in search results, crawlers need access to your app.

○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 have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback