Find out more about the Evaluation
Performance 68/100
Speed Index
-
Speed Index8832.70target < 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
-
Time16.5seconds
-
Resources57requests
-
Bytes in1.5MB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time17.4seconds
-
Resources60requests
-
Bytes in1.5MB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- likhaaesthetic.ie
- use.typekit.net
- js.stripe.com
- m.stripe.network
- www.instagram.com
- m.stripe.com
- checkout.stripe.com
- www.googletagmanager.com
- www.google-analytics.com
- static.cloudflareinsights.com
- ocsp.digicert.com
- p.typekit.net
Bytes downloaded
- likhaaesthetic.ie
- use.typekit.net
- js.stripe.com
- www.googletagmanager.com
- m.stripe.network
- static.cloudflareinsights.com
- www.instagram.com
- checkout.stripe.com
- ocsp.digicert.com
- m.stripe.com
- p.typekit.net
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time16486 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 byte1695 ms
The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more
First Contentful Paint3961.441 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3961.441 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 Idle3961.44 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 Interactive3961.44 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: 96%
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
5 resources found
| URL |
|---|
| https://js.stripe.com/v3/ ( 5 minutes ) |
| https://m.stripe.network/out-4.5.35.js ( 5 minutes ) |
| https://js.stripe.com/v3/fingerprinted/js/m-outer-d887d0dff5675390e1f75e9f1623eaa0.js ( 5 minutes ) |
| https://static.cloudflareinsights.com/beacon.min.js ( 1 day ) |
| https://p.typekit.net/p.css?s=1&k=lpi0kvl&ht=tk&f=10881.10882.10884.10885.15357.15358.15361.15362.32874.32875&a=7214688&app=typekit&e=css ( 1 week ) |
... |
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 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 size561 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 Nodes561target < 1,500 nodes
-
DOM Depth13target < 32
-
Maximum Children45target < 60 nodes
Compressed ImagesPotential savings of 68 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
| Thumbnails | URL | Original | Potential Savings |
|---|---|---|---|
 | https://likhaaesthetic.ie/wp-content/uploads/2021/02/image01.jpg | 306 KB | 68 KB (22%) |
... |
|||
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 160 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 2,080 ms
| URL |
|---|
| https://likhaaesthetic.ie/wp-includes/css/dist/block-library/style.min.css?ver=5.7.2<\/span> |
| https://checkout.stripe.com/v3/checkout/button.css<\/span> |
| https://likhaaesthetic.ie/wp-content/themes/wondr/dist/index.css?ver=5.0.0<\/span> |
| https://likhaaesthetic.ie/wp-includes/js/jquery/jquery.min.js?ver=3.5.1<\/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
Performance 67/100
Speed Index
-
Speed Index8917.07target < 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
-
Time19.9seconds
-
Resources62requests
-
Bytes in2.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
-
Time22.7seconds
-
Resources67requests
-
Bytes in2.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
- likhaaesthetic.ie
- www.instagram.com
- use.typekit.net
- js.stripe.com
- scontent-iad3-2.cdninstagram.com
- m.stripe.network
- graph.instagram.com
- ocsp.digicert.com
- likha.wpengine.com
- m.stripe.com
- checkout.stripe.com
- www.googletagmanager.com
- www.google-analytics.com
- static.cloudflareinsights.com
- p.typekit.net
Bytes downloaded
- likhaaesthetic.ie
- scontent-iad3-2.cdninstagram.com
- www.instagram.com
- use.typekit.net
- js.stripe.com
- www.googletagmanager.com
- m.stripe.network
- static.cloudflareinsights.com
- ocsp.digicert.com
- checkout.stripe.com
- likha.wpengine.com
- m.stripe.com
- graph.instagram.com
- p.typekit.net
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- video
- other
Bytes downloaded
- html
- js
- css
- image
- font
- video
- other
Speed
Load time19913 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 byte2030 ms
The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more
First Contentful Paint3896.236 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3896.236 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 Idle3896.24 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 Interactive3896.24 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
5 resources found
| URL |
|---|
| https://js.stripe.com/v3/ ( 5 minutes ) |
| https://m.stripe.network/out-4.5.35.js ( 5 minutes ) |
| https://js.stripe.com/v3/fingerprinted/js/m-outer-60c368c1e1eddba7bd149e4b4f5408df.js ( 5 minutes ) |
| https://static.cloudflareinsights.com/beacon.min.js ( 1 day ) |
| https://p.typekit.net/p.css?s=1&k=lpi0kvl&ht=tk&f=10881.10882.10884.10885.15357.15358.15361.15362.32874.32875&a=7214688&app=typekit&e=css ( 1 week ) |
... |
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 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 size488 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 Nodes488target < 1,500 nodes
-
DOM Depth13target < 32
-
Maximum Children45target < 60 nodes
Compressed ImagesPotential savings of 222 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
| Thumbnails | URL | Original | Potential Savings |
|---|---|---|---|
 | https://likhaaesthetic.ie/wp-content/uploads/2021/03/Frame-32.jpg | 121 KB | 83 KB (69%) |
 | https://likhaaesthetic.ie/wp-content/uploads/2021/03/Frame-30.jpg | 98 KB | 69 KB (69%) |
 | https://likhaaesthetic.ie/wp-content/uploads/2021/03/Polish2.jpg | 77 KB | 28 KB (36%) |
 | https://likhaaesthetic.ie/wp-content/uploads/2021/03/SPF2.jpg | 62 KB | 23 KB (36%) |
 | https://likhaaesthetic.ie/wp-content/uploads/2021/03/Retinol2.jpg | 45 KB | 17 KB (38%) |
... |
|||
Uses Progressive JPEGsScore: 16 %
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,080 ms
| URL |
|---|
| https://likhaaesthetic.ie/wp-includes/css/dist/block-library/style.min.css?ver=5.7.2<\/span> |
| https://checkout.stripe.com/v3/checkout/button.css<\/span> |
| https://likhaaesthetic.ie/wp-content/themes/wondr/dist/index.css?ver=5.0.0<\/span> |
| https://likhaaesthetic.ie/wp-includes/js/jquery/jquery.min.js?ver=3.5.1<\/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
Report created on Jun 30, 2021, 08:52 AM GMT+0 in 13 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 | Virginia USA - EC2 |
| Browser | Chrome - Emulated Motorola G (gen 4) | |
| 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 |