PageSpeed Insights Report

Priority Issues

Structural Issues — fix in code (3)▶

✗

Reduce unused CSS

Est savings of 54 KiB

✗

Reduce unused JavaScript

Est savings of 733 KiB

✗

Avoid enormous network payloads

Total size was 3,373 KiB

Environment-Sensitive Metrics — note trends, don't chase numbers (16)▶

⚠

First Contentful Paint

1.0 s~ env-sensitive

⚠

Total Blocking Time

320 ms~ env-sensitive

⚠

Cumulative Layout Shift

0.317~ env-sensitive

⚠

Speed Index

1.7 s~ env-sensitive

⚠

Use efficient cache lifetimes

Est savings of 435 KiB~ env-sensitive

⚠

Layout shift culprits

~ env-sensitive

⚠

Forced reflow

~ env-sensitive

⚠

Improve image delivery

Est savings of 104 KiB~ env-sensitive

⚠

Legacy JavaScript

Est savings of 13 KiB~ env-sensitive

⚠

Network dependency tree

~ env-sensitive

⚠

Render-blocking requests

Est savings of 110 ms~ env-sensitive

⚠

Time to Interactive

4.2 s~ env-sensitive

⚠

Max Potential First Input Delay

140 ms~ env-sensitive

⚠

Reduce JavaScript execution time

2.0 s~ env-sensitive

⚠

Minimize main-thread work

3.3 s~ env-sensitive

⚠

Avoid large layout shifts

1 layout shift found~ env-sensitive

Scores

Performance

SEO

Best Practices

100

Accessibility (LH)

Run time: 53.8s

Performance

⚠

First Contentful Paint

1.0 s~ env-sensitive

⚠

Total Blocking Time

320 ms~ env-sensitive

✗

Cumulative Layout Shift

0.317~ env-sensitive

⚠

Speed Index

1.7 s~ env-sensitive

✗

Use efficient cache lifetimes

Est savings of 435 KiB~ env-sensitive

✗

Layout shift culprits

~ env-sensitive

✗

Forced reflow

~ env-sensitive

⚠

Improve image delivery

Est savings of 104 KiB~ env-sensitive

⚠

Legacy JavaScript

Est savings of 13 KiB~ env-sensitive

✗

Network dependency tree

~ env-sensitive

✗

Render-blocking requests

Est savings of 110 ms~ env-sensitive

⚠

Time to Interactive

4.2 s~ env-sensitive

⚠

Max Potential First Input Delay

140 ms~ env-sensitive

✗

Reduce unused CSS

Est savings of 54 KiB

⚠

Reduce unused JavaScript

Est savings of 733 KiB

⚠

Avoid enormous network payloads

Total size was 3,373 KiB

✗

Reduce JavaScript execution time

2.0 s~ env-sensitive

✗

Minimize main-thread work

3.3 s~ env-sensitive

✗

Avoid large layout shifts

1 layout shift found~ env-sensitive

▸ 25 passed / informational

✓

Largest Contentful Paint

1.1 s~ env-sensitive

✓

Document request latency

~ env-sensitive

ℹ

Optimize DOM size

~ env-sensitive

✓

Duplicated JavaScript

~ env-sensitive

✓

Font display

~ env-sensitive

ℹ

LCP breakdown

~ env-sensitive

ℹ

3rd parties

~ env-sensitive

✓

Optimize viewport for mobile

~ env-sensitive

✓

Minify CSS

✓

Minify JavaScript

ℹ

Avoid long main-thread tasks

14 long tasks found~ env-sensitive

ℹ

Avoid non-composited animations

2 animated elements found~ env-sensitive

✓

Image elements have explicit `width` and `height`

~ env-sensitive

ℹ

Network Requests

~ env-sensitive

ℹ

Network Round Trip Times

30 ms~ env-sensitive

ℹ

Server Backend Latencies

40 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

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

✗

Uses deprecated APIs

1 warning found

✗

Browser errors were logged to the console

✗

Missing source maps for large first-party JavaScript

▸ 17 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 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.