Studio P2MV
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
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 64/100
Speed Index
-
Speed Index11266.65target < 4500 ms
Perceptual 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
-
Time84.1seconds
-
Resources54requests
-
Bytes in13.5MB
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
-
Time92.3seconds
-
Resources56requests
-
Bytes in13.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
- p2mv.studio
- www.google-analytics.com
Bytes downloaded
- p2mv.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- video
- other
Bytes downloaded
- html
- js
- css
- image
- font
- video
- other
Speed
Load time84137 ms
Page load is fast enough on 3G
First byte2204 ms
First Contentful Paint6367.174 ms
First meaningful paint6367.174 ms
Estimated Input Latency12 ms (target < 50 ms)
Uses persistent connections (keep alive)Score: 100%
First CPU Idle6367.17 ms
Time to Interactive6367.17 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 39%
Uses a CDN for all static assetsScore: 3%
Leverage browser caching
Leverage browser caching for the following cacheable resources:
URL |
---|
https://www.google-analytics.com/analytics.js (2 hours) |
... |
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size334 nodes
-
Total DOM Nodes334target < 1,500 nodes
-
DOM Depth13target < 32
-
Maximum Children89target < 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
Prioritizes visible content
Improves server response time
Avoids landing page redirects
Usability 63/100 Industry: Agency / Portfolio
Brand logo linked to homepage
No ending trailing paths
Active section is highlighted in navigation menus
Listing/overview pages with many items implements deferred loading techniques
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
The case listing page is not the only way to browse through all the cases
Carousels are generally avoided (but they are acceptable if they are well implemented)
Make it easy to contact you
The most appropriate keyboard for the input type is provided firstNot applicable
All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable
PWA / Best Practices 73/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
Mobile Friendliness 80/100
Configures the viewport
Content is sized correctly for the viewport
Size tap targets appropriately
Uses legible font sizes
Color Contrast is satisfactory
Failing Elements
Impact | Snippet | Target | Failure Summary |
---|---|---|---|
serious | <a data-v-6b441e2c="" href="/case/keus" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Keus</a> | a[href$="keus"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/sony-music-france" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Sony Music France</a> | a[href$="sony-music-france"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/new-jumo-concept" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">New Jumo Concept</a> | a[href$="new-jumo-concept"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/the-feebles" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">The Feebles</a> | a[href$="the-feebles"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/agence-titan" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Agence Titan</a> | a[href$="agence-titan"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/7h34" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">7h34</a> | :root | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/madame-porte-la-culotte" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Madame porte la culotte</a> | a[href$="madame-porte-la-culotte"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/fubiz-talks-2018" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Fubiz Talks 2018</a> | a[href$="fubiz-talks-2018"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
serious | <a data-v-6b441e2c="" href="/case/antigel" class="project-teaser inline-block no-underline leading-normal text-2xl md:text-44" style="visibility: inherit;">Antigel</a> | a[href$="antigel"] | Fix any of the following: Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 18.0pt, font weight: normal). Expected contrast ratio of 3:1 |
... |
Performance 65/100
Speed Index
-
Speed Index16942.50target < 4500 ms
Perceptual 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
-
Time64.5seconds
-
Resources57requests
-
Bytes in10.8MB
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
-
Time73.8seconds
-
Resources59requests
-
Bytes in10.8MB
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
- p2mv.studio
- www.google-analytics.com
Bytes downloaded
- p2mv.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- video
- other
Bytes downloaded
- html
- js
- css
- image
- font
- video
- other
Speed
Load time64536 ms
Page load is fast enough on 3G
First byte2037 ms
First Contentful Paint6275.09 ms
First meaningful paint6275.09 ms
Estimated Input Latency12 ms (target < 50 ms)
Uses persistent connections (keep alive)Score: 100%
First CPU Idle6275.09 ms
Time to Interactive6275.09 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 39%
Uses a CDN for all static assetsScore: 5%
Leverage browser caching
Leverage browser caching for the following cacheable resources:
URL |
---|
https://www.google-analytics.com/analytics.js (2 hours) |
... |
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size173 nodes
-
Total DOM Nodes173target < 1,500 nodes
-
DOM Depth9target < 32
-
Maximum Children91target < 60 nodes
Compressed Images
Uses Progressive JPEGsScore: 100 %
Properly Sized Images
Offscreen images
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 63/100 Industry: Agency / Portfolio
Brand logo linked to homepage
No ending trailing paths
Active section is highlighted in navigation menus
Listing/overview pages with many items implements deferred loading techniques
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
The case listing page is not the only way to browse through all the cases
Carousels are generally avoided (but they are acceptable if they are well implemented)
Make it easy to contact you
The most appropriate keyboard for the input type is provided firstNot applicable
All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable
PWA / Best Practices 73/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
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 Index9641.56target < 4500 ms
Perceptual 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
-
Time46.2seconds
-
Resources65requests
-
Bytes in7.5MB
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
-
Time55.1seconds
-
Resources67requests
-
Bytes in7.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
- p2mv.studio
- www.google-analytics.com
Bytes downloaded
- p2mv.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- video
- other
Bytes downloaded
- html
- js
- css
- image
- font
- video
- other
Speed
Load time46155 ms
Page load is fast enough on 3G
First byte2195 ms
First Contentful Paint5074.783 ms
First meaningful paint5074.783 ms
Estimated Input Latency12 ms (target < 50 ms)
Uses persistent connections (keep alive)Score: 100%
First CPU Idle5074.78 ms
Time to Interactive5074.78 ms
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 39%
Uses a CDN for all static assetsScore: 4%
Leverage browser caching
Leverage browser caching for the following cacheable resources:
URL |
---|
https://www.google-analytics.com/analytics.js (2 hours) |
... |
Minify CSS
Minify HTML
Minify JavaScript
Avoids an excessive DOM size418 nodes
-
Total DOM Nodes418target < 1,500 nodes
-
DOM Depth20target < 32
-
Maximum Children92target < 60 nodes
Compressed Images
Uses Progressive JPEGsScore: 100 %
Properly Sized ImagesPotential savings of 38 KB
Offscreen images
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 63/100 Industry: Agency / Portfolio
Brand logo linked to homepage
No ending trailing paths
Active section is highlighted in navigation menus
Listing/overview pages with many items implements deferred loading techniques
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
The case listing page is not the only way to browse through all the cases
Carousels are generally avoided (but they are acceptable if they are well implemented)
Make it easy to contact you
The most appropriate keyboard for the input type is provided firstNot applicable
All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable
PWA / Best Practices 73/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 |