Tools & Wizards About Us
facelake.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

facelake.com

Fetal Doppler, Pulse Oximeter, Portable ECG Monitor

Page Load Speed

656 ms in total

First Response

80 ms

Resources Loaded

360 ms

Page Rendered

216 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 80 ms and then it took 576 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

facelake.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value9.8 s

11/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.327

35/100

15%

TTI (Time to Interactive)

Value14.7 s

9/100

10%

Network Requests Diagram

facelake.com

80 ms

css-base.css

28 ms

css-element.css

59 ms

css-contents.css

40 ms

css-edits.css

42 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 19% of them (8 requests) were addressed to the original Facelake.com, 50% (21 requests) were made to Ep.yimg.com and 7% (3 requests) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (119 ms) relates to the external source S.yimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.7 kB (49%)

Content Size

386.5 kB

After Optimization

196.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 19.6 kB

  • Original 24.9 kB
  • After minification 24.8 kB
  • After compression 5.2 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 19.6 kB or 79% of the original size.

Image Optimization

-27%

Potential reduce by 48.6 kB

  • Original 182.9 kB
  • After minification 134.2 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. Obviously, Facelake needs image optimization as it can save up to 48.6 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 105.4 kB

  • Original 158.8 kB
  • After minification 158.3 kB
  • After compression 53.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 105.4 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 16.0 kB

  • Original 20.0 kB
  • After minification 15.5 kB
  • After compression 4.0 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 needs all CSS files to be minified and compressed as it can save up to 16.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (34%)

Requests Now

41

After Optimization

27

  • 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 7 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

facelake.com

facelake.com

80 ms

css-base.css

css-base.css

28 ms

css-element.css

css-element.css

59 ms

css-contents.css

css-contents.css

40 ms

css-edits.css

css-edits.css

42 ms

loader_536a99d.js

loader_536a99d.js

119 ms

ywa.js

ywa.js

54 ms

angelsounds-fetal-doppler-jpd-100s-in-pink-3.gif

angelsounds-fetal-doppler-jpd-100s-in-pink-3.gif

55 ms

finger-oximeter-oxygen-meter-cms50dl-cms-50dl-12.gif

finger-oximeter-oxygen-meter-cms50dl-cms-50dl-12.gif

33 ms

finger-pulse-oximeter-cms50-dl-10.gif

finger-pulse-oximeter-cms50-dl-10.gif

37 ms

pulse-oximeter-pink-cms50dl-11.gif

pulse-oximeter-pink-cms50dl-11.gif

34 ms

pulse-oximeter-with-alarm-15.gif

pulse-oximeter-with-alarm-15.gif

18 ms

finger-pulse-oximeter-cms50d-cms-50d-11.gif

finger-pulse-oximeter-cms50d-cms-50d-11.gif

35 ms

pulse-oximeter-with-alarm-cms50d-plus-cms-50d-plus-10.gif

pulse-oximeter-with-alarm-cms50d-plus-cms-50d-plus-10.gif

38 ms

fl-300-fingertip-pulse-oximeter-blood-oxygen-monitor-bluetooth-5.gif

fl-300-fingertip-pulse-oximeter-blood-oxygen-monitor-bluetooth-5.gif

50 ms

wireless-pulse-oximeter-with-alarm-cms-50e-cms50e-wireless-oxygen-meter-10.gif

wireless-pulse-oximeter-with-alarm-cms-50e-cms50e-wireless-oxygen-meter-10.gif

36 ms

wrist-pulse-oximeter-cms-50f-cms50f-wrist-oxygen-monitor-10.gif

wrist-pulse-oximeter-cms-50f-cms50f-wrist-oxygen-monitor-10.gif

54 ms

handheld-pulse-oximeter-pm-60a-pulse-monitor-3.gif

handheld-pulse-oximeter-pm-60a-pulse-monitor-3.gif

79 ms

handheld-pulse-oximeter-cms60c-cms-60c-3.gif

handheld-pulse-oximeter-cms60c-cms-60c-3.gif

79 ms

sonotrax-b-ultrasound-fetal-doppler-lcd-display-with-back-light-free-gel-17.gif

sonotrax-b-ultrasound-fetal-doppler-lcd-display-with-back-light-free-gel-17.gif

78 ms

jumper-angelsounds-fetal-doppler-baby-heart-prenatal-monitor-jpd-100s-11.gif

jumper-angelsounds-fetal-doppler-baby-heart-prenatal-monitor-jpd-100s-11.gif

79 ms

fetal-doppler-baby-sound-b-with-lcd-3.gif

fetal-doppler-baby-sound-b-with-lcd-3.gif

80 ms

sonotrax-basic-fetal-doppler-baby-heart-monitor-13.gif

sonotrax-basic-fetal-doppler-baby-heart-monitor-13.gif

80 ms

visual-electronic-stethoscope-with-pulse-oximeter-and-ecg-cms-ve-cmsve-4.gif

visual-electronic-stethoscope-with-pulse-oximeter-and-ecg-cms-ve-cmsve-4.gif

80 ms

hand-held-single-channel-ecg-ecg-80a-3.gif

hand-held-single-channel-ecg-ecg-80a-3.gif

77 ms

css-base.css

css-base.css

23 ms

css-base.css

css-base.css

51 ms

ga.js

ga.js

10 ms

img-15946.gif

img-15946.gif

47 ms

css-element.css

css-element.css

43 ms

1458491168409___fc_yhst-40043675472013.js

1458491168409___fc_yhst-40043675472013.js

43 ms

img-15942.gif

img-15942.gif

58 ms

img-15943.gif

img-15943.gif

25 ms

__utm.gif

__utm.gif

26 ms

combo

combo

7 ms

combo

combo

19 ms

promo_manager_bui_a784667.js

promo_manager_bui_a784667.js

5 ms

cpers-3ab41d0.js

cpers-3ab41d0.js

7 ms

promo_manager_bui_193214.css

promo_manager_bui_193214.css

4 ms

product

product

25 ms

product

product

24 ms

sprite.png

sprite.png

13 ms

Accessibility Review

facelake.com accessibility score

79

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

<frame> or <iframe> elements do not have a title

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

77

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

    N/A

  • Encoding

    N/A

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Facelake.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

facelake.com

Open Graph description is not detected on the main page of Facelake. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: