Mobile Excellence / Loeven Morcel
Oct 15, 2020, 8:09 PM

Loeven Morcel

By Jomor Design (Canada)
  • 0
    Friendliness
  • 0
    Performance
  • 0
    Usability
  • 0
    PWA
  • 0
    Total
Find out more about the Evaluation
Mobile Excellence
Loeven Morcel
Visit Site

Mobile Friendliness 67/100

Content is not blocked for zoom/scale

The `[user-scalable="no"]` parameter is not present in the `<meta name="viewport">` element and the `[maximum-scale]` parameter is not less than 2.Source: Lighthouse - 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

Uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Source: Lighthouse - 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<div class="no">No. 1</div>.list-row:nth-child(1) > .no-div > .noFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="no">No. 2</div>.list-row:nth-child(2) > .no-div > .noFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="no">No. 3</div>.list-row:nth-child(3) > .no-div > .noFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="no">No. 4</div>.list-row:nth-child(4) > .no-div > .noFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="no">No. 5</div>.list-row:nth-child(5) > .no-div > .noFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 9.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="sub-header">Infolettre</div>.sub-headerFix any of the following: Element has insufficient color contrast of 2.46 (foreground color: #979591, background color: #ece9e3, font size: 6.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 75/100

Speed Index

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

  • Time
    22.2
    seconds
  • Resources
    47
    requests
  • Bytes in
    3.1
    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
    25.4
    seconds
  • Resources
    52
    requests
  • Bytes in
    3.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

  • assets.website-files.com

  • q.stripe.com

  • js.stripe.com

  • www.loevenmorcel.com

  • www.google-analytics.com

  • m.stripe.network

  • fonts.gstatic.com

  • www.google.com

  • m.stripe.com

  • www.googletagmanager.com

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • content-autofill.googleapis.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

  • d3e54v103j8qbb.cloudfront.net

Bytes downloaded

  • assets.website-files.com

  • js.stripe.com

  • fonts.gstatic.com

  • www.googletagmanager.com

  • d3e54v103j8qbb.cloudfront.net

  • www.google-analytics.com

  • www.loevenmorcel.com

  • m.stripe.network

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • ajax.googleapis.com

  • fonts.googleapis.com

  • q.stripe.com

  • m.stripe.com

  • www.google.com

  • content-autofill.googleapis.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 time22192 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 byte1802 ms

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

First Contentful Paint3007.208 ms

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

First meaningful paint3007.208 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 Idle3007.21 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 Interactive3007.21 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: 97%

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

6 resources found

URL
https://cjh.sfo2.cdn.digitaloceanspaces.com/Smooth-Scroll/luxy.js ( 1 minute )
https://js.stripe.com/v3/ ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/shared-af3956f2b43e52584e75241a4c20e806.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/controller-207a0a1b39a190f1e22c08ab25c9f3ee.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/m-outer-c82fcd3637b2420476985f79ea6bba68.js ( 5 minutes )
https://www.google-analytics.com/analytics.js ( 2 hours )
...

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

Potential savings of 4 KiB

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.8e6645153.css<\/span> ( 16.06% )
...

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

Avoids an excessive DOM size370 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
    370
    target < 1,500 nodes
  • DOM Depth
    19
    target < 32
  • Maximum Children
    28
    target < 60 nodes

Compressed ImagesPotential savings of 9 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://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5ee9326d8581023e9680d2d5_Lessard--9-p-800.jpeg81 KB8 KB (10%)
...

Uses Progressive JPEGsScore: 5 %

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 1937 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

Potential savings of 1,260 ms

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.8e6645153.css<\/span>
https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js<\/span>
https://js.stripe.com/v3/<\/span>
...

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 72/100 Industry: Retail Pure play

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.

Key and appropriate information is provided and easy to find on the product page

Fails if any key information is missing or hard to find, i.e. delivery dates, shipping costs, returns policy plus all product pertinent info like size, colour, quantity, etc.

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 67/100

Content is not blocked for zoom/scale

The `[user-scalable="no"]` parameter is not present in the `<meta name="viewport">` element and the `[maximum-scale]` parameter is not less than 2.Source: Lighthouse - 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

Uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Source: Lighthouse - 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<div class="title-text light">subst. masc. </div>.def-wrap:nth-child(1) > .pad-15 > .title-text.lightFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 7.1pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="title-text light">adj. et subst. masc. </div>.def-wrap:nth-child(2) > .pad-15 > .title-text.lightFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 7.1pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="sub-header">Infolettre</div>.sub-headerFix any of the following: Element has insufficient color contrast of 2.46 (foreground color: #979591, background color: #ece9e3, font size: 6.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 71/100

Speed Index

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

  • Time
    7.6
    seconds
  • Resources
    19
    requests
  • Bytes in
    11.8
    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
    120.1
    seconds
  • Resources
    56
    requests
  • Bytes in
    19.4
    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

  • assets.website-files.com

  • js.stripe.com

  • q.stripe.com

  • www.loevenmorcel.com

  • www.google-analytics.com

  • m.stripe.network

  • fonts.gstatic.com

  • www.google.com

  • m.stripe.com

  • www.googletagmanager.com

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • content-autofill.googleapis.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

  • d3e54v103j8qbb.cloudfront.net

Bytes downloaded

  • assets.website-files.com

  • js.stripe.com

  • fonts.gstatic.com

  • www.googletagmanager.com

  • d3e54v103j8qbb.cloudfront.net

  • www.google-analytics.com

  • www.loevenmorcel.com

  • m.stripe.network

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • ajax.googleapis.com

  • fonts.googleapis.com

  • q.stripe.com

  • m.stripe.com

  • www.google.com

  • content-autofill.googleapis.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 time7618 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 byte2119 ms

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

First Contentful Paint3457.161 ms

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

First meaningful paint3457.161 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 Idle3457.16 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 Interactive3457.16 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: 98%

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

6 resources found

URL
https://cjh.sfo2.cdn.digitaloceanspaces.com/Smooth-Scroll/luxy.js ( 1 minute )
https://js.stripe.com/v3/ ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/shared-af3956f2b43e52584e75241a4c20e806.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/controller-207a0a1b39a190f1e22c08ab25c9f3ee.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/m-outer-c82fcd3637b2420476985f79ea6bba68.js ( 5 minutes )
https://www.google-analytics.com/analytics.js ( 2 hours )
...

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

Potential savings of 4 KiB

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.1e761bb60.css<\/span> ( 16.06% )
...

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

Avoids an excessive DOM size394 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
    394
    target < 1,500 nodes
  • DOM Depth
    19
    target < 32
  • Maximum Children
    28
    target < 60 nodes

Compressed ImagesPotential savings of 19280 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://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f87045cd8560179d26ca541_HALO_02_ANGLE1_CSIMPNR-KOA-PNOY.jpg3877 KB2621 KB (67%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f86ff547aaeb94d265c1a28_HALO_02_ANGLE1_CSIMPRS-MAP-PERA.jpg3635 KB2447 KB (67%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f8769273a5b891828938841_HALO_03_ANGLE1_CDOUBNR-KOA-PNOY.jpg3318 KB2246 KB (67%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f8765b24c31b25c3ffe8332_HALO_03_ANGLE1_CDOUBBL-CHB-PCHB.jpg3165 KB2226 KB (70%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f8761a9efdb3046e68c0cb8_HALO_03_ANGLE1_CDOUBRS-MAP-PERA.jpg3130 KB2150 KB (68%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f85f0cf7cc16fdd90ece957_HALO_01_ANGLE1_TDCGR-CER-CER.jpg2190 KB1541 KB (70%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f85ec1779806c83778dccbd_HALO_01_ANGLE1_TDCBE-NOY-NOY.jpg2131 KB1539 KB (72%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f85d7658b3d467b474cbf80_HALO_01_ANGLE1_TDCBL-CHB-CHB.jpg2057 KB1499 KB (72%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f85e62e8960afe9741ae68a_HALO_01_ANGLE1_TDCNR-KOA-CER.jpg2045 KB1492 KB (72%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f85e1e17528b9fa4b607152_HALO_01_ANGLE1_TDCRS-MAP-ERA.jpg2013 KB1483 KB (73%)
https://assets.website-files.com/5e88a02f516d8f94d2aef8e5/5f861ab6bba1e20c00ba3612_HALO_02_ANGLE1_CSIMPBL-CHB-PCHB.jpg1169 KB30 KB (2%)
...

Uses Progressive JPEGsScore: 0 %

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 32657 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

Potential savings of 1,460 ms

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.1e761bb60.css<\/span>
https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js<\/span>
https://js.stripe.com/v3/<\/span>
...

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 72/100 Industry: Retail Pure play

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.

Key and appropriate information is provided and easy to find on the product page

Fails if any key information is missing or hard to find, i.e. delivery dates, shipping costs, returns policy plus all product pertinent info like size, colour, quantity, etc.

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 67/100

Content is not blocked for zoom/scale

The `[user-scalable="no"]` parameter is not present in the `<meta name="viewport">` element and the `[maximum-scale]` parameter is not less than 2.Source: Lighthouse - 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

Uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Source: Lighthouse - 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<div data-wf-sku-bindings="%5B%7B%22from%22%3A%22f_price_%22%2C%22to%22%3A%22innerHTML%22%7D%5D" class="body-18 gray">$&nbsp;820,00&nbsp;CAD</div>.grayFix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #7e7e7e, background color: #ece9e3, font size: 12.0pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<label data-wf-bindings="%5B%7B%22innerHTML%22%3A%7B%22type%22%3A%22PlainText%22%2C%22filter%22%3A%7B%22type%22%3A%22identity%22%2C%22params%22%3A%5B%5D%7D%2C%22dataPath%22%3A%22name%22%7D%7D%5D" class="field-label">Essence</label>div[role="group"] > labelFix any of the following: Element has insufficient color contrast of 2.46 (foreground color: #979591, background color: #ece9e3, font size: 6.8pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<label for="quantity-198310329b1ce76faea0424c153536bb" class="field-label">Quantité</label>.qty-div > label:nth-child(1)Fix any of the following: Element has insufficient color contrast of 2.46 (foreground color: #979591, background color: #ece9e3, font size: 6.8pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<div class="sub-header">Infolettre</div>footer > .footer.container > .footer-content > .new.footer-item > .news-wrap > .sub-headerFix any of the following: Element has insufficient color contrast of 2.46 (foreground color: #979591, background color: #ece9e3, font size: 6.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 78/100

Speed Index

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

  • Time
    16.1
    seconds
  • Resources
    47
    requests
  • Bytes in
    641.2
    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
    19.8
    seconds
  • Resources
    53
    requests
  • Bytes in
    644.6
    KB

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

  • assets.website-files.com

  • q.stripe.com

  • js.stripe.com

  • www.google-analytics.com

  • www.loevenmorcel.com

  • m.stripe.network

  • fonts.gstatic.com

  • www.google.com

  • m.stripe.com

  • www.googletagmanager.com

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • content-autofill.googleapis.com

  • fonts.googleapis.com

  • ajax.googleapis.com

  • stats.g.doubleclick.net

  • d3e54v103j8qbb.cloudfront.net

Bytes downloaded

  • assets.website-files.com

  • js.stripe.com

  • fonts.gstatic.com

  • www.googletagmanager.com

  • d3e54v103j8qbb.cloudfront.net

  • www.google-analytics.com

  • www.loevenmorcel.com

  • m.stripe.network

  • cjh.sfo2.cdn.digitaloceanspaces.com

  • ajax.googleapis.com

  • fonts.googleapis.com

  • q.stripe.com

  • m.stripe.com

  • content-autofill.googleapis.com

  • www.google.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 time16146 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 byte4187 ms

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

First Contentful Paint3304.293 ms

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

First meaningful paint3304.293 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 Idle3304.29 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 Interactive3304.29 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: 97%

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

7 resources found

URL
https://cjh.sfo2.cdn.digitaloceanspaces.com/Smooth-Scroll/luxy.js ( 1 minute )
https://js.stripe.com/v3/ ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/shared-af3956f2b43e52584e75241a4c20e806.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/controller-207a0a1b39a190f1e22c08ab25c9f3ee.js ( 5 minutes )
https://js.stripe.com/v3/fingerprinted/js/m-outer-c82fcd3637b2420476985f79ea6bba68.js ( 5 minutes )
https://www.google-analytics.com/plugins/ua/ec.js ( 1 hour )
https://www.google-analytics.com/analytics.js ( 2 hours )
...

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

Potential savings of 4 KiB

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.1e761bb60.css<\/span> ( 16.06% )
...

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

Avoids an excessive DOM size481 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
    481
    target < 1,500 nodes
  • DOM Depth
    19
    target < 32
  • Maximum Children
    21
    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: 100 %

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 Images

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

Potential savings of 2,450 ms

URL
https://assets.website-files.com/5e879b54bebe7d689af9a75e/css/loevenmorcel20.1e761bb60.css<\/span>
https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js<\/span>
https://js.stripe.com/v3/<\/span>
...

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 72/100 Industry: Retail Pure play

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.

Key and appropriate information is provided and easy to find on the product page

Fails if any key information is missing or hard to find, i.e. delivery dates, shipping costs, returns policy plus all product pertinent info like size, colour, quantity, etc.

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 15, 2020, 20:09 PM GMT+0 in 12 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