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://devbox.rabinovicionline.com/projects/ZEB/zgl-fedex-abm-campaign-assets-q2-25/index.html
75
Perf
58
SEO
73
BP
91
A11y
75
Performance
58
SEO
73
Best Practices
91
Accessibility (LH)
Run time: 23.0s
Performance
Largest Contentful Paint
3.6 s
Total Blocking Time
150 ms
Speed Index
1.5 s
Use efficient cache lifetimes
Est savings of 685 KiB
Improve image delivery
Est savings of 2,615 KiB
LCP request discovery
Legacy JavaScript
Est savings of 28 KiB
Network dependency tree
Render blocking requests
Est savings of 270 ms
Time to Interactive
3.6 s
Minify CSS
Est savings of 4 KiB
Minify JavaScript
Est savings of 4 KiB
Reduce unused CSS
Est savings of 209 KiB
Reduce unused JavaScript
Est savings of 381 KiB
Avoid enormous network payloads
Total size was 4,023 KiB
Image elements do not have explicit `width` and `height`
▸ 28 passed / informational
First Contentful Paint
0.9 s
Cumulative Layout Shift
0.025
Layout shift culprits
Document request latency
Optimize DOM size
Duplicated JavaScript
Font display
Forced reflow
LCP breakdown
3rd parties
Optimize viewport for mobile
Max Potential First Input Delay
100 ms
JavaScript execution time
0.6 s
Minimizes main-thread work
1.2 s
Avoid long main-thread tasks
5 long tasks found
Network Requests
Network Round Trip Times
40 ms
Server Backend Latencies
20 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short
Root document took 0 ms
Avoid large layout shifts
1 layout shift found
SEO
Page is blocked from indexing
Links do not have descriptive text
2 links found
▸ 8 passed / informational
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`
Structured data is valid
Best Practices
Uses third-party cookies
2 cookies found
Browser errors were logged to the console
Issues were logged in the `Issues` panel in Chrome Devtools
▸ 16 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
Page has valid source maps
Accessibility
`[aria-*]` attributes do not match their roles
Background and foreground colors do not have a sufficient contrast ratio.
▸ 35 passed / informational
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
`<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 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.