PageSpeed Insights Report
Accessibility scores shown here are from PageSpeed Insights's automated audit. For detailed axe-core violations, see the Accessibility + SEO report.
https://analyticpartners.com/knowledge-hub/blog/i-wrote-magic-quadrants-heres-how-i-read-them/
72
Perf
92
SEO
54
BP
100
A11y
Priority Issues
Structural Issues — fix in code (2)
Reduce unused CSS
Est savings of 21 KiB
Reduce unused JavaScript
Est savings of 270 KiB
Environment-Sensitive Metrics — note trends, don't chase numbers (13)
Total Blocking Time
640 ms~ env-sensitive
Speed Index
1.4 s~ env-sensitive
Use efficient cache lifetimes
Est savings of 468 KiB~ env-sensitive
Forced reflow
~ env-sensitive
Improve image delivery
Est savings of 299 KiB~ env-sensitive
Legacy JavaScript
Est savings of 23 KiB~ env-sensitive
Network dependency tree
~ env-sensitive
Render-blocking requests
Est savings of 360 ms~ env-sensitive
Time to Interactive
3.2 s~ env-sensitive
Max Potential First Input Delay
310 ms~ env-sensitive
Reduce JavaScript execution time
1.7 s~ env-sensitive
Minimize main-thread work
2.9 s~ env-sensitive
Image elements do not have explicit `width` and `height`
~ env-sensitive
72
Performance
92
SEO
54
Best Practices
100
Accessibility (LH)
Run time: 32.7s
Performance
Total Blocking Time
640 ms~ env-sensitive
Speed Index
1.4 s~ env-sensitive
Use efficient cache lifetimes
Est savings of 468 KiB~ env-sensitive
Forced reflow
~ env-sensitive
Improve image delivery
Est savings of 299 KiB~ env-sensitive
Legacy JavaScript
Est savings of 23 KiB~ env-sensitive
Network dependency tree
~ env-sensitive
Render-blocking requests
Est savings of 360 ms~ env-sensitive
Time to Interactive
3.2 s~ env-sensitive
Max Potential First Input Delay
310 ms~ env-sensitive
Reduce unused CSS
Est savings of 21 KiB
Reduce unused JavaScript
Est savings of 270 KiB
Reduce JavaScript execution time
1.7 s~ env-sensitive
Minimize main-thread work
2.9 s~ env-sensitive
Image elements do not have explicit `width` and `height`
~ env-sensitive
▸ 29 passed / informational
First Contentful Paint
0.4 s~ env-sensitive
Largest Contentful Paint
1.1 s~ env-sensitive
Cumulative Layout Shift
0.001~ env-sensitive
Layout shift culprits
~ env-sensitive
Document request latency
~ env-sensitive
Optimize DOM size
~ env-sensitive
Duplicated JavaScript
~ env-sensitive
Font display
~ env-sensitive
LCP breakdown
~ env-sensitive
3rd parties
~ env-sensitive
Optimize viewport for mobile
~ env-sensitive
Minify CSS
Minify JavaScript
Avoids enormous network payloads
Total size was 2,611 KiB
Avoid long main-thread tasks
9 long tasks found~ env-sensitive
Avoid non-composited animations
1 animated element found~ env-sensitive
Network Requests
~ env-sensitive
Network Round Trip Times
10 ms~ env-sensitive
Server Backend Latencies
50 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
Avoid multiple page redirects
~ env-sensitive
Initial server response time was short
Root document took 10 ms
Avoid large layout shifts
1 layout shift found~ env-sensitive
SEO
Links are not crawlable
▸ 10 passed / informational
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
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
2 warnings found
Uses third-party cookies
1 cookie found
Browser errors were logged to the console
Issues were logged in the `Issues` panel in Chrome Devtools
▸ 14 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
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
Page has the HTML doctype
Properly defines charset
Baseline Features
Detected JavaScript libraries
Page has valid source maps
Accessibility
No issues found.
▸ 41 passed / informational
`[aria-*]` attributes match their roles
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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
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.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
`autocomplete` attributes are used correctly
Elements with `role="none"` or `role="presentation"` do not have conflicts
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
Elements with visible text labels have matching accessible names.