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://ogpnet.com
42
Perf
92
SEO
96
BP
100
A11y
Priority Issues
Structural Issues — fix in code (3)
Reduce unused CSS
Est savings of 80 KiB
Reduce unused JavaScript
Est savings of 620 KiB
Avoid enormous network payloads
Total size was 4,404 KiB
Environment-Sensitive Metrics — note trends, don't chase numbers (19)
First Contentful Paint
1.6 s~ env-sensitive
Largest Contentful Paint
2.7 s~ env-sensitive
Total Blocking Time
1,630 ms~ env-sensitive
Speed Index
3.1 s~ env-sensitive
Use efficient cache lifetimes
Est savings of 102 KiB~ env-sensitive
Document request latency
Est savings of 210 ms~ env-sensitive
Font display
Est savings of 50 ms~ env-sensitive
Forced reflow
~ env-sensitive
Improve image delivery
Est savings of 1,238 KiB~ env-sensitive
LCP request discovery
~ env-sensitive
Legacy JavaScript
Est savings of 15 KiB~ env-sensitive
Network dependency tree
~ env-sensitive
Render blocking requests
Est savings of 1,130 ms~ env-sensitive
Time to Interactive
5.1 s~ env-sensitive
Max Potential First Input Delay
800 ms~ env-sensitive
Reduce JavaScript execution time
2.9 s~ env-sensitive
Minimize main-thread work
4.6 s~ env-sensitive
Image elements do not have explicit `width` and `height`
~ env-sensitive
Avoid multiple page redirects
Est savings of 230 ms~ env-sensitive
42
Performance
92
SEO
96
Best Practices
100
Accessibility (LH)
Run time: 35.4s
Performance
First Contentful Paint
1.6 s~ env-sensitive
Largest Contentful Paint
2.7 s~ env-sensitive
Total Blocking Time
1,630 ms~ env-sensitive
Speed Index
3.1 s~ env-sensitive
Use efficient cache lifetimes
Est savings of 102 KiB~ env-sensitive
Document request latency
Est savings of 210 ms~ env-sensitive
Font display
Est savings of 50 ms~ env-sensitive
Forced reflow
~ env-sensitive
Improve image delivery
Est savings of 1,238 KiB~ env-sensitive
LCP request discovery
~ env-sensitive
Legacy JavaScript
Est savings of 15 KiB~ env-sensitive
Network dependency tree
~ env-sensitive
Render blocking requests
Est savings of 1,130 ms~ env-sensitive
Time to Interactive
5.1 s~ env-sensitive
Max Potential First Input Delay
800 ms~ env-sensitive
Reduce unused CSS
Est savings of 80 KiB
Reduce unused JavaScript
Est savings of 620 KiB
Avoid enormous network payloads
Total size was 4,404 KiB
Reduce JavaScript execution time
2.9 s~ env-sensitive
Minimize main-thread work
4.6 s~ env-sensitive
Image elements do not have explicit `width` and `height`
~ env-sensitive
Avoid multiple page redirects
Est savings of 230 ms~ env-sensitive
▸ 23 passed / informational
Cumulative Layout Shift
0.06~ env-sensitive
Layout shift culprits
~ env-sensitive
Optimize DOM size
~ env-sensitive
Duplicated JavaScript
~ env-sensitive
LCP breakdown
~ env-sensitive
3rd parties
~ env-sensitive
Optimize viewport for mobile
~ env-sensitive
Minify CSS
Minify JavaScript
User Timing marks and measures
8 user timings~ env-sensitive
Avoid long main-thread tasks
18 long tasks found~ env-sensitive
Network Requests
~ env-sensitive
Network Round Trip Times
30 ms~ env-sensitive
Server Backend Latencies
10 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
Initial server response time was short
Root document took 10 ms
Avoid large layout shifts
15 layout shifts found~ env-sensitive
SEO
Links do not have descriptive text
7 links found
▸ 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 are crawlable
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
Browser errors were logged to the console
▸ 18 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 clickjacking with XFO or CSP
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
Detected JavaScript libraries
Avoids deprecated APIs
Avoids third-party cookies
Page has valid source maps
No issues in the `Issues` panel in Chrome Devtools
Accessibility
Elements with visible text labels do not have matching accessible names.
▸ 39 passed / informational
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
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
`<frame>` or `<iframe>` elements have a title
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
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.
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
Identical links have the same purpose.