Mobile Excellence / ZEST STORE
Oct 3, 2019, 4:57 PM

ZEST STORE

By Studio DOT (France) Paul Aballea
  • 0
    Friendliness
  • 0
    Performance
  • 0
    Usability
  • 0
    PWA
  • 0
    Total
Find out more about the Evaluation
ZEST STORE
Visit Site

Mobile Friendliness 80/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

URL
The tap target <input id="submited" type="submit"> is close to 1 other tap targets.
The tap target <a href="https://www.fa…m/zesttoulouse"></a> and 1 others are close to other tap targets.
The tap target <button class="popUp popmake-…ap pum-trigger"></button> is close to 1 other tap targets.
The tap target <a id="cn-accept-cookie" href="#" class="cn-set-cookie…default button">Ok</a> is close to 1 other tap targets final.
The tap target <a href="https://www.go…icies/privacy/">Privacy</a> is close to 1 other tap targets final.
...

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Performance 59/100

Speed Index

  • Speed Index
    4440.12
    target < 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

  • Time
    31.7
    seconds
  • Resources
    100
    requests
  • Bytes in
    2.7
    MB

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

  • Time
    50.9
    seconds
  • Resources
    116
    requests
  • Bytes in
    3.6
    MB

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

  • zestore.fr

  • scontent.cdninstagram.com

  • www.google.com

  • www.gstatic.com

  • chimpstatic.com

  • ajax.cloudflare.com

  • api.instagram.com

  • www.google-analytics.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

Bytes downloaded

  • zestore.fr

  • www.gstatic.com

  • scontent.cdninstagram.com

  • www.google.com

  • ajax.googleapis.com

  • ajax.cloudflare.com

  • api.instagram.com

  • chimpstatic.com

  • fonts.googleapis.com

  • www.google-analytics.com

  • stats.g.doubleclick.net

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • other

Speed

Load time31659 ms

Also known as the document complete time, it’s the time from the initial request until the browser load event. It can vary based on server location, device, browser, and third-party apps. Source: WebPagetest - Learn more

Page load is fast enough on 3G

A fast page load over a 3G network ensures a good mobile user experience. Source: Lighthouse - Learn more

First byte6819 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint2160.517 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint2160.517 ms

First meaningful paint measures when the primary content of a page is visible. It's essentially the paint after which the biggest above-the-fold layout change has happened, and web fonts have loaded. Source: Lighthouse - Learn more

Estimated Input Latency12 ms (target < 50 ms)

The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score (< 50ms), users may perceive your app as laggy. Source: Lighthouse - Learn more

Uses persistent connections (keep alive)Score: 100%

Closing connections are a missed opportunity for performance enhancement: additional round-trips between the user and the server to initiate a connection is redundant and time-consuming. Keep-Alive measures the effectiveness of connection reuse. The purpose of this grade is to evaluate the extent to which requests are inefficiently reopening connections. Source: WebPagetest - Learn more

First CPU Idle2160.52 ms

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Source: Lighthouse - Learn more

Time to Interactive2160.52 ms

Interactive marks the time at which the page is fully interactive. Source: Lighthouse - Learn more

Page weight

Uses compression (gzip, zopfli, deflate, brotli)Score: 100%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more

Uses a CDN for all static assetsScore: 100%

Each request for a piece of content to the web server has to travel from the user's browser all the way to the server and back. A content delivery network (CDN) is a system for distributing resources to servers geographically closer to users. The main benefit of this is that the round-trip time is faster. The passing grade for using a CDN effectively is to have at least 80% of static resources served from a CDN. Source: WebPagetest - Learn more

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Source: PageSpeed Insights - Learn more

Leverage browser caching for the following cacheable resources:

URL
https://www.google.com/recaptcha/api.js?render=6LfGlbAUAAAAAG0OPi3C4SMSk_zuQWD8B90VVWmW (5 minutes)
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=Zy-zVXWdnDW6AUZkKlojAKGe (5 minutes)
https://chimpstatic.com/mcjs-connected/js/users/a406809aa8c614fd34a591d99/a56ef9fdad8ff754cd92d48b0.js?ver=2.2.4 (29.2 minutes)
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days)
...

