C — https://ntnu.no | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

CMS · 1310 peers

You 72

Avg 73

At average

0 50 100

Better than 23% of CMS sites

Framework · 1225 peers

You 72

Avg 74

At average

0 50 100

Better than 24% of Framework sites

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fntnu.no)](https://beavercheck.com/results/f47c7b71-e5f1-40ed-b9b4-77695722f459)

HTML

<a href="https://beavercheck.com/results/f47c7b71-e5f1-40ed-b9b4-77695722f459"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fntnu.no" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fntnu.no

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~31%.

Speed (2)

Page takes 22.9s to load

+12% bounce

Users abandon at ~3s — you're 20.4s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 933ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

NOK 4,050 investment → NOK 9.27/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

NOK 4,050

4h · 5 findings

Monthly returns

NOK 9.27 /mo

~NOK 111 / year

Bandwidth savings NOK 9.27

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

NOK 1,350 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

kr4,050

4.5 developer hours at kr900/hr

Based on Norway rates (kr900/hr)

Quick wins

kr1,350 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

kr /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

NOK 10,041,676 / month at risk

~NOK 120,500,111 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

NOK 9.27 /mo

10773.1 MB/mo × 0.860 NOK/GB

Optimize transfer: save ~1.1 MB per page load
Saves NOK 9.27/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

9.61 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

22.91 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

933 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.096

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

11.47 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

23.38 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	0.0 ms	115.6 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	1800.0 s	115.6 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-solid-900.woff2	0.0 ms	90.1 KiB
chat.kindlycdn.com/kindly-chat.js	600.0 s	88.4 KiB
/src/assets/fonts/IBMPlexSans-Medium.c4877bdfa15aef22d925...	60.0 s	79.7 KiB
/src/assets/fonts/IBMPlexSans-Regular.2c412e2f77ae69aa215...	60.0 s	75.0 KiB
survey.skyra.no/skyra-survey.js	36000.0 s	92.6 KiB
/media/chatbubble-images/6d899ed855c242a8917e78af20f3716d...	0.0 ms	10.8 KiB
siteimproveanalytics.com/js/siteanalyze_6000120.js	86400.0 s	25.0 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	0.0 ms	5.3 KiB
www.ntnu.no/o/ntnu-theme/images/logo_ntnu_tag_norsk.svg	0.0 ms	4.5 KiB
www.ntnu.no/o/ntnu-theme/images/ntnu-logo-web-v1.svg	0.0 ms	1.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.

URL	Est Savings
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	110 ms
www.ntnu.no/o/ntnu-theme/webfonts/fa-solid-900.woff2	65 ms
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	60 ms
/src/assets/fonts/IBMPlexSans-Medium.c4877bdfa15aef22d925...	50 ms
/src/assets/fonts/IBMPlexSans-Regular.2c412e2f77ae69aa215...	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.

	URL	Resource Size	Est 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 KiB	479.0 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 KiB	261.2 KiB
Studenter foran NTNUs hovedbygg i Trondheim `div.clearfix > figure.mb-0 > picture > img.h-100`	/o/adaptive-media/image/1377145565/Preview-1000x0/studies...	302.1 KiB	260.6 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 KiB	174.4 KiB
Fire studenter på biblioteket `div.clearfix > article.row > div.col-12 > img`	/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...	130.8 KiB	115.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 KiB	79.2 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 KiB	78.4 KiB
Studenter som sitter rundt et bord og prater `div.clearfix > article.row > div.col-12 > img`	/documents/1289651112/1391671168/NTNU_Studentrekruttering...	84.7 KiB	76.7 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 KiB	10.0 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:407.539 label:Time to first byte subpart:timeToFirstByte] map[duration:55.561 label:Resource load delay subpart:resourceLoadDelay] map[duration:596.549 label:Resource load duration subpart:resourceLoadDuration] map[duration:1511.878 label:Element render delay subpart:elementRenderDelay]]

lhId: page-2-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,1,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="1377145565" src="https://www.ntnu.no/o/adaptive-media/image/1377145565/Preview-1000x0/studi…" style="object-fit:cover;">

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-2-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,1,FIGURE,1,PICTURE,2,IMG

selector: div.clearfix > figure.mb-0 > picture > img.h-100

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.

URL	Protocol
www.ntnu.no/	http/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	http/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.js	http/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=1776870929928	http/1.1
www.ntnu.no/o/js_loader_config?t=1776870930203	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
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	http/1.1
www.ntnu.no/o/frontend-js-web/loader/config.js	http/1.1
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	http/1.1
www.ntnu.no/o/js_bundle_config?t=1776870963084	http/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.svg	http/1.1
/o/adaptive-media/image/1377145565/Preview-1000x0/studies...	http/1.1
/o/adaptive-media/image/1377145553/Preview-1000x0/studies...	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.svg	http/1.1
/o/ntnu-theme/js/main.js?browserId=other&minifierType=js&...	http/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.tablesorter.js	http/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.slider.js?v=4.2.17	http/1.1
www.ntnu.no/o/ntnu-theme/images/lexicon/icons.svg	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/webfonts/fa-solid-900.woff2	http/1.1
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	http/1.1
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	http/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.ico	http/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

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
www.ntnu.no/o/js_loader_modules?t=1776870929928	137.9 KiB	6.5 s
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	143.1 KiB	6.1 s
www.ntnu.no/o/js_bundle_config?t=1776870963084	5.4 KiB	815 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	835 B	614 ms
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	26.0 KiB	2.4 s
www.ntnu.no/o/frontend-js-web/loader/config.js	900 B	614 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.7 KiB	5.5 s
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	72.9 KiB	4.2 s
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	29.3 KiB	2.6 s
www.ntnu.no/o/js_loader_config?t=1776870930203	646 B	614 ms
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...	99.1 KiB	5.3 s
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...	25.8 KiB	2.4 s
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.js	885 B	614 ms
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...	18.7 KiB	1.8 s
/combo?browserId=other&minifierType=css&languageId=nb_NO&...	4.4 KiB	815 ms
/combo?browserId=other&minifierType=&themeId=ntnutheme_WA...	2.2 KiB	614 ms
fonts.googleapis.com/css?family=Open+Sans:400italic,400,300,600,700	2.4 KiB	820 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: 916 ms

URL	Time Spent
ntnu.no/	916 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

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

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: 800 ms 84.6 KiB

URL	Transfer Size	Est Savings
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.3 KiB	69.8 KiB
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	25.5 KiB	14.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: 1.0 s 139.4 KiB

URL	Transfer Size	Est Savings
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...	98.6 KiB	97.4 KiB
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...	25.3 KiB	23.8 KiB
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...	18.3 KiB	18.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 2.3 s 296.9 KiB

URL	Transfer Size	Est Savings
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	142.6 KiB	75.0 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	115.2 KiB	58.9 KiB
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	72.4 KiB	55.6 KiB
survey.skyra.no/skyra-survey.js	92.2 KiB	49.1 KiB
chat.kindlycdn.com/kindly-chat.js	87.6 KiB	29.9 KiB
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.3 KiB	28.4 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
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	828 ms	481 ms	69 ms
Unattributable	510 ms	23 ms	0.0 ms
www.ntnu.no/	503 ms	115 ms	9.4 ms
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	406 ms	373 ms	32 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	285 ms	232 ms	26 ms
/combo/?browserId=other&minifierType=&languageId=nb_NO&b=...	239 ms	209 ms	8.6 ms
survey.skyra.no/skyra-survey.js	172 ms	142 ms	29 ms
www.ntnu.no/o/js_loader_modules?t=1776870929928	149 ms	45 ms	103 ms
chat.kindlycdn.com/kindly-chat.js	114 ms	72 ms	33 ms
siteimproveanalytics.com/js/siteanalyze_6000120.js	112 ms	49 ms	12 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	72 ms	22 ms	49 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	1.8 s
Other	586 ms
Script Parsing & Compilation	442 ms
Style & Layout	417 ms
Parse HTML & CSS	144 ms
Garbage Collection	109 ms
Rendering	45 ms

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 reason	Failure 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.

URL	Transfer Size
/documents/1289651112/1308286184/s_effekt_1100_550.jpg/44...	493.6 KiB
/o/adaptive-media/image/1377145565/Preview-1000x0/studies...	302.9 KiB
/documents/1289651112/1308286184/malin-andersson-stavridi...	275.4 KiB
/documents/10137/0/vimu-DSCF3725-forside.jpg/9166cd17-c34...	190.5 KiB
/o/adaptive-media/image/1377145553/Preview-1000x0/studies...	185.9 KiB
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	143.1 KiB
www.ntnu.no/o/js_loader_modules?t=1776870929928	137.9 KiB
/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...	130.8 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	115.6 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	115.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`	/o/adaptive-media/image/1377145565/Preview-1000x0/studies...
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.

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Optimize viewport for mobile

●Minify CSS

●Avoid long main-thread tasks 15 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 110 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Meny `div#navigation > div.container > div.navbar-buttons > button#nav-toggle-btn`

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

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

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

○`[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 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

○Form elements have associated labels

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

URL	Map URL
www.ntnu.no/o/js_loader_modules?t=1776870929928
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.js	www.ntnu.no/o/frontend-js-web/loader/loader.3.js.map
www.ntnu.no/o/frontend-js-web/loader/config.js	www.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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.07 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.37 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

22 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.07 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.05 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	0.0 ms	115.6 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	1800.0 s	115.6 KiB
chat.kindlycdn.com/kindly-chat.js	600.0 s	88.4 KiB
/src/assets/fonts/IBMPlexSans-Medium.c4877bdfa15aef22d925...	60.0 s	79.7 KiB
survey.skyra.no/skyra-survey.js	36000.0 s	92.6 KiB
/media/chatbubble-images/6d899ed855c242a8917e78af20f3716d...	0.0 ms	10.8 KiB
siteimproveanalytics.com/js/siteanalyze_6000120.js	86400.0 s	25.0 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	0.0 ms	5.3 KiB
www.ntnu.no/o/ntnu-theme/images/logo_ntnu_tag_norsk.svg	0.0 ms	4.5 KiB
www.ntnu.no/o/ntnu-theme/images/ntnu-logo-web-v1.svg	0.0 ms	1.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.

URL	Est Savings
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	65 ms
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	55 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.

	URL	Resource Size	Est 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 KiB	484.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 KiB	356.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 KiB	266.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 KiB	180.1 KiB
Fire studenter på biblioteket `div.clearfix > article.row > div.col-12 > img`	/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...	130.8 KiB	118.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 KiB	84.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 KiB	84.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 KiB	63.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 KiB	9.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.

URL	Protocol
www.ntnu.no/	http/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	http/1.1
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.js	http/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=1776871995145	http/1.1
www.ntnu.no/o/js_loader_config?t=1776871995412	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
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	http/1.1
www.ntnu.no/o/frontend-js-web/loader/config.js	http/1.1
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	http/1.1
www.ntnu.no/o/js_bundle_config?t=1776872028683	http/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.svg	http/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.svg	http/1.1
/o/ntnu-theme/js/main.js?browserId=other&minifierType=js&...	http/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.tablesorter.js	http/1.1
www.ntnu.no/o/ntnu-theme/js/jquery.slider.js?v=4.2.17	http/1.1
www.ntnu.no/o/ntnu-theme/images/lexicon/icons.svg	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/webfonts/fa-light-300.woff2	http/1.1
www.ntnu.no/o/ntnu-theme/webfonts/fa-brands-400.woff2	http/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.ico	http/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.

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.

URL	Transfer Size	Duration
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	143.1 KiB	912 ms
www.ntnu.no/o/js_loader_modules?t=1776871995145	137.9 KiB	1.1 s
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	835 B	281 ms
www.ntnu.no/o/js_bundle_config?t=1776872028683	5.4 KiB	281 ms
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	26.0 KiB	461 ms
www.ntnu.no/o/frontend-js-web/loader/config.js	900 B	281 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.7 KiB	912 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	72.9 KiB	732 ms
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	29.3 KiB	461 ms
www.ntnu.no/o/js_loader_config?t=1776871995412	646 B	281 ms
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...	99.1 KiB	822 ms
www.ntnu.no/o/frontend-js-lodash-web/lodash/util.js	885 B	281 ms
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...	25.8 KiB	461 ms
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...	18.7 KiB	371 ms
/combo?browserId=other&minifierType=css&languageId=nb_NO&...	4.4 KiB	281 ms
/combo?browserId=other&minifierType=&themeId=ntnutheme_WA...	2.2 KiB	281 ms
fonts.googleapis.com/css?family=Open+Sans:400italic,400,300,600,700	2.4 KiB	271 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

URL	Time 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

URL	Transfer Size	Est Savings
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.3 KiB	69.8 KiB
www.ntnu.no/o/frontend-js-web/loader/loader.3.js	25.5 KiB	14.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

URL	Transfer Size	Est Savings
/o/ntnu-theme/css/clay.css?browserId=other&themeId=ntnuth...	98.6 KiB	96.7 KiB
/o/ntnu-theme/css/main.css?browserId=other&themeId=ntnuth...	25.3 KiB	23.8 KiB
/o/frontend-css-web/main.css?browserId=other&themeId=ntnu...	18.3 KiB	18.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 180 ms 296.8 KiB

URL	Transfer Size	Est Savings
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	142.6 KiB	74.8 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	115.2 KiB	58.9 KiB
/combo?browserId=other&minifierType=js&languageId=nb_NO&b...	72.4 KiB	55.6 KiB
survey.skyra.no/skyra-survey.js	92.2 KiB	49.1 KiB
chat.kindlycdn.com/kindly-chat.js	87.6 KiB	29.9 KiB
www.ntnu.no/o/frontend-js-lodash-web/lodash/lodash.js	95.3 KiB	28.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 reason	Failure 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.

URL	Transfer 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=1776871995145	137.9 KiB
/documents/10137/0/NTNU_Studentrekruttering_BERREDSCF9123...	130.8 KiB
www.ntnu.no/o/ntnu-theme/webfonts/fa-light-300.woff2	115.6 KiB
chat.kindlycdn.com/KindlyChat-baacf46311ce02247f2c.js	115.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

Accessibility

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map 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.js	www.ntnu.no/o/frontend-js-web/loader/loader.3.js.map
www.ntnu.no/o/frontend-js-web/loader/config.js	www.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

SEO

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

Results for https://ntnu.no

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Tables and lists

Best Practices

General

SEO

Crawling and Indexing

Keyboard Shortcuts