Mobile Excellence / Corsaires Studio
Jul 26, 2019, 7:03 PM
Corsaires Studio
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Find out more about the Evaluation
Mobile Friendliness 100/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
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 73/100
Speed Index
-
Speed Index3654.40target < 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
-
Time7.5seconds
-
Resources13requests
-
Bytes in785.1KB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time15.3seconds
-
Resources31requests
-
Bytes in1.4MB
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
- www.corsaires.studio
- www.google-analytics.com
Bytes downloaded
- www.corsaires.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time7535 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 Paint2266.489 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3420.46 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 Idle3420.46 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 Interactive3420.46 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: 10%
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-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
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
Avoids an excessive DOM size386 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 Nodes386target < 1,500 nodes
-
DOM Depth17target < 32
-
Maximum Children52target < 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: 23 %
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 56 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 1 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| https://www.corsaires.studio/wp-content/cache/min/1/5921f3cd9f69fbaa09b78bd11c0b8a11.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 63/100 Industry: Promotional
Brand logo linked to homepage
Fails if doesn't have a logo or clicking it doesn't lead you to homepage.
No ending trailing paths
Fails if doesn't provide at least one of the following: main navigation options on footers, fixed or 'smart' headers/burger-icon, Back to top or close buttons.
Active section is highlighted in navigation menusNot applicable
Fails if current section or page is not visually highlighted in navigation menus, except for internal section pages where it's accepted not to highlight the parent section.
Listing/overview pages with many items implements deferred loading techniquesNot applicable
Fails if the website doesn't provide at least one of the following: lazy-loading, load more buttons, paginator. Doesn't provide a clear reference about the total amount of items in a portfolio or blog page.
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
Fails if transitioning from placeholders to final images changes the rendered size of the element as media loads. Not using a solid color placeholder occupying the same dimensions as the target image, or techniques such as LQIP or SQIP that hint at the content of a media item before it loads. These changes can be disorienting for users and trigger expensive DOM layout operations that consume system resources and contribute to jank.
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.
Make it easy to contact you
Fails if the website does not provide all of the following: easy to find contact options, tap to call, mailto on emails, addresses do not link to gMaps, except being embedded.
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 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
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
| Impact | Snippet | Target | Failure Summary |
|---|---|---|---|
| serious | <div class="map-contact__contact__content">Tell us about your projects!</div> | .map-contact__contact__content | Fix any of the following: Element has insufficient color contrast of 2.5 (foreground color: #fca2a6, background color: #e4002b, font size: 12.8pt, font weight: normal). Expected contrast ratio of 4.5:1 |
... |
|||
Performance 74/100
Speed Index
-
Speed Index4433.94target < 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
-
Time8.6seconds
-
Resources13requests
-
Bytes in784KB
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
-
Time14seconds
-
Resources28requests
-
Bytes in1MB
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
- www.corsaires.studio
- www.google-analytics.com
Bytes downloaded
- www.corsaires.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time8578 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 byte1663 ms
The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more
First Contentful Paint2388.073 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3544.459 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 Idle3544.46 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 Interactive3544.46 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: 11%
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-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
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
Avoids an excessive DOM size499 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 Nodes499target < 1,500 nodes
-
DOM Depth13target < 32
-
Maximum Children52target < 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 JPEGsn/a
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 181 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 1 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| https://www.corsaires.studio/wp-content/cache/min/1/5921f3cd9f69fbaa09b78bd11c0b8a11.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 63/100 Industry: Promotional
Brand logo linked to homepage
Fails if doesn't have a logo or clicking it doesn't lead you to homepage.
No ending trailing paths
Fails if doesn't provide at least one of the following: main navigation options on footers, fixed or 'smart' headers/burger-icon, Back to top or close buttons.
Active section is highlighted in navigation menusNot applicable
Fails if current section or page is not visually highlighted in navigation menus, except for internal section pages where it's accepted not to highlight the parent section.
Listing/overview pages with many items implements deferred loading techniquesNot applicable
Fails if the website doesn't provide at least one of the following: lazy-loading, load more buttons, paginator. Doesn't provide a clear reference about the total amount of items in a portfolio or blog page.
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
Fails if transitioning from placeholders to final images changes the rendered size of the element as media loads. Not using a solid color placeholder occupying the same dimensions as the target image, or techniques such as LQIP or SQIP that hint at the content of a media item before it loads. These changes can be disorienting for users and trigger expensive DOM layout operations that consume system resources and contribute to jank.
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.
Make it easy to contact you
Fails if the website does not provide all of the following: easy to find contact options, tap to call, mailto on emails, addresses do not link to gMaps, except being embedded.
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 <button type="button" class="form-next btn…st btn--sticky">Next</button> 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
| Impact | Snippet | Target | Failure Summary |
|---|---|---|---|
| serious | <span>We are happy to see you.</span> | div[data-os-animation-delay="\32 00"] > span:nth-child(1) | Fix any of the following: Element has insufficient color contrast of 4.23 (foreground color: #7b7b7b, background color: #ffffff, font size: 12.8pt, font weight: normal). Expected contrast ratio of 4.5:1 |
| serious | <span>Tell us a little bit about yourself:</span> | div[data-os-animation-delay="\32 00"] > span:nth-child(3) | Fix any of the following: Element has insufficient color contrast of 4.23 (foreground color: #7b7b7b, background color: #ffffff, font size: 12.8pt, font weight: normal). Expected contrast ratio of 4.5:1 |
... |
|||
Performance 73/100
Speed Index
-
Speed Index3556.01target < 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
-
Time10.2seconds
-
Resources19requests
-
Bytes in1.1MB
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
-
Time14.8seconds
-
Resources30requests
-
Bytes in1.1MB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- www.corsaires.studio
- www.google-analytics.com
Bytes downloaded
- www.corsaires.studio
- www.google-analytics.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time10214 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 byte1651 ms
The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more
First Contentful Paint2249.296 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3392.413 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 Idle3392.41 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 Interactive3392.41 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: 11%
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-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
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
Avoids an excessive DOM size512 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 Nodes512target < 1,500 nodes
-
DOM Depth17target < 32
-
Maximum Children52target < 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 JPEGsn/a
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 283 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 1 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| https://www.corsaires.studio/wp-content/cache/min/1/5921f3cd9f69fbaa09b78bd11c0b8a11.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 63/100 Industry: Promotional
Brand logo linked to homepage
Fails if doesn't have a logo or clicking it doesn't lead you to homepage.
No ending trailing paths
Fails if doesn't provide at least one of the following: main navigation options on footers, fixed or 'smart' headers/burger-icon, Back to top or close buttons.
Active section is highlighted in navigation menusNot applicable
Fails if current section or page is not visually highlighted in navigation menus, except for internal section pages where it's accepted not to highlight the parent section.
Listing/overview pages with many items implements deferred loading techniquesNot applicable
Fails if the website doesn't provide at least one of the following: lazy-loading, load more buttons, paginator. Doesn't provide a clear reference about the total amount of items in a portfolio or blog page.
Prevent layout shiftings when loading media. Set width and height attributes on both <img> and <video> tags
Fails if transitioning from placeholders to final images changes the rendered size of the element as media loads. Not using a solid color placeholder occupying the same dimensions as the target image, or techniques such as LQIP or SQIP that hint at the content of a media item before it loads. These changes can be disorienting for users and trigger expensive DOM layout operations that consume system resources and contribute to jank.
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.
Make it easy to contact you
Fails if the website does not provide all of the following: easy to find contact options, tap to call, mailto on emails, addresses do not link to gMaps, except being embedded.
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 Jul 26, 2019, 13:56 PM GMT+0 in 15 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 | Environment | Mobile |