Minify CSS

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify CSS for the following resources to reduce their size by 1.3KiB (17% reduction).

URL
Minifying https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3 could save 1.3KiB (17% reduction) after compression.
...

Minify HTML

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript for the following resources to reduce their size by 318B (13% reduction).

URL
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/themes/twentyseventeen/assets/js/jquery.scrollTo-2.1.2.js could save 204B (13% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/js/js-cookie/js.cookie.min-2.1.4.js could save 114B (12% reduction) after compression.
...

Avoids an excessive DOM size1081 nodes

Number of elements in the document. Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Source: Lighthouse - Learn more
  • Total DOM Nodes
    1,081
    target < 1,500 nodes
  • DOM Depth
    13
    target < 32
  • Maximum Children
    88
    target < 60 nodes

Compressed Images

The image compression check just looks at photo images and makes sure the quality isn't set too high. Images can usually be compressed pretty substantially without any noticeable reduction in visual quality. Source: Lighthouse - Learn more

Uses Progressive JPEGsScore: 96 %

A progressive JPEG is image created using the JPEG suite of compression algorithms that will 'fade in' in successive waves of lines until the entire image has completely arrived. They show the entire image right away, looking slightly pixelated until the image data is fully loaded. Source: WebPagetest - Learn more

Properly Sized ImagesPotential savings of 25 KB

Serve images that are appropriately-sized to save cellular data and improve load time. Source: Lighthouse - Learn more

Offscreen images

Consider lazy-loading offscreen images to improve page load speed and time to interactive. Source: Lighthouse - Learn more

First impression

Eliminates render-blocking JavaScript and CSS in above-the-fold content

This rule triggers when detecting that your HTML references a blocking external resource / file in the above-the-fold portion of your page. Source: PageSpeed Insights - Learn more about JS - Learn more about CSS

Your page has 3 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

URL
https://zestore.fr/wp-content/cache/busting/1/wp-includes/js/jquery/jquery-1.12.4-wp.js
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
https://www.google.com/recaptcha/api.js?render=6LfGlbAUAAAAAG0OPi3C4SMSk_zuQWD8B90VVWmW
https://zestore.fr/wp-content/cache/min/1/70aa782471ad9400b8f6bf3ca385fd76.css
https://fonts.googleapis.com/css?family=Montserrat:100
https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/css/woocommerce-smallscreen-3.7.0.css
https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3
https://zestore.fr/wp-content/themes/twentyseventeen-child/assets/css/select2/select2.min.css
https://zestore.fr/wp-content/themes/twentyseventeen-child/style.css
...

Prioritizes visible content

This rule triggers when detecting that additional network round trips are required to render the above-the-fold content of the page. Source: PageSpeed Insights - Learn more

Improves server response time

This rule triggers when detecting that your server response time is above 200 ms. Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. Source: PageSpeed Insights - Learn more

Avoids landing page redirects

Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single round trip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance. Source: PageSpeed Insights - Learn more

Usability 94/100 Industry: Retail Omnichannel

Autocomplete is used to suggest popular searches (but can be ignored)Not applicable

Fails if no autocomplete or if the user is not allowed to ignore the autocomplete.

Filtering is available and prominent on search results or category listing pages

Fails if filtering is appropriate but not provided or if sorting is prioritized over filtering in the visual hierarchy.

The product details follow a set pattern making it easier to compare, e.g. bullet points with tech specs

Fails if different product description information formatting from one page to another.

It is possible to check in-store product availability

Fails if in-store product availability is not provided.

All product images are zoomable, without blur

Fails if product images are blurry at full zoom.

Carousels are generally avoided (but they are acceptable if they are well implemented)

Fails if any of the following are seen: carousels auto-rotate, text is not legible, swipe is not supported, next images do not load within 1 second of swipe.

There is a choice to convert without creating an account, i.e. Guest checkout

Fails if no guest checkout.

The most appropriate keyboard for the input type is provided first

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofill

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more

Mobile Friendliness 60/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

URL
The tap target <a href="https://zestor…tions-legales/">En savoir plus…ue de cookies.</a> and 1 others are close to other tap targets final.
The tap target <a id="cn-accept-cookie" href="#" class="cn-set-cookie…default button">Ok</a> is close to 2 other tap targets final.
...

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Failing Elements

ImpactSnippetTargetFailure Summary
serious<button type="submit" class="single_add_to_cart_button button alt disabled wc-variation-selection-needed">Ajouter au panier</button>.single_add_to_cart_buttonFix any of the following: Element has insufficient color contrast of 1.6 (foreground color: #c9c9a8, background color: #fcfcd3, font size: 9.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 51/100

Speed Index

  • Speed Index
    5184.11
    target < 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

  • Time
    15.1
    seconds
  • Resources
    87
    requests
  • Bytes in
    1.4
    MB

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

  • Time
    18.3
    seconds
  • Resources
    88
    requests
  • Bytes in
    1.5
    MB

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

  • zestore.fr

  • chimpstatic.com

  • ajax.cloudflare.com

  • www.google-analytics.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

Bytes downloaded

  • zestore.fr

  • ajax.googleapis.com

  • ajax.cloudflare.com

  • chimpstatic.com

  • fonts.googleapis.com

  • www.google-analytics.com

  • stats.g.doubleclick.net

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • other

Speed

Load time15111 ms

Also known as the document complete time, it’s the time from the initial request until the browser load event. It can vary based on server location, device, browser, and third-party apps. Source: WebPagetest - Learn more

Page load is fast enough on 3G

A fast page load over a 3G network ensures a good mobile user experience. Source: Lighthouse - Learn more

First byte5063 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint2166.057 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint2781.945 ms

First meaningful paint measures when the primary content of a page is visible. It's essentially the paint after which the biggest above-the-fold layout change has happened, and web fonts have loaded. Source: Lighthouse - Learn more

Estimated Input Latency12 ms (target < 50 ms)

The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score (< 50ms), users may perceive your app as laggy. Source: Lighthouse - Learn more

Uses persistent connections (keep alive)Score: 100%

Closing connections are a missed opportunity for performance enhancement: additional round-trips between the user and the server to initiate a connection is redundant and time-consuming. Keep-Alive measures the effectiveness of connection reuse. The purpose of this grade is to evaluate the extent to which requests are inefficiently reopening connections. Source: WebPagetest - Learn more

First CPU Idle2781.95 ms

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Source: Lighthouse - Learn more

Time to Interactive2781.95 ms

Interactive marks the time at which the page is fully interactive. Source: Lighthouse - Learn more

Page weight

Uses compression (gzip, zopfli, deflate, brotli)Score: 100%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more

Uses a CDN for all static assetsScore: 100%

Each request for a piece of content to the web server has to travel from the user's browser all the way to the server and back. A content delivery network (CDN) is a system for distributing resources to servers geographically closer to users. The main benefit of this is that the round-trip time is faster. The passing grade for using a CDN effectively is to have at least 80% of static resources served from a CDN. Source: WebPagetest - Learn more

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Source: PageSpeed Insights - Learn more

Leverage browser caching for the following cacheable resources:

URL
https://chimpstatic.com/mcjs-connected/js/users/a406809aa8c614fd34a591d99/a56ef9fdad8ff754cd92d48b0.js?ver=2.2.4 (30 minutes)
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days)
...

Minify CSS

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify CSS for the following resources to reduce their size by 1.3KiB (17% reduction).

URL
Minifying https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3 could save 1.3KiB (17% reduction) after compression.
...

Minify HTML

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript for the following resources to reduce their size by 901B (27% reduction).

URL
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/themes/twentyseventeen-child/assets/js/checkout-1.0.0.js could save 445B (95% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/themes/twentyseventeen/assets/js/jquery.scrollTo-2.1.2.js could save 204B (13% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/themes/twentyseventeen/assets/js/skip-link-focus-fix-1.0.js could save 138B (34% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/js/js-cookie/js.cookie.min-2.1.4.js could save 114B (12% reduction) after compression.
...

Avoids an excessive DOM size1705 nodes

Number of elements in the document. Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Source: Lighthouse - Learn more
  • Total DOM Nodes
    1,705
    target < 1,500 nodes
  • DOM Depth
    18
    target < 32
  • Maximum Children
    93
    target < 60 nodes

Compressed ImagesPotential savings of 22 KB

The image compression check just looks at photo images and makes sure the quality isn't set too high. Images can usually be compressed pretty substantially without any noticeable reduction in visual quality. Source: Lighthouse - Learn more

ThumbnailsURLOriginalPotential Savings
https://zestore.fr/wp-content/uploads/2019/07/Zest-Eternal-Love-Dos-T-Shirt-Noir.jpg132 KB22 KB (16%)
...

Uses Progressive JPEGsScore: 9 %

A progressive JPEG is image created using the JPEG suite of compression algorithms that will 'fade in' in successive waves of lines until the entire image has completely arrived. They show the entire image right away, looking slightly pixelated until the image data is fully loaded. Source: WebPagetest - Learn more

Properly Sized ImagesPotential savings of 35 KB

Serve images that are appropriately-sized to save cellular data and improve load time. Source: Lighthouse - Learn more

Offscreen images

Consider lazy-loading offscreen images to improve page load speed and time to interactive. Source: Lighthouse - Learn more

First impression

Eliminates render-blocking JavaScript and CSS in above-the-fold content

This rule triggers when detecting that your HTML references a blocking external resource / file in the above-the-fold portion of your page. Source: PageSpeed Insights - Learn more about JS - Learn more about CSS

Your page has 2 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

URL
https://zestore.fr/wp-content/cache/busting/1/wp-includes/js/jquery/jquery-1.12.4-wp.js
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
https://zestore.fr/wp-content/cache/min/1/70aa782471ad9400b8f6bf3ca385fd76.css
https://fonts.googleapis.com/css?family=Montserrat:100
https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/css/woocommerce-smallscreen-3.7.0.css
https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3
https://zestore.fr/wp-content/themes/twentyseventeen-child/assets/css/select2/select2.min.css
https://zestore.fr/wp-content/themes/twentyseventeen-child/style.css
...

Prioritizes visible content

This rule triggers when detecting that additional network round trips are required to render the above-the-fold content of the page. Source: PageSpeed Insights - Learn more

Improves server response time

This rule triggers when detecting that your server response time is above 200 ms. Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. Source: PageSpeed Insights - Learn more

Avoids landing page redirects

Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single round trip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance. Source: PageSpeed Insights - Learn more

Usability 94/100 Industry: Retail Omnichannel

Autocomplete is used to suggest popular searches (but can be ignored)Not applicable

Fails if no autocomplete or if the user is not allowed to ignore the autocomplete.

Filtering is available and prominent on search results or category listing pages

Fails if filtering is appropriate but not provided or if sorting is prioritized over filtering in the visual hierarchy.

The product details follow a set pattern making it easier to compare, e.g. bullet points with tech specs

Fails if different product description information formatting from one page to another.

It is possible to check in-store product availability

Fails if in-store product availability is not provided.

All product images are zoomable, without blur

Fails if product images are blurry at full zoom.

Carousels are generally avoided (but they are acceptable if they are well implemented)

Fails if any of the following are seen: carousels auto-rotate, text is not legible, swipe is not supported, next images do not load within 1 second of swipe.

There is a choice to convert without creating an account, i.e. Guest checkout

Fails if no guest checkout.

The most appropriate keyboard for the input type is provided first

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofill

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more

Mobile Friendliness 60/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

URL
The tap target <a href="https://zestor…tions-legales/">En savoir plus…ue de cookies.</a> is close to 1 other tap targets final.
...

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Failing Elements

ImpactSnippetTargetFailure Summary
serious<span data-progress="0"> 0/100</span>span[data-progress="\30 "]Fix any of the following: Element has insufficient color contrast of 2.92 (foreground color: #979797, background color: #ffffff, font size: 4.5pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 47/100

Speed Index

  • Speed Index
    6500.84
    target < 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

  • Time
    15.7
    seconds
  • Resources
    84
    requests
  • Bytes in
    957
    KB

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

  • Time
    18.8
    seconds
  • Resources
    92
    requests
  • Bytes in
    1.1
    MB

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

  • zestore.fr

  • chimpstatic.com

  • cdnjs.cloudflare.com

  • ajax.cloudflare.com

  • www.google-analytics.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

Bytes downloaded

  • zestore.fr

  • ajax.googleapis.com

  • ajax.cloudflare.com

  • chimpstatic.com

  • cdnjs.cloudflare.com

  • fonts.googleapis.com

  • www.google-analytics.com

  • stats.g.doubleclick.net

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • other

Speed

Load time15716 ms

Also known as the document complete time, it’s the time from the initial request until the browser load event. It can vary based on server location, device, browser, and third-party apps. Source: WebPagetest - Learn more

Page load is fast enough on 3G

A fast page load over a 3G network ensures a good mobile user experience. Source: Lighthouse - Learn more

First byte5163 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint4468.585 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint4468.585 ms

First meaningful paint measures when the primary content of a page is visible. It's essentially the paint after which the biggest above-the-fold layout change has happened, and web fonts have loaded. Source: Lighthouse - Learn more

Estimated Input Latency12 ms (target < 50 ms)

The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score (< 50ms), users may perceive your app as laggy. Source: Lighthouse - Learn more

Uses persistent connections (keep alive)Score: 100%

Closing connections are a missed opportunity for performance enhancement: additional round-trips between the user and the server to initiate a connection is redundant and time-consuming. Keep-Alive measures the effectiveness of connection reuse. The purpose of this grade is to evaluate the extent to which requests are inefficiently reopening connections. Source: WebPagetest - Learn more

First CPU Idle4468.59 ms

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Source: Lighthouse - Learn more

Time to Interactive4468.59 ms

Interactive marks the time at which the page is fully interactive. Source: Lighthouse - Learn more

Page weight

Uses compression (gzip, zopfli, deflate, brotli)Score: 100%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more

Uses a CDN for all static assetsScore: 100%

Each request for a piece of content to the web server has to travel from the user's browser all the way to the server and back. A content delivery network (CDN) is a system for distributing resources to servers geographically closer to users. The main benefit of this is that the round-trip time is faster. The passing grade for using a CDN effectively is to have at least 80% of static resources served from a CDN. Source: WebPagetest - Learn more

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Source: PageSpeed Insights - Learn more

Leverage browser caching for the following cacheable resources:

URL
https://chimpstatic.com/mcjs-connected/js/users/a406809aa8c614fd34a591d99/a56ef9fdad8ff754cd92d48b0.js?ver=2.2.4 (29.8 minutes)
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days)
...

Minify CSS

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify CSS for the following resources to reduce their size by 1.3KiB (17% reduction).

URL
Minifying https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3 could save 1.3KiB (17% reduction) after compression.
...

Minify HTML

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript

Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Source: PageSpeed Insights - Learn more

Minify JavaScript for the following resources to reduce their size by 7.7KiB (24% reduction).

URL
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce-ajax-filters/js/widget.min-2.3.1.1.js could save 3.7KiB (21% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce-ajax-filters/js/styler/formstyler-2.3.1.1.js could save 2.8KiB (38% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce-load-more-products/js/load_products-3.1.4.2.js could save 637B (20% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/themes/twentyseventeen/assets/js/jquery.scrollTo-2.1.2.js could save 204B (13% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce-ajax-filters/js/jquery.ui.touch-punch.min-2.3.1.1.js could save 127B (22% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-includes/js/jquery/ui/mouse.min-1.11.4.js could save 115B (12% reduction) after compression.
Minifying https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/js/js-cookie/js.cookie.min-2.1.4.js could save 114B (12% reduction) after compression.
...

Avoids an excessive DOM size2025 nodes

Number of elements in the document. Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Source: Lighthouse - Learn more
  • Total DOM Nodes
    2,025
    target < 1,500 nodes
  • DOM Depth
    14
    target < 32
  • Maximum Children
    90
    target < 60 nodes

Compressed Images

The image compression check just looks at photo images and makes sure the quality isn't set too high. Images can usually be compressed pretty substantially without any noticeable reduction in visual quality. Source: Lighthouse - Learn more

Uses Progressive JPEGsScore: 45 %

A progressive JPEG is image created using the JPEG suite of compression algorithms that will 'fade in' in successive waves of lines until the entire image has completely arrived. They show the entire image right away, looking slightly pixelated until the image data is fully loaded. Source: WebPagetest - Learn more

Properly Sized ImagesPotential savings of 18 KB

Serve images that are appropriately-sized to save cellular data and improve load time. Source: Lighthouse - Learn more

Offscreen images

Consider lazy-loading offscreen images to improve page load speed and time to interactive. Source: Lighthouse - Learn more

First impression

Eliminates render-blocking JavaScript and CSS in above-the-fold content

This rule triggers when detecting that your HTML references a blocking external resource / file in the above-the-fold portion of your page. Source: PageSpeed Insights - Learn more about JS - Learn more about CSS

Your page has 2 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

URL
https://zestore.fr/wp-content/cache/busting/1/wp-includes/js/jquery/jquery-1.12.4-wp.js
https://zestore.fr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
https://zestore.fr/wp-content/cache/min/1/e6990f76bfb8e0b3b39d0c4c25dd6a52.css
https://fonts.googleapis.com/css?family=Montserrat:100
https://zestore.fr/wp-content/cache/busting/1/wp-content/plugins/woocommerce/assets/css/woocommerce-smallscreen-3.7.0.css
https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.3/themes/smoothness/jquery-ui.css?ver=5.2.3
https://zestore.fr/wp-content/themes/twentyseventeen-child/assets/css/select2/select2.min.css
https://zestore.fr/wp-content/themes/twentyseventeen-child/style.css
...

Prioritizes visible content

This rule triggers when detecting that additional network round trips are required to render the above-the-fold content of the page. Source: PageSpeed Insights - Learn more

Improves server response time

This rule triggers when detecting that your server response time is above 200 ms. Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. Source: PageSpeed Insights - Learn more

Avoids landing page redirects

Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single round trip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance. Source: PageSpeed Insights - Learn more

Usability 94/100 Industry: Retail Omnichannel

Autocomplete is used to suggest popular searches (but can be ignored)Not applicable

Fails if no autocomplete or if the user is not allowed to ignore the autocomplete.

Filtering is available and prominent on search results or category listing pages

Fails if filtering is appropriate but not provided or if sorting is prioritized over filtering in the visual hierarchy.

The product details follow a set pattern making it easier to compare, e.g. bullet points with tech specs

Fails if different product description information formatting from one page to another.

It is possible to check in-store product availability

Fails if in-store product availability is not provided.

All product images are zoomable, without blur

Fails if product images are blurry at full zoom.

Carousels are generally avoided (but they are acceptable if they are well implemented)

Fails if any of the following are seen: carousels auto-rotate, text is not legible, swipe is not supported, next images do not load within 1 second of swipe.

There is a choice to convert without creating an account, i.e. Guest checkout

Fails if no guest checkout.

The most appropriate keyboard for the input type is provided first

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofill

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more
Report created on Oct 03, 2019, 16:55 PM GMT+0 in 11 min.

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 EnvironmentMobile