Reports › RAB2B-241 › rab2b-com-2026-07-24T15-41-48 › PageSpeed Insights
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://www.rab2b.com/what-we-do/ai/geo
91
Perf
100
SEO
96
BP
100
A11y
 ▼
Priority Issues
Structural Issues — fix in code (3)▶
✗
Reduce unused CSS
Est savings of 53 KiB
✗
Reduce unused JavaScript
Est savings of 644 KiB
✗
Avoid enormous network payloads
Total size was 3,925 KiB
Environment-Sensitive Metrics — note trends, don't chase numbers (10)▶
⚠
Speed Index
2.3 s~ env-sensitive
⚠
Use efficient cache lifetimes
Est savings of 475 KiB~ env-sensitive
⚠
Forced reflow
~ env-sensitive
⚠
Improve image delivery
Est savings of 702 KiB~ env-sensitive
⚠
Legacy JavaScript
Est savings of 13 KiB~ env-sensitive
⚠
Network dependency tree
~ env-sensitive
⚠
Render-blocking requests
~ env-sensitive
⚠
Time to Interactive
3.2 s~ env-sensitive
⚠
Reduce JavaScript execution time
1.4 s~ env-sensitive
⚠
Minimize main-thread work
2.7 s~ env-sensitive
Scores
91
Performance
100
SEO
96
Best Practices
100
Accessibility (LH)
Run time: 20.9s
Performance
✗
Speed Index
2.3 s~ env-sensitive
✗
Use efficient cache lifetimes
Est savings of 475 KiB~ env-sensitive
✗
Forced reflow
~ env-sensitive
⚠
Improve image delivery
Est savings of 702 KiB~ env-sensitive
⚠
Legacy JavaScript
Est savings of 13 KiB~ env-sensitive
✗
Network dependency tree
~ env-sensitive
⚠
Render-blocking requests
~ env-sensitive
⚠
Time to Interactive
3.2 s~ env-sensitive
✗
Reduce unused CSS
Est savings of 53 KiB
✗
Reduce unused JavaScript
Est savings of 644 KiB
⚠
Avoid enormous network payloads
Total size was 3,925 KiB
✗
Reduce JavaScript execution time
1.4 s~ env-sensitive
✗
Minimize main-thread work
2.7 s~ env-sensitive
▸ 32 passed / informational
✓
First Contentful Paint
0.8 s~ env-sensitive
✓
Largest Contentful Paint
1.0 s~ env-sensitive
✓
Total Blocking Time
120 ms~ env-sensitive
✓
Cumulative Layout Shift
0.057~ 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
✓
LCP request discovery
~ env-sensitive
ℹ
3rd parties
~ env-sensitive
✓
Optimize viewport for mobile
~ env-sensitive
✓
Max Potential First Input Delay
100 ms~ env-sensitive
✓
Minify CSS
✓
Minify JavaScript
ℹ
Avoid long main-thread tasks
9 long tasks found~ env-sensitive
ℹ
Avoid non-composited animations
1 animated element found~ env-sensitive
✓
Image elements have explicit `width` and `height`
~ env-sensitive
ℹ
Network Requests
~ env-sensitive
ℹ
Network Round Trip Times
40 ms~ env-sensitive
ℹ
Server Backend Latencies
20 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
No issues found.
▸ 11 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
✓
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
✗
Missing source maps for large first-party JavaScript
▸ 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
ℹ
Baseline Features
ℹ
Detected JavaScript libraries
✓
Avoids deprecated APIs
✓
Avoids third-party cookies
✓
No issues in the `Issues` panel in Chrome Devtools
Accessibility
No issues found.
▸ 42 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
ℹ
ARIA IDs are unique
✓
`<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
✓
Input buttons have discernible text.
✓
Form elements have associated labels
✓
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.
Generated 7/24/2026, 3:42:15 PM · Jira RAB2B-241 · Run by [email protected]