5.5 sec in total
158 ms
2.6 sec
2.8 sec
Click here to check amazing Frankbody content. Otherwise, check out these important facts you probably never knew about frankbody.eu
Your bathroom will never be the same again. Clean skincare made from coffee to give you soft, glowing skin. No nasties, so you can be naughty. Wink. ...
Visit frankbody.euWe analyzed Frankbody.eu page load time and found that the first response time was 158 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
frankbody.eu performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value4.7 s
33/100
25%
Value7.4 s
27/100
10%
Value410 ms
67/100
30%
Value0.12
84/100
15%
Value9.4 s
31/100
10%
158 ms
463 ms
278 ms
484 ms
17 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frankbody.eu, 73% (32 requests) were made to Static.thcdn.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.thcdn.com.
Page size can be reduced by 351.1 kB (18%)
1.9 MB
1.6 MB
In fact, the total size of Frankbody.eu main page is 1.9 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 318.6 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 318.6 kB or 80% of the original size.
Potential reduce by 546 B
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. Frankbody images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 47% of the original size.
Potential reduce by 14 B
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. Frankbody.eu has all CSS files already compressed.
Number of requests can be reduced by 6 (15%)
39
33
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankbody. 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 as a result speed up the page load time.
frankbody.eu
158 ms
eu.frankbody.com
463 ms
screen-e786bafae5.css
278 ms
frankbody-takeover.css
484 ms
vendor-4cf02f9634.min.js
17 ms
https://:0/
42 ms
bOdfqw-s-084016.png
669 ms
13228959-1634896968975562.jpg
118 ms
13228962-1814896969703710.jpg
339 ms
13228963-7164896969965460.jpg
235 ms
13228977-1204896970010019.jpg
458 ms
3uU6ShUQ-083730.png
824 ms
THG-PRODUCT-PROMO-SLIDER-1200x1200-112929.jpg
311 ms
13228976-1494967482055556.jpg
733 ms
13228977-1204896970010019.jpg
463 ms
13228978-7674898992301667.jpg
719 ms
13228979-1914898995642461.jpg
822 ms
THG-PRIMARY-BANNER-SUSTAINABILITY600x600-113856.jpg
567 ms
original-Untitled_design_%2825%29-041506.png
724 ms
original-Untitled_design_%2826%29-041530.png
1048 ms
original-Untitled_design_%2827%29-041541.png
1096 ms
original-Untitled_design_%2828%29-041552.png
869 ms
original-Untitled_design_%2829%29-041602.png
906 ms
original-Untitled_design_%2830%29-041613.png
1218 ms
original-Untitled_design_%2825%29-042029.png
1213 ms
original-Untitled_design_%2826%29-042109.png
1022 ms
original-Untitled_design_%2827%29-042119.png
1290 ms
original-Untitled_design_%2828%29-042127.png
1142 ms
original-ICONS_HOMEPAGE_Clean_Text_300px-101327.jpg
1387 ms
original-ICONS_HOMEPAGE_PETA_Text_300px-101333.jpg
1426 ms
original-ICONS_HOMEPAGE_SLS_Text_300px-101340.jpg
1241 ms
ICONS_HOMEPAGE_Australia_Text_507px-100743.jpg
1551 ms
THG_EmailSignUp_Image_290x97_%281%29-083046.jpg
1546 ms
gtm.js
174 ms
FoundersGroteskText-Light.woff
1219 ms
PitchWeb-Semibold.woff
1269 ms
analytics.js
56 ms
25869.js
378 ms
fbevents.js
28 ms
bat.js
88 ms
2219856241628078
153 ms
collect
23 ms
collect
35 ms
ga-audiences
29 ms
frankbody.eu accessibility score
frankbody.eu 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
frankbody.eu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankbody.eu 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 Frankbody.eu 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.
frankbody.eu
Open Graph description is not detected on the main page of Frankbody. 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: