Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

foreo.com

FOREO Sweden l Pro-level Skincare and Oral Care

Page Load Speed

4.9 sec in total

First Response

534 ms

Resources Loaded

3.6 sec

Page Rendered

713 ms

foreo.com screenshot

About Website

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

Discover FOREO's pro-level skincare and oral care products, featuring cutting-edge beauty-tech solutions. Shop now to elevate your skincare routine!

Visit foreo.com

Key Findings

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

Performance Metrics

foreo.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value4,100 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.867

4/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

www.foreo.com

534 ms

10014279-10013669.js

896 ms

system.base.css

162 ms

system.messages.css

225 ms

system.theme.css

231 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 60% of them (73 requests) were addressed to the original Foreo.com, 7% (8 requests) were made to D.adroll.com and 5% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Foreo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (38%)

Content Size

4.2 MB

After Optimization

2.6 MB

In fact, the total size of Foreo.com main page is 4.2 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 65.2 kB

  • Original 80.2 kB
  • After minification 76.1 kB
  • After compression 15.0 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 65.2 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 138.7 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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. FOREO images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 293.1 kB

  • Original 514.9 kB
  • After minification 461.6 kB
  • After compression 221.7 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 293.1 kB or 57% of the original size.

CSS Optimization

-89%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 137.1 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. Foreo.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (58%)

Requests Now

105

After Optimization

44

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

Accessibility Review

foreo.com accessibility score

77

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

foreo.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

foreo.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Foreo.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 Foreo.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

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