Skip to content
https://au.dk

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.

68

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
cdn.apple-mapkit.com/mk/5.x.x/mapkit.js285.0 s232.3 KiB
cdn.au.dk/2016/assets/img/misc/aias.jpg0.0 ms199.2 KiB
cdn.au.dk/2016/assets/js/vendor.js0.0 ms123.2 KiB
cdn.cookie-script.com/s/a8ca7e688df75cd8a6a03fcab6d18143.js0.0 ms56.7 KiB
customer.cludo.com/scripts/bundles/search-script.min.js0.0 ms51.1 KiB
cdn.au.dk/apps/react/findwidget/6.0.2/app.js0.0 ms41.3 KiB
cdn.au.dk/2016/assets/css/app.css0.0 ms39.7 KiB
fonts.au.dk/fonts/aupassata_rg-webfont.woff20.0 ms33.1 KiB
fonts.au.dk/fonts/aupassata_bold-webfont.woff20.0 ms29.8 KiB
fonts.au.dk/fonts/autohinting/aupassata_bold-webfont.woff20.0 ms21.3 KiB
fonts.au.dk/fonts/au_icons.woff0.0 ms18.2 KiB
cdn.au.dk/components/umd/databox.js?v=2026041611000.0 ms16.3 KiB
cdn.au.dk/2016/assets/img/au_segl.svg0.0 ms16.3 KiB
cdn.au.dk/2016/assets/js/app.js0.0 ms15.3 KiB
cdn.au.dk/components/umd/alphabox.js?v=2026041611000.0 ms12.0 KiB
cdn.au.dk/components/umd/news.js?v=2026041611000.0 ms10.2 KiB
customer.cludo.com/css/511/2151/cludo-search.min.css0.0 ms8.5 KiB
cdn.au.dk/components/umd/all.css0.0 ms5.8 KiB
/npm/@aarhus-university/au-designsystem-delphinus@latest/...604800.0 s38.7 KiB
cdn.au.dk/res/cookiescript/cookie-modal.min.js?a=2023041712500.0 ms2.9 KiB
cdn.au.dk/apps/react/presentation/5.2.0/presentation.css0.0 ms2.5 KiB
cdn.au.dk/apps/react/some/3.4.0/some.css0.0 ms1.0 KiB
www.au.dk/typo3temp/assets/css/4adea90c81bdd79ac4f5be3b55a7851c.css?177425879814400.0 s1.3 KiB
www.au.dk/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2870.0 s726 B
/npm/@aarhus-university/au-designsystem-delphinus@latest/...604800.0 s3.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:56.354 source:map[column:74 line:71 type:source-location url:https://cdn.cookie-script.com/s/a8ca7e688df75cd8a6a03fcab6d18143.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:73.619 source:map[type:text value:[unattributed]]] map[reflowTime:4.125 source:map[column:7775 line:0 type:source-location url:https://cdn.au.dk/2016/assets/js/vendor.js urlProvider:network]] map[reflowTime:1.068 source:map[column:7753 line:0 type:source-location url:https://cdn.au.dk/2016/assets/js/vendor.js urlProvider:network]] map[reflowTime:0.452 source:map[column:8756 line:0 type:source-location url:https://cdn.au.dk/2016/assets/js/vendor.js urlProvider:network]] map[reflowTime:5.123 source:map[column:447 line:0 type:source-location url:https://cdn.jsdelivr.net/npm/@aarhus-university/au-designsystem-delphinus@latest/public/projects/typo3/js/app.js urlProvider:network]] map[reflowTime:56.255 source:map[column:274 line:16 type:source-location url:https://cdn.cookie-script.com/s/a8ca7e688df75cd8a6a03fcab6d18143.js urlProvider:network]] map[reflowTime:0.099 source:map[column:107 line:39 type:source-location url:https://cdn.cookie-script.com/s/a8ca7e688df75cd8a6a03fcab6d18143.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: Forskningens Døgn d. 22. april Hvorfor findes der legetøj? Hvordan opstod der …
path: 1,HTML,1,BODY,1,DIV,0,DIV
selector: body.general > div#c3772115 > div.row
snippet: <div class="row expanded hero" style="background-image: url(&quot;/fileadmin/www.au.dk/Hero-forside/Forskningens_Dogn…&quot;);">

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.

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.

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.column > div#c2494557 > a > img div.column > div#c2494557 > a > img
/fileadmin/www.au.dk/pressen/COLOURBOX2512779_kopier2_fol...824.1 KiB815.6 KiB
Aarhus Universitetspark i efterårssol med træer uden blade div.row > div.column > div#c2249814 > img
www.au.dk/fileadmin/_processed_/7/a/csm_Parken_efteraar_800px_07def1e842.jpg150.1 KiB141.9 KiB
div.column > div#c2766954 > a > img div.column > div#c2766954 > a > img
www.au.dk/fileadmin/www.au.dk/pressen/sort_felt.jpg5.9 KiB5.2 KiB

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: 827 ms
URLTime Spent
au.dk/827 ms
www.au.dk/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

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: 50 ms 74.2 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.

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
Aarhus Universitets segl header > div.row > div.large-1 > img.seal
cdn.au.dk/2016/assets/img/au_segl.svg
Aarhus Universitets' segl div.large-6 > div.row > div.large-6 > img.seal
cdn.au.dk/2016/assets/img/au_segl.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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.8 s
●Avoid long main-thread tasks 2 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 210 ms
●Server Backend Latencies 310 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 250 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
94

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies på au.dk div.row > div.small-12 > p.muted > a
Privatlivspolitik div.row > div.small-12 > p.muted > a
Tilgængelighedserklæring div.row > div.small-12 > p.muted > a
239037 / i40 body.general > footer > div.page-id

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Til studerende div#c2241368 > ul.utility > li > a
Til ph.d.er div#c2241368 > ul.utility > li > a
Til medarbejdere div#c2241368 > ul.utility > li > a
Institutter og fakulteter div#c2241368 > ul.utility > li > a
Bibliotek div#c2241368 > ul.utility > li > a
Presse div#c2241368 > ul.utility > li > a
Privatlivspolitik div.row > div.small-12 > p.muted > a
Tilgængelighedserklæring div.row > div.small-12 > p.muted > a

These items highlight common accessibility best practices.

○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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
●`<object>` elements have alternate text
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[accesskey]` values are unique
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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">`
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
100

Best Practices

●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Til studerende div#c2241368 > ul.utility > li > a
Til ph.d.er div#c2241368 > ul.utility > li > a
Til medarbejdere div#c2241368 > ul.utility > li > a
Institutter og fakulteter div#c2241368 > ul.utility > li > a

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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback