Reports › ANP-205 › analyticwebstg-wpenginepowered-com-2026-07-21T17-07-20 › Lighthouse
Lighthouse Report
Accessibility scores shown here are from Lighthouse's automated audit. For detailed axe-core violations, see the Accessibility + SEO report.
https://analyticwebstg.wpenginepowered.com/knowledge-hub/blog/i-wrote-magic-quadrants-heres-how-i-read-them/
34
Perf
61
SEO
57
BP
100
A11y
 ▼
Priority Issues
Structural Issues — fix in code (6)▶
✗
Eliminate render-blocking resources
Est savings of 1,600 ms
✗
Properly size images
Est savings of 270 KiB
✗
Reduce unused CSS
Est savings of 14 KiB
✗
Reduce unused JavaScript
Est savings of 271 KiB
✗
Avoid serving legacy JavaScript to modern browsers
Est savings of 16 KiB
✗
Serve static assets with an efficient cache policy
13 resources found
Infrastructure Issues — backend fix required (1)▶
✗
Reduce initial server response time
Root document took 1,540 ms
Environment-Sensitive Metrics — note trends, don't chase numbers (21)▶
⚠
First Contentful Paint
3.5 s~ env-sensitive
⚠
Largest Contentful Paint
7.4 s~ env-sensitive
⚠
Total Blocking Time
3,660 ms~ env-sensitive
⚠
Speed Index
6.4 s~ env-sensitive
⚠
Use efficient cache lifetimes
Est savings of 361 KiB~ env-sensitive
⚠
Document request latency
Est savings of 1,440 ms~ env-sensitive
⚠
Forced reflow
~ env-sensitive
⚠
Improve image delivery
Est savings of 112 KiB~ env-sensitive
⚠
Legacy JavaScript
Est savings of 13 KiB~ env-sensitive
⚠
Network dependency tree
~ env-sensitive
⚠
Render blocking requests
Est savings of 1,770 ms~ env-sensitive
⚠
Time to Interactive
18.2 s~ env-sensitive
⚠
Max Potential First Input Delay
660 ms~ env-sensitive
⚠
Defer offscreen images
Est savings of 257 KiB~ env-sensitive
⚠
Avoid an excessive DOM size
997 elements~ env-sensitive
⚠
Reduce JavaScript execution time
6.2 s~ env-sensitive
⚠
Minimize main-thread work
10.9 s~ env-sensitive
⚠
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,550 ms~ env-sensitive
⚠
Largest Contentful Paint element
7,420 ms~ env-sensitive
⚠
Does not use passive listeners to improve scrolling performance
~ env-sensitive
⚠
Image elements do not have explicit `width` and `height`
~ env-sensitive
Scores
34
Performance
61
SEO
57
Best Practices
100
Accessibility (LH)
Run time: 26.0s
Performance
✗
First Contentful Paint
3.5 s~ env-sensitive
✗
Largest Contentful Paint
7.4 s~ env-sensitive
✗
Total Blocking Time
3,660 ms~ env-sensitive
✗
Speed Index
6.4 s~ env-sensitive
✗
Use efficient cache lifetimes
Est savings of 361 KiB~ env-sensitive
✗
Document request latency
Est savings of 1,440 ms~ env-sensitive
✗
Forced reflow
~ env-sensitive
✗
Improve image delivery
Est savings of 112 KiB~ env-sensitive
⚠
Legacy JavaScript
Est savings of 13 KiB~ env-sensitive
✗
Network dependency tree
~ env-sensitive
✗
Render blocking requests
Est savings of 1,770 ms~ env-sensitive
✗
Time to Interactive
18.2 s~ env-sensitive
✗
Max Potential First Input Delay
660 ms~ env-sensitive
✗
Eliminate render-blocking resources
Est savings of 1,600 ms
✗
Properly size images
Est savings of 270 KiB
✗
Defer offscreen images
Est savings of 257 KiB~ env-sensitive
✗
Reduce unused CSS
Est savings of 14 KiB
✗
Reduce unused JavaScript
Est savings of 271 KiB
✗
Reduce initial server response time
Root document took 1,540 ms
⚠
Avoid serving legacy JavaScript to modern browsers
Est savings of 16 KiB
⚠
Serve static assets with an efficient cache policy
13 resources found
✗
Avoid an excessive DOM size
997 elements~ env-sensitive
✗
Reduce JavaScript execution time
6.2 s~ env-sensitive
✗
Minimize main-thread work
10.9 s~ env-sensitive
✗
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,550 ms~ env-sensitive
✗
Largest Contentful Paint element
7,420 ms~ env-sensitive
⚠
Does not use passive listeners to improve scrolling performance
~ env-sensitive
⚠
Image elements do not have explicit `width` and `height`
~ env-sensitive
▸ 38 passed / informational
✓
Cumulative Layout Shift
0.011~ env-sensitive
ℹ
Layout shift culprits
~ env-sensitive
ℹ
Optimize DOM size
~ env-sensitive
✓
Duplicated JavaScript
~ env-sensitive
✓
Font display
~ env-sensitive
ℹ
LCP breakdown
~ env-sensitive
✓
Modern HTTP
~ env-sensitive
ℹ
3rd parties
~ env-sensitive
✓
Optimize viewport for mobile
~ env-sensitive
✓
Minify CSS
✓
Minify JavaScript
✓
Efficiently encode images
✓
Serve images in next-gen formats
✓
Enable text compression
✓
Preconnect to required origins
✓
Avoid multiple page redirects
~ env-sensitive
✓
Use HTTP/2
~ env-sensitive
✓
Use video formats for animated content
✓
Remove duplicate modules in JavaScript bundles
✓
Avoids enormous network payloads
Total size was 1,576 KiB
ℹ
Avoid chaining critical requests
29 chains found~ env-sensitive
✓
All text remains visible during webfont loads
~ env-sensitive
ℹ
Avoid large layout shifts
1 layout shift found~ env-sensitive
✓
Avoids `document.write()`
~ env-sensitive
ℹ
Avoid long main-thread tasks
20 long tasks found~ env-sensitive
ℹ
Avoid non-composited animations
1 animated element found~ env-sensitive
✓
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
~ env-sensitive
✓
Page didn't prevent back/forward cache restoration
~ env-sensitive
ℹ
Network Requests
~ env-sensitive
ℹ
Network Round Trip Times
40 ms~ env-sensitive
ℹ
Server Backend Latencies
120 ms~ env-sensitive
ℹ
Tasks
~ env-sensitive
ℹ
Diagnostics
~ env-sensitive
ℹ
Metrics
~ env-sensitive
ℹ
Screenshot Thumbnails
~ env-sensitive
ℹ
Final Screenshot
~ env-sensitive
ℹ
Script Treemap Data
~ env-sensitive
ℹ
Resources Summary
~ env-sensitive
SEO
✗
Page is blocked from indexing
✗
Links are not crawlable
▸ 9 passed / informational
✓
Document has a `<title>` element
✓
Document has a meta description
✓
Page has successful HTTP status code
✓
Links have descriptive text
✓
robots.txt is valid
✓
Image elements have `[alt]` attributes
✓
Document has a valid `hreflang`
✓
Document has a valid `rel=canonical`
◎
Structured data is valid
Best Practices
✗
Uses deprecated APIs
4 warnings found
✗
Uses third-party cookies
23 cookies found
✗
Browser errors were logged to the console
✗
Issues were logged in the `Issues` panel in Chrome Devtools
▸ 16 passed / informational
✓
Uses HTTPS
✓
Avoids requesting the geolocation permission on page load
✓
Avoids requesting the notification permission on page load
ℹ
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
✓
Allows users to paste into input fields
✓
Displays images with correct aspect ratio
✓
Serves images with appropriate resolution
✓
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
✓
Document uses legible font sizes
99.98% legible text
✓
Page has the HTML doctype
✓
Properly defines charset
ℹ
Detected JavaScript libraries
✓
Page has valid source maps
Accessibility
No issues found.
▸ 37 passed / informational
✓
`[aria-*]` attributes match their roles
✓
Uses ARIA roles only on compatible elements
✓
ARIA attributes are used as specified for the element's role
✓
Deprecated ARIA roles were not used
✓
`[aria-hidden="true"]` is not present on the document `<body>`
✓
`[aria-hidden="true"]` elements do not contain focusable descendents
✓
Elements use only permitted ARIA attributes
✓
`[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
✓
Background and foreground colors have a sufficient contrast ratio
✓
Document has a `<title>` element
✓
Heading elements appear in a sequentially-descending order
✓
`<html>` element has a `[lang]` attribute
✓
`<html>` element has a valid value for its `[lang]` attribute
✓
Image elements have `[alt]` attributes
✓
Image elements do not have `[alt]` attributes that are redundant text.
✓
Input buttons have discernible text.
✓
Form elements have associated labels
✓
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
✓
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
✓
Touch targets have sufficient size and spacing.
◎
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
Generated 7/21/2026, 5:10:27 PM · Jira ANP-205 · Run by [email protected]