Tools & Wizards About Us
facelake.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

facelake.com

Fetal Doppler, Pulse Oximeter, Portable ECG Monitor

Page Load Speed

3.4 sec in total

First Response

576 ms

Resources Loaded

2.5 sec

Page Rendered

321 ms

facelake.com screenshot

About Website

Click here to check amazing Facelake content for United States. Otherwise, check out these important facts you probably never knew about facelake.com

Pulse Oximeters, Fetal Dopplers, and Portable ECG Monitors from FaceLake. Top-rated brand of best selling pulse oximeters. One of the most popular brands of digital pulse oximeters on Amazon, Walmart,...

Visit facelake.com

Key Findings

We analyzed Facelake.com page load time and found that the first response time was 576 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

facelake.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

facelake.com

576 ms

gtm.js

121 ms

css

117 ms

css

181 ms

rt.vendors.scss.css

142 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 43% of them (20 requests) were addressed to the original Facelake.com, 9% (4 requests) were made to Cdn.shopify.com and 7% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (761 ms) belongs to the original domain Facelake.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (64%)

Content Size

1.8 MB

After Optimization

664.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Facelake.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 186.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.2 MB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 712 B

  • Original 18.8 kB
  • After minification 18.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Facelake images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 313.0 kB
  • After minification 313.0 kB
  • After compression 311.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.8 kB

  • Original 151.6 kB
  • After minification 151.6 kB
  • After compression 148.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Facelake.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (80%)

Requests Now

41

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facelake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

facelake.com

facelake.com

576 ms

gtm.js

gtm.js

121 ms

css

css

117 ms

css

css

181 ms

rt.vendors.scss.css

rt.vendors.scss.css

142 ms

rt.application.scss.css

rt.application.scss.css

91 ms

rt.custom.scss.css

rt.custom.scss.css

83 ms

custom_code.scss.css

custom_code.scss.css

81 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

90 ms

preloads.js

preloads.js

352 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

135 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

135 ms

style.css

style.css

104 ms

loader.js

loader.js

374 ms

inbox-chat-loader.js

inbox-chat-loader.js

307 ms

rt.application.js

rt.application.js

276 ms

theme.js

theme.js

59 ms

css

css

292 ms

wc-review.css

wc-review.css

376 ms

wc-product-review.js

wc-product-review.js

382 ms

ndnapps-jslibrary.js

ndnapps-jslibrary.js

427 ms

booster-page-speed-optimizer.js

booster-page-speed-optimizer.js

355 ms

amplitude-6.2.0-min.gz.js

amplitude-6.2.0-min.gz.js

232 ms

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

206 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

205 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

204 ms

logo.jpg

logo.jpg

150 ms

facelake_logo_121321.png

facelake_logo_121321.png

151 ms

payment-icon.png

payment-icon.png

150 ms

font

font

200 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

112 ms

8AAngBY2BkYGDgA2IJBhBgAvKZGViBJAuYxwAABJsAOgAAeAFjYGBgZACCk535hiD60tn0azAaAEqpB6wAAA==

8AAngBY2BkYGDgA2IJBhBgAvKZGViBJAuYxwAABJsAOgAAeAFjYGBgZACCk535hiD60tn0azAaAEqpB6wAAA==

4 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

761 ms

base.css

base.css

5 ms

font

font

8 ms

21e29a2f6b1332caaad08b98f.js

21e29a2f6b1332caaad08b98f.js

183 ms

loader.js

loader.js

647 ms

resultpage.js

resultpage.js

190 ms

klaviyo.js

klaviyo.js

133 ms

installed.js

installed.js

132 ms

pushowl-shopify.js

pushowl-shopify.js

155 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

298 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

30 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

40 ms

runtime.c2eb0d014838986979b7.js

runtime.c2eb0d014838986979b7.js

7 ms

sharedUtils.e8c90ec039ff40fd1c44.js

sharedUtils.e8c90ec039ff40fd1c44.js

21 ms

Accessibility Review

facelake.com accessibility score

81

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

facelake.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

facelake.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facelake.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Facelake.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

facelake.com

Open Graph data is detected on the main page of Facelake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: