Skip to content
https://www.accenture.com/de-de/about/contact-us#contactus-formheader

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.

63

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
connect.facebook.net/en_US/fbevents.js1200.0 s98.6 KiB
cdn.cookielaw.org/scripttemplates/202601.1.0/otBannerSdk.js86400.0 s127.0 KiB
/signals/config/772335989453317?v=2.9.353&r=stable&domain...1200.0 s54.4 KiB
www.datadoghq-browser-agent.com/datadog-rum-v6.js14400.0 s59.3 KiB
/is/image/accenture/Accenture-contact-us-hero?ts=17798044...35983.0 s70.3 KiB
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad/resour...86400.0 s79.5 KiB
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad/resour...86400.0 s53.0 KiB
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad/resour...86400.0 s49.2 KiB
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad/resour...86400.0 s40.1 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms14.1 KiB
sc.lfeeder.com/lftracker_v1_JMvZ8gvn0Yma2pOd.js3600.0 s11.5 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms8.8 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.8 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.7 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.6 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.6 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.6 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.5 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.4 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.4 KiB
/etc/clientlibs/dtm-reactor/EN785f1994af8549b6b4a28ab29b6...0.0 ms7.2 KiB
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad/resour...86400.0 s16.9 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
/logos/2396a178-b290-4b3f-bf3f-5be727810e2a/eb81c031-0349...86400.0 s7.1 KiB
www.accenture.com/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js3600.0 s1.3 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.6 KiB
js.adsrvr.org/universal_pixel.js0.0 ms995 B
/is/content/accenture/Employee_80x80?ts=1781558360060&dpr...24385.0 s1.1 KiB
/is/content/accenture/Ecosystem_80x80-1?ts=1781558245122&...34727.0 s1.2 KiB
/?sid=JMvZ8gvn0Yma2pOd&data=eyJnYVRyYWNraW5nSWRzIjpbXSwiZ...0.0 ms320 B
cdn.cookielaw.org/logos/static/ot_close.svg86400.0 s603 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=772335989453317&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:74.227 source:map[type:text value:[unattributed]]]]

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#heroimage-1d1a9bd68d > div.rad-hero-image__photo > div#image-9265095823 > img.cmp-image__image div#heroimage-1d1a9bd68d > div.rad-hero-image__photo > div#image-9265095823 > img.cmp-image__image
/is/image/accenture/Accenture-contact-us-hero?ts=17798044...69.9 KiB54.8 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:68.0720009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:3206.1289990234377 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-DIV
nodeLabel: Willkommen auf accenture.com. Auf unserer Website verwenden wir Cookies, um bes…
path: 1,HTML,1,BODY,35,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV
selector: div.ot-sdk-row > div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text
snippet: <div id="onetrust-policy-text">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused 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: 120 ms 179.7 KiB
URLTransfer SizeEst Savings
/etc.clientlibs/cio-sites/clientlibs/clientlib-rad.lc-d30...168.5 KiB160.2 KiB
22.5 KiB19.5 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.

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.

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.

CategoryTime Spent
Script Evaluation1.6 s
Other555 ms
Script Parsing & Compilation224 ms
Style & Layout177 ms
Parse HTML & CSS68 ms
Garbage Collection54 ms
Rendering29 ms

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 12 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 70 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 0 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid large layout shifts
97

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#formoptions-d6e9e83356 > div.rad-form__field > div#radselect-form-options-932169080 > div#selectlistbox-form-options-932169080 div#formoptions-d6e9e83356 > div.rad-form__field > div#radselect-form-options-932169080 > div#selectlistbox-form-options-932169080
div#formoptions-8a20f45c57 > div.rad-form__field > div#radselect-form-options-878467730 > div#selectlistbox-form-options-878467730 div#formoptions-8a20f45c57 > div.rad-form__field > div#radselect-form-options-878467730 > div#selectlistbox-form-options-878467730

These are opportunities to improve keyboard navigation in your application.

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
Präferenz-Center div.rad-footer__links-container > ul.rad-footer__links-column > li.rad-footer__link-item > a.rad-footer__link
Impressum. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a#pc-policy-text-link-3
○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]` 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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`[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.
○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.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.
Ignoring duplicate Content-Security-Policy directive 'img-src'.

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.

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
69

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head > meta

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

○Structured data is valid
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback