User Experience Performance Single Region Diagnostic Results

Webpage: https://coasiacm.com

Device: Desktop Computer

Region: United States West (Oregon)

Single Region Score

0
Poor Page Performance
A total of 13 improvements can achieve a better score
Heading elements are not in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order].

Render blocking requests

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining] can move these network requests out of the critical path.

First Contentful Paint

First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric].

Third parties

Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.

Missing source maps for large first-party JavaScript

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. [Learn more about source maps].

Links do not have descriptive text

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible].

Layout shift culprits

Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts], such as elements being added, removed, or their fonts changing as the page loads.

Document request latency

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Improve image delivery

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]

ARIA input fields do not have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. [Learn more about input field labels].

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric].

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. [Learn more about the viewport meta tag].

Links do not have a discernible name

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. [Learn how to make links accessible].

Show All