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://rab2b.com
85
Perf
92
SEO
100
BP
96
A11y
85
Performance
92
SEO
100
Best Practices
96
Accessibility (LH)
Run time: 29.5s
Performance
Largest Contentful Paint
1.3 s
Total Blocking Time
240 ms
Speed Index
1.7 s
Use efficient cache lifetimes
Est savings of 767 KiB
Document request latency
Est savings of 120 ms
Forced reflow
Improve image delivery
Est savings of 321 KiB
LCP request discovery
Legacy JavaScript
Est savings of 13 KiB
Network dependency tree
Render blocking requests
Est savings of 30 ms
Max Potential First Input Delay
150 ms
Minify CSS
Est savings of 3 KiB
Reduce unused CSS
Est savings of 54 KiB
Reduce unused JavaScript
Est savings of 91 KiB
Avoid enormous network payloads
Total size was 6,945 KiB
Minimize main-thread work
2.7 s
Image elements do not have explicit `width` and `height`
Avoid multiple page redirects
Est savings of 230 ms
▸ 26 passed / informational
First Contentful Paint
0.8 s
Cumulative Layout Shift
0.021
Layout shift culprits
Optimize DOM size
Duplicated JavaScript
Font display
LCP breakdown
3rd parties
Optimize viewport for mobile
Time to Interactive
2.3 s
Minify JavaScript
JavaScript execution time
1.0 s
Avoid long main-thread tasks
8 long tasks found
Avoid non-composited animations
1 animated element found
Network Requests
Network Round Trip Times
10 ms
Server Backend Latencies
40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short
Root document took 10 ms
Avoid large layout shifts
1 layout shift found
SEO
Links do not have descriptive text
1 link 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
No issues found.
▸ 19 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
No browser errors logged to the console
Page has valid source maps
No issues in the `Issues` panel in Chrome Devtools
Accessibility
Background and foreground colors do not have a sufficient contrast ratio.
Elements with visible text labels do not have matching accessible names.
▸ 36 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
Document has a `<title>` element
ARIA IDs are unique
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 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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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