EarCOUTURE
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Mobile Friendliness 100/100
Content is not blocked for zoom/scale
Content is sized correctly for the viewport
Uses legible font sizes
Color Contrast is satisfactory
Performance 79/100
Speed Index
-
Speed Index0.00target < 4500 ms
Speed Index is a page load performance metric that shows you how quickly the contents of a page are visibly populated. The lower the score, the better. Source: Lighthouse - Learn more
Document complete
-
Time23seconds
-
Resources28requests
-
Bytes in2.9MB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time27.6seconds
-
Resources36requests
-
Bytes in3.1MB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- earcouture.jp
- www.googletagmanager.com
- content-autofill.googleapis.com
Bytes downloaded
- earcouture.jp
- www.googletagmanager.com
- content-autofill.googleapis.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time22996 ms
Page load is fast enough on 3G
First byte3500 ms
First Contentful Paint3268.483 ms
First meaningful paint3268.483 ms
Estimated Input Latency12 ms (target < 50 ms)
Uses persistent connections (keep alive)Score: 100%
First CPU Idle3268.48 ms
Time to Interactive3268.48 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 100%
Uses a CDN for all static assetsScore: 97%
Leverage browser caching
2 resources found
URL |
---|
https://www.google-analytics.com/analytics.js ( 2 hours ) |
https://earcouture.jp/asset/font/quiche_sans_light.woff2 ( 1 week ) |
... |
Minify CSS
Minify JavaScript
Avoids an excessive DOM size609 nodes
-
Total DOM Nodes609target < 1,500 nodes
-
DOM Depth21target < 32
-
Maximum Children53target < 60 nodes
Compressed Images
Uses Progressive JPEGsn/a
Properly Sized Images
Offscreen images
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
Improves server response time
Avoids landing page redirects
Usability 50/100 Industry: Retail Pure play
Autocomplete is used to suggest popular searches (but can be ignored)
Filtering is available and prominent on search results or category listing pages
The product details follow a set pattern making it easier to compare, e.g. bullet points with tech specs
Key and appropriate information is provided and easy to find on the product page
All product images are zoomable, without blur
Carousels are generally avoided (but they are acceptable if they are well implemented)
There is a choice to convert without creating an account, i.e. Guest checkout
The most appropriate keyboard for the input type is provided first
The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofill
All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time
PWA / Best Practices 100/100
Avoids Application Cache
Avoids WebSQL DB
Avoids requesting the geolocation permission on page load
robots.txt is valid
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Allows to paste into password input fields
Registers a Service Worker
Responds with a 200 when offline
Uses HTTPS
Redirects HTTP traffic to HTTPS
Uses HTTP/2 for its own resources
Uses passive listeners to improve scrolling performance
Avoid using document.write()
Manifest's short_name won't be truncated when displayed on homescreen
Configured for a custom splash screen
User can be prompted to Install the Web App
This report was built manually by Awwwards experts taking care personally of every detail using several Google and 3rd-party audit tools and services for metrics, web performance optimization and best practices for mobile design and development.
Loading time vary depending on network, device, server, site design, and implementation.
These are the environments used to create this report:
Webpagetest | Test Location | Dulles VA USA |
Browser | MotoG4 Chrome | |
Connection | Mobile 3G (1.6 Mbps / 768 Kbps 300ms RTT) | |
Number of Runs | 1 | |
User Agent | Default | |
Lighthouse | User agent | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 |
Device Emulation | Emulated Nexus 5X | |
Network Throttling | 150ms TCP RTT, 1,638.4 Kbps throughput (Simulated) | |
CPU Throttling | 4x slowdown (Simulated) | |
PageSpeed Insights | Environment | Mobile |