Mobile Friendliness 100/100
Configures the viewport
Content is sized correctly for the viewport
Size tap targets appropriately
Uses legible font sizes
Color Contrast is satisfactory
Performance 59/100
Speed Index
-
Speed Index11803target < 4000 ms
The Speed Index measures how quickly the page contents are visually populated / painted, and computes an overall score where lower numbers are better. It is expressed in milliseconds and dependent on size of the viewport (above-the-fold contents). Learn more
Document complete
-
Time10.8seconds
-
Resources109requests
-
Bytes in4.6MB
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
-
Time15.3seconds
-
Resources205requests
-
Bytes in41MB
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
- new.oberig.jewelry
- api.oberig.jewelry
Bytes downloaded
- api.oberig.jewelry
- new.oberig.jewelry
Assets by Mime-Type
Requests
- html
- js
- image
- font
- video
Bytes downloaded
- html
- js
- image
- font
- video
Speed
Load time 10792 ms
Page load is fast enough on 3G
First byte 2387 ms
First meaningful paint 5352 ms
Estimated Input Latency 57Â ms (target < 50 ms)
Uses persistent connections (keep alive) Score: 100%
First interactive (beta - experimental) 17770 ms
Consistently Interactive (beta - experimental) 22732 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli) Score: 100%
Uses a CDN for all static assets Score: 0%
Leverage browser caching 1
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size 992 nodes
-
Total DOM Nodes992target < 1,500 nodes
-
DOM Depth21target < 32
-
Maximum Children91target < 60 nodes
Compressed Images
Uses Progressive JPEGs n/a
Properly Sized Images Potential savings of 219Â KB (~1,300Â ms)
Offscreen images Potential savings of 659Â KB (~3,930Â ms)
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
Prioritizes visible content
Improves server response time
Avoids landing page redirects
Usability 88/100
Clicking logo always leads you to homepage.
Key CTAs are visible on the homepage.
No ending trailing paths.
Suports multi-device experiences. Not applicable
For category pages/search result with lots of products, make sure lazy-loading or pagination are used.
Possible to swipe to see more images or tap to enlarge them.
Streamlines forms information entry.
Forms error warnings.
Makes site search visible and user-friendly. Not applicable
Keeps your user in a single browser window.
Best Practices 100/100
Avoids Application Cache
Avoids WebSQL DB
Avoids requesting the geolocation permission on page load
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
Mobile Friendliness 100/100
Configures the viewport
Content is sized correctly for the viewport
Size tap targets appropriately
Uses legible font sizes
Color Contrast is satisfactory
Performance 67/100
Speed Index
-
Speed Index10091target < 4000 ms
The Speed Index measures how quickly the page contents are visually populated / painted, and computes an overall score where lower numbers are better. It is expressed in milliseconds and dependent on size of the viewport (above-the-fold contents). Learn more
Document complete
-
Time7.3seconds
-
Resources60requests
-
Bytes in3MB
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
-
Time10.8seconds
-
Resources140requests
-
Bytes in10.5MB
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
- new.oberig.jewelry
- api.oberig.jewelry
Bytes downloaded
- new.oberig.jewelry
- api.oberig.jewelry
Assets by Mime-Type
Requests
- html
- js
- image
- font
Bytes downloaded
- html
- js
- image
- font
Speed
Load time 7255 ms
Page load is fast enough on 3G
First byte 2397 ms
First meaningful paint 5271.5 ms
Estimated Input Latency 40Â ms (target < 50 ms)
Uses persistent connections (keep alive) Score: 100%
First interactive (beta - experimental) 12926.5 ms
Consistently Interactive (beta - experimental) 17014.5 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli) Score: 100%
Uses a CDN for all static assets Score: 0%
Leverage browser caching 1
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size 479 nodes
-
Total DOM Nodes479target < 1,500 nodes
-
DOM Depth20target < 32
-
Maximum Children85target < 60 nodes
Compressed Images
Uses Progressive JPEGs n/a
Properly Sized Images
Offscreen images Potential savings of 70Â KB (~410Â ms)
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
Prioritizes visible content
Improves server response time
Avoids landing page redirects
Usability 88/100
Clicking logo always leads you to homepage.
Key CTAs are visible on the homepage.
No ending trailing paths.
Suports multi-device experiences. Not applicable
For category pages/search result with lots of products, make sure lazy-loading or pagination are used.
Possible to swipe to see more images or tap to enlarge them.
Streamlines forms information entry.
Forms error warnings.
Makes site search visible and user-friendly. Not applicable
Keeps your user in a single browser window.
Best Practices 100/100
Avoids Application Cache
Avoids WebSQL DB
Avoids requesting the geolocation permission on page load
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
Mobile Friendliness 100/100
Configures the viewport
Content is sized correctly for the viewport
Size tap targets appropriately
Uses legible font sizes
Color Contrast is satisfactory
Performance 65/100
Speed Index
-
Speed Index15198target < 4000 ms
The Speed Index measures how quickly the page contents are visually populated / painted, and computes an overall score where lower numbers are better. It is expressed in milliseconds and dependent on size of the viewport (above-the-fold contents). Learn more
Document complete
-
Time9.4seconds
-
Resources55requests
-
Bytes in3MB
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
-
Time12.3seconds
-
Resources128requests
-
Bytes in9.3MB
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
- new.oberig.jewelry
- api.oberig.jewelry
Bytes downloaded
- new.oberig.jewelry
- api.oberig.jewelry
Assets by Mime-Type
Requests
- html
- js
- image
- font
Bytes downloaded
- html
- js
- image
- font
Speed
Load time 9384 ms
Page load is fast enough on 3G
First byte 2252 ms
First meaningful paint 5016 ms
Estimated Input Latency 44Â ms (target < 50 ms)
Uses persistent connections (keep alive) Score: 100%
First interactive (beta - experimental) 13933 ms
Consistently Interactive (beta - experimental) 18049 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli) Score: 100%
Uses a CDN for all static assets Score: 0%
Leverage browser caching 1
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size 486 nodes
-
Total DOM Nodes486target < 1,500 nodes
-
DOM Depth20target < 32
-
Maximum Children97target < 60 nodes
Compressed Images
Uses Progressive JPEGs n/a
Properly Sized Images Potential savings of 71Â KB (~410Â ms)
Offscreen images Potential savings of 96Â KB (~560Â ms)
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
Prioritizes visible content
Improves server response time
Avoids landing page redirects
Usability 88/100
Clicking logo always leads you to homepage.
Key CTAs are visible on the homepage.
No ending trailing paths.
Suports multi-device experiences. Not applicable
For category pages/search result with lots of products, make sure lazy-loading or pagination are used.
Possible to swipe to see more images or tap to enlarge them.
Streamlines forms information entry.
Forms error warnings.
Makes site search visible and user-friendly. Not applicable
Keeps your user in a single browser window.
Best Practices 100/100
Avoids Application Cache
Avoids WebSQL DB
Avoids requesting the geolocation permission on page load
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 using several Google, 3rd-party and Awwwards 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 (Linux; Android 6.0.1; Nexus 5 Build/MRA58N) AppleWebKit/537.36(KHTML, like Gecko) Chrome/61.0.3116.0 Mobile Safari/537.36 |
Device Emulation | Nexus 5X o MotoG | |
Network Throttling | 1.4Mbps down, 0.7Mbps up, 562.5ms RTT (PageSpeed uses Chrome on Moto G4 within a 3G network) | |
CPU Throttling | 4x slowdown | |
PageSpeed Insights Mobile | Environment | Default |
TestMySite | Environment | Default |