4.9 sec in total
534 ms
3.6 sec
713 ms
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.comWe 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.
foreo.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value6.0 s
13/100
25%
Value12.9 s
2/100
10%
Value4,100 ms
1/100
30%
Value0.867
4/100
15%
Value18.8 s
3/100
10%
534 ms
896 ms
162 ms
225 ms
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 size can be reduced by 1.6 MB (38%)
4.2 MB
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.
Potential reduce by 65.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 65.2 kB or 81% of the original size.
Potential reduce by 138.7 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. FOREO images are well optimized though.
Potential reduce by 293.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. 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.
Potential reduce by 1.1 MB
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.
Number of requests can be reduced by 61 (58%)
105
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.
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
colorbox_node.css
229 ms
comment.css
231 ms
date.css
234 ms
datepicker.1.7.css
242 ms
field.css
295 ms
node.css
302 ms
picture_wysiwyg.css
305 ms
search.css
305 ms
search_krumo.css
309 ms
user.css
324 ms
views.css
366 ms
ckeditor.css
375 ms
colorbox_style.css
375 ms
ctools.css
372 ms
dhtml_menu.css
377 ms
commerce_price_savings_formatter.css
400 ms
field_group.field_ui.css
429 ms
commerce_fancy_attributes.css
439 ms
STARTER.css
850 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
600 ms
js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js
544 ms
js_9lDz07E6kUInbBJs69pkmTWSl-TgXRvFJdHO2oOlkT0.js
482 ms
js_vunmgoeoPKH1jiv0g5jWDQprfiq-PwfJSzq1CsKOS5A.js
654 ms
js_7Ukqb3ierdBEL0eowfOKzTkNu-Le97OPm-UqTS5NENU.js
457 ms
5.js
431 ms
logo.svg
117 ms
luna_glblNav_290x174.png
434 ms
LunaMini_glblNav_290x174.png
429 ms
men_glblNav_290x174.png
114 ms
foreo-cleansers-promo.jpg
114 ms
menu-issa-range.png
427 ms
menu-issa-mini-range.png
429 ms
issa-accessories-sub_0.jpg
430 ms
iris_hp_kv_banner.jpg
494 ms
LUNA2-PP-Productimage-Front-Normal%28425x523%29.png
494 ms
LUNAmen2-PP-Productimage-Front%28425x523%29.png
430 ms
03-product_425x523_Pink.png
432 ms
40-ISSA_Hybrid_423x523-04.png
430 ms
HP%20LUNA%202%20633x426.jpg
671 ms
issa_model_ylw_hp_oc_blck_1_0.jpg
735 ms
HP%20mysa%20400x232.jpg
598 ms
Mysa_article_small-02.jpg
631 ms
HP%20cleanser%20men%20400x232.jpg
689 ms
vogue_0.png
605 ms
elle.png
704 ms
logo.svg
705 ms
credit-cards.svg
720 ms
gtm.js
108 ms
language.svg
725 ms
arrow-down.svg
751 ms
sponsor-quote.svg
754 ms
facebook.svg
753 ms
twitter.svg
757 ms
google.svg
779 ms
linkedin.svg
805 ms
pinterest.svg
835 ms
instagram.svg
831 ms
youtube.svg
828 ms
footer-closed-mobile.svg
837 ms
AvenirNextCyr-Light.woff
807 ms
AvenirNextCyr-Medium.woff
879 ms
PTF56F-webfont.woff
875 ms
analytics.js
315 ms
roundtrip.js
573 ms
conversion_async.js
333 ms
oct.js
429 ms
ytc.js
414 ms
watch.js
216 ms
authcache.php
837 ms
iris_hp_kv_banner.jpg
691 ms
HP%20LUNA%202%20633x426.jpg
644 ms
issa_model_ylw_hp_oc_blck_1_0.jpg
647 ms
HP%20mysa%20400x232.jpg
680 ms
Mysa_article_small-02.jpg
677 ms
HP%20cleanser%20men%20400x232.jpg
682 ms
orbit-arrow-left.svg
701 ms
orbit-arrow-right.svg
1054 ms
activityi;src=5139301;type=homep0;cat=hompa0;ord=4720171248331;~oref=https%3A%2F%2Fwww.foreo.com%2F
188 ms
315 ms
linkid.js
80 ms
ec.js
91 ms
112 ms
collect
11 ms
collect
148 ms
aquant.js
129 ms
adsct
186 ms
adsct
212 ms
fbds.js
468 ms
bat.js
162 ms
148 ms
ga-audiences
59 ms
pixel;r=326601703;a=p-ZNpeg4gg9cCL2;orderid=;revenue=;labels=_fp.event.Homepage;fpan=u;fpa=;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460136360484;tzo=-180;ref=https%3A%2F%2Fwww.foreo.com%2F;url=https%3A%2F%2F5139301.fls.doubleclick.net%2Factivityi%3Bsrc%3D5139301%3Btype%3Dhomep0%3Bcat%3Dhompa0%3Bord%3D4720171248331%3B~oref%3Dhttps%253A%252F%252Fwww.foreo.com%252F%3F;ogl=
70 ms
AT7S33ZHPJEEZGLIZFCJ7C.js
217 ms
fbevents.hashing.js
390 ms
out
30 ms
out
386 ms
out
388 ms
out
387 ms
out
387 ms
out
388 ms
418 ms
362 ms
u.php
80 ms
pixel
125 ms
89 ms
75 ms
66 ms
tap.php
30 ms
377928.gif
13 ms
in
7 ms
sync
38 ms
in
9 ms
sd
29 ms
collect
43 ms
5 ms
collect
18 ms
ga-audiences
22 ms
foreo.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
foreo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foreo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
EN
EN
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.
foreo.com
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: