Laqua.jp Site Title
ラクーア - LaQua
Laqua.jp Meta Description
東京・後楽園、東京ドームに併設されたスパ施設を中心とした水がテーマの総合アミューズメント施設「LaQua」の公式ページ。都会の真ん中で夜景を楽しみながらお湯を楽しみ、極上の癒しが手に入るスパ・ラクーアをはじめ、併設されたショッピングセンターでは有名ブランドのショッピングやレストランで食事が楽しめます。お得なプラン、セール、キャンペーンやイベントのご案内など情報が満載。
Laqua.jp Test Results
Laqua.jp Mobile Performance: 42/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
74,410 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 508 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Efficiently encode images
Potential savings of 3,051 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 27,510 ms
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.
Defer offscreen images
Potential savings of 1,044 KiB
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.
Avoid large layout shifts
6 layout shifts found
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
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Properly size images
Potential savings of 128 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused CSS
Potential savings of 96 KiB
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.
Reduce initial server response time
Root document took 1,910 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Serve images in next-gen formats
Potential savings of 6,820 KiB
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.
Serve static assets with an efficient cache policy
125 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 17,630 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Enable text compression
Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid an excessive DOM size
1,409 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Reduce JavaScript execution time
4.5 s
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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 51 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Minimize main-thread work
15.4 s
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
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,660 ms
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.
Time to Interactive
29.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
29.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Laqua.jp Mobile SEO: 91/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
Laqua.jp Mobile Best Practices: 62/100
Quick overview:
General
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
Trust and Safety
Does not use HTTPS
1 insecure request found
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.
Laqua.jp Mobile Accessibility: 82/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
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.
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Contrast
These are opportunities to improve the legibility of your content.
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.
Similar sites
Similar tests
www.laqua.com
www.laqua.net
www.laqua.org
www.laqua.info
www.laqua.biz
www.laqua.us
www.laqua.mobi
www.aqua.jp
www.laqua.jp
www.paqua.jp
www.lpaqua.jp
www.plaqua.jp
www.oaqua.jp
www.loaqua.jp
www.olaqua.jp
www.kaqua.jp
www.lkaqua.jp
www.klaqua.jp
www.lqua.jp
www.lqqua.jp
www.laqqua.jp
www.lqaqua.jp
www.lwqua.jp
www.lawqua.jp
www.lwaqua.jp
www.lsqua.jp
www.lasqua.jp
www.lsaqua.jp
www.lzqua.jp
www.lazqua.jp
www.lzaqua.jp
www.laua.jp
www.laaua.jp
www.laqaua.jp
www.laaqua.jp
www.lawua.jp
www.laqwua.jp
www.laqa.jp
www.laqya.jp
www.laquya.jp
www.laqyua.jp
www.laqha.jp
www.laquha.jp
www.laqhua.jp
www.laqja.jp
www.laquja.jp
www.laqjua.jp
www.laqia.jp
www.laquia.jp
www.laqiua.jp
www.laqu.jp
www.laquq.jp
www.laquaq.jp
www.laquqa.jp
www.laquw.jp
www.laquaw.jp
www.laquwa.jp
www.laqus.jp
www.laquas.jp
www.laqusa.jp
www.laquz.jp
www.laquaz.jp
www.laquza.jp
www.laqua.net
www.laqua.org
www.laqua.info
www.laqua.biz
www.laqua.us
www.laqua.mobi
www.aqua.jp
www.laqua.jp
www.paqua.jp
www.lpaqua.jp
www.plaqua.jp
www.oaqua.jp
www.loaqua.jp
www.olaqua.jp
www.kaqua.jp
www.lkaqua.jp
www.klaqua.jp
www.lqua.jp
www.lqqua.jp
www.laqqua.jp
www.lqaqua.jp
www.lwqua.jp
www.lawqua.jp
www.lwaqua.jp
www.lsqua.jp
www.lasqua.jp
www.lsaqua.jp
www.lzqua.jp
www.lazqua.jp
www.lzaqua.jp
www.laua.jp
www.laaua.jp
www.laqaua.jp
www.laaqua.jp
www.lawua.jp
www.laqwua.jp
www.laqa.jp
www.laqya.jp
www.laquya.jp
www.laqyua.jp
www.laqha.jp
www.laquha.jp
www.laqhua.jp
www.laqja.jp
www.laquja.jp
www.laqjua.jp
www.laqia.jp
www.laquia.jp
www.laqiua.jp
www.laqu.jp
www.laquq.jp
www.laquaq.jp
www.laquqa.jp
www.laquw.jp
www.laquaw.jp
www.laquwa.jp
www.laqus.jp
www.laquas.jp
www.laqusa.jp
www.laquz.jp
www.laquaz.jp
www.laquza.jp