← All Reports
Lighthouse Report
Accessibility scores shown here are from Lighthouse's automated audit. For detailed axe-core violations, see the Accessibility + SEO report.
https://www.rab2b.com/built-on-hubspot?hs_preview=GcZIIalQ-211238729274
51
Perf
69
SEO
79
BP
100
A11y
51
Performance
69
SEO
79
Best Practices
100
Accessibility (LH)
Run time: 57.8s
Performance
First Contentful Paint
2.1 s
Largest Contentful Paint
4.1 s
Total Blocking Time
5,280 ms
Speed Index
5.1 s
Use efficient cache lifetimes
Est savings of 384 KiB
Font display
Est savings of 10 ms
Forced reflow
Improve image delivery
Est savings of 30 KiB
Network dependency tree
Render blocking requests
Est savings of 150 ms
Time to Interactive
10.4 s
Max Potential First Input Delay
770 ms
Eliminate render-blocking resources
Est savings of 150 ms
Properly size images
Est savings of 26 KiB
Reduce unused JavaScript
Est savings of 252 KiB
Avoid serving legacy JavaScript to modern browsers
Avoid enormous network payloads
Total size was 4,984 KiB
Serve static assets with an efficient cache policy
6 resources found
Avoid an excessive DOM size
1,094 elements
Reduce JavaScript execution time
7.4 s
Minimize main-thread work
17.1 s
Reduce the impact of third-party code
Third-party code blocked the main thread for 4,290 ms
Largest Contentful Paint element
4,070 ms
▸ 47 passed / informational
Cumulative Layout Shift
0.002
Layout shift culprits
Document request latency
Optimize DOM size
Duplicated JavaScript
LCP breakdown
LCP request discovery
Legacy JavaScript
Modern HTTP
3rd parties
Optimize viewport for mobile
Defer offscreen images
Minify CSS
Minify JavaScript
Reduce unused CSS
Efficiently encode images
Serve images in next-gen formats
Enable text compression
Preconnect to required origins
Initial server response time was short
Root document took 30 ms
Avoid multiple page redirects
Use HTTP/2
Use video formats for animated content
Remove duplicate modules in JavaScript bundles
Preload Largest Contentful Paint image
Avoid chaining critical requests
29 chains found
User Timing marks and measures
8 user timings
All text remains visible during webfont loads
Largest Contentful Paint image was not lazily loaded
Avoid large layout shifts
1 layout shift found
Uses passive listeners to improve scrolling performance
Avoids `document.write()`
Avoid long main-thread tasks
20 long tasks found
Avoid non-composited animations
2 animated elements found
Image elements have explicit `width` and `height`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times
20 ms
Server Backend Latencies
70 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
SEO
Page is blocked from indexing
▸ 10 passed / informational
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
Uses third-party cookies
4 cookies found
Issues were logged in the `Issues` panel in Chrome Devtools
▸ 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
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document uses legible font sizes
99.6% legible text
Page has the HTML doctype
Properly defines charset
Avoids deprecated APIs
No browser errors logged to the console
Page has valid source maps
Accessibility
Elements with visible text labels do not have matching accessible names.
▸ 42 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
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
Image elements do not have `[alt]` attributes that are redundant 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.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.