Skip to content
https://accenture.wd103.myworkdayjobs.com/AccentureCareers/login?redirect=%2FAccentureCareers%2FuserHome

Lighthouse Mobile

· 0 checks — Mobile 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.

17

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.35878613486824684] map[node:map[boundingRect:map[bottom:1080 height:722 left:86 right:326 top:358 width:240] lhId:page-8-DIV nodeLabel:Sign In You may choose to sign in using your Google account as an alternative … path:1,HTML,1,BODY,7,DIV,1,DIV,0,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV selector:div#wd-Authentication-NO_METADATA_ID-uid5 > div > div.css-ecyovj > div snippet:<div dir="ltr"> type:node] score:0.326394540037383] map[node:map[boundingRect:map[bottom:1342 height:63 left:1 right:411 top:1279 width:410] lhId:page-4-DIV nodeLabel:© 2026 Workday, Inc. All rights reserved. path:1,HTML,1,BODY,7,DIV,1,DIV,1,DIV selector:body#vpsBody > div#workdayApplicationFrame > div.WKIP > div#mainFooter snippet:<div class="WNIP" id="mainFooter"> type:node] score:0.01714435448200468] map[node:map[boundingRect:map[bottom:1247 height:908 left:1 right:411 top:339 width:410] lhId:page-3-SECTION nodeLabel:Sign In You may choose to sign in using your Google account as an alternative … path:1,HTML,1,BODY,7,DIV,1,DIV,0,DIV,1,SECTION selector:div#workdayApplicationFrame > div.WKIP > div#mainContent > section.WCIP snippet:<section class="WCIP"> type:node] score:0.009132674435493603 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:339 height:78 left:0 right:412 top:261 width:412] lhId:page-0-IMG nodeLabel:body#vpsBody > div#d3d0a8ad1585470b8452ccaeae04b9fc > div.css-1mffsng > img.css-ap2pah path:1,HTML,1,BODY,0,DIV,3,DIV,0,IMG selector:body#vpsBody > div#d3d0a8ad1585470b8452ccaeae04b9fc > div.css-1mffsng > img.css-ap2pah snippet:<img alt="" src="/AccentureCareers/assets/banner" data-automation-id="banner" class="css-ap2pah"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1342 height:63 left:1 right:411 top:1279 width:410] lhId:page-4-DIV nodeLabel:© 2026 Workday, Inc. All rights reserved. path:1,HTML,1,BODY,7,DIV,1,DIV,1,DIV selector:body#vpsBody > div#workdayApplicationFrame > div.WKIP > div#mainFooter snippet:<div class="WNIP" id="mainFooter"> type:node] score:0.006114565913365558]]

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
body#vpsBody > div#d3d0a8ad1585470b8452ccaeae04b9fc > div.css-1mffsng > img.css-ap2pah body#vpsBody > div#d3d0a8ad1585470b8452ccaeae04b9fc > div.css-1mffsng > img.css-ap2pah
accenture.wd103.myworkdayjobs.com/AccentureCareers/assets/banner482.1 KiB476.5 KiB
careers home div.css-12et3te > div.css-jgqd7u > a.css-uma65v > img.css-1t8sqvc
accenture.wd103.myworkdayjobs.com/AccentureCareers/assets/logo7.2 KiB7.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:354.783 label:Time to first byte subpart:timeToFirstByte] map[duration:3209.689 label:Element render delay subpart:elementRenderDelay]]
lhId: page-2-P
nodeLabel: Accenture receives only the information necessary to enable account access and …
path: 1,HTML,1,BODY,7,DIV,1,DIV,0,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,P
selector: div.css-14ejnr5 > div.css-v07xv2 > div.css-hgwum5 > p
snippet: <p>

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

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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Sign In You may choose to sign in using your Google account as an alternative … div#wd-Authentication-NO_METADATA_ID-uid5 > div > div.css-ecyovj > div
0.326
© 2026 Workday, Inc. All rights reserved. body#vpsBody > div#workdayApplicationFrame > div.WKIP > div#mainFooter
0.017
Sign In You may choose to sign in using your Google account as an alternative … div#workdayApplicationFrame > div.WKIP > div#mainContent > section.WCIP
0.009
© 2026 Workday, Inc. All rights reserved. body#vpsBody > div#workdayApplicationFrame > div.WKIP > div#mainFooter
0.006

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 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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Parsing & Compilation3.3 s
Script Evaluation3.2 s
Other658 ms
Style & Layout457 ms
Parse HTML & CSS168 ms
Garbage Collection108 ms
Rendering101 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 reasonFailure type
The page has an unload handler in the main frame.Actionable

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.

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
careers home div.css-12et3te > div.css-jgqd7u > a.css-uma65v > img.css-1t8sqvc
accenture.wd103.myworkdayjobs.com/AccentureCareers/assets/logo

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

●Document request latency
●Optimize DOM size
●Forced reflow
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 16 long tasks found
●Avoid non-composited animations 5 animated elements found
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 160 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 270 ms
○INP breakdown
○LCP request discovery
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.

○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.
●`button`, `link`, and `menuitem` elements have accessible names
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
ExternalApp-0.js line 40957, col 193

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

SEO

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●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