User Experience Performance Single Region Diagnostic Results

Webpage: https://prosper.com.vn

Device: Desktop Computer

Region: Germany (Frankfurt)

Single Region Score

43
Poor Page Performance
A total of 30 improvements can achieve a better score
Third parties

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

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript].

Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute].

`[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].

Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS].

Avoid large layout shifts

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing]. [Learn how to improve CLS]

`[role]`s are not contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. [Learn more about ARIA roles and required parent element].

List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

Screen readers require list items (`

  • `) to be contained within a parent `
    • Properly size images

    Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images].

    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].

    `<html>` element does not have a valid value for its `[lang]` attribute.

    Specifying a valid [BCP 47 language] helps screen readers announce text properly. [Learn how to use the `lang` attribute].

    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].

    Document does not have a meta description

    Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description].

    Eliminate render-blocking resources

    Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn how to eliminate render-blocking resources].

    LCP request discovery

    Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]

    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.

    Efficiently encode images

    Optimized images load faster and consume less cellular data. [Learn how to efficiently encode images].

    `<frame>` or `<iframe>` elements do not have a title

    Screen reader users rely on frame titles to describe the contents of frames. [Learn more about frame titles].

    Largest Contentful Paint element

    This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]

    Document doesn't have a `<title>` element

    The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. [Learn more about document titles].

    Browser errors were logged to the console

    Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit]

    Background and foreground colors do not have a sufficient contrast ratio.

    Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].

    Defer offscreen images

    Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn how to defer offscreen images].

    Serve images in next-gen formats

    Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more about modern image formats].

    Minify CSS

    Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS].

    Reduce unused JavaScript

    Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].

    Links are not crawlable

    Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable]

    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.

    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].

    Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.

    Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. [Learn more about roles and required children elements].

    Show All