Webpage: https://www.pewc.com.tw
Device: Desktop Computer
Region: Ireland (Dublin)
Single Region Score
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
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].
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. [Learn more about third-party cookies].
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]
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].
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more about text compression].
Image display dimensions should match natural aspect ratio. [Learn more about image aspect ratio].
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]
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.
Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS].
Optimized images load faster and consume less cellular data. [Learn how to efficiently encode images].
Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript].
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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].
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].
Screen readers require list items (`
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. [Learn more about roles and required children elements].
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].
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute].
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].
Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images].
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]
Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric].
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.
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]
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. [Learn how to defer third-parties with a facade].
Screen reader users rely on frame titles to describe the contents of frames. [Learn more about frame titles].
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
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.