Webpage: http://captain-drink.co.jp
Device: Desktop Computer
Region: Australia (Sydney)
Single Region Score
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].
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].
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. [Learn more].
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work]
Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript].
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. [Learn more about third-party cookies].
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images].
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric]
Screen reader users rely on frame titles to describe the contents of frames. [Learn more about frame titles].
First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric].
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.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time].
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]
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].
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].
Optimized images load faster and consume less cellular data. [Learn how to efficiently encode images].
Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible].
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].
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more about text compression].
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. [Learn how to minimize third-party impact].
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].
A `` not only optimizes your app for mobile screen sizes, but also prevents [a 300 millisecond delay to user input]. [Learn more about using the viewport meta tag].
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content], where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. [Learn more about HTTPS].