6 sec in total
1.1 sec
4.3 sec
531 ms
Visit fr.hom.com now to see the best up-to-date Fr HOM content for Indonesia and also check out these interesting facts you probably never knew about fr.hom.com
Découvrez HOM® l'une des meilleures marque de boxers hommes, sous-vêtements luxe, pyjamas , slips, chaussettes, tee-shirts... avec une Livraison rapide et retour gratuit*
Visit fr.hom.comWe analyzed Fr.hom.com page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fr.hom.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.7 s
1/100
25%
Value11.0 s
6/100
10%
Value2,000 ms
8/100
30%
Value0.004
100/100
15%
Value18.0 s
3/100
10%
1133 ms
28 ms
303 ms
227 ms
228 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 52% of them (78 requests) were addressed to the original Fr.hom.com, 6% (9 requests) were made to Its.tradelab.fr and 5% (8 requests) were made to Cdn.tradelab.fr. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fr.hom.com.
Page size can be reduced by 1.2 MB (45%)
2.6 MB
1.4 MB
In fact, the total size of Fr.hom.com main page is 2.6 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 44.9 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 44.9 kB or 75% of the original size.
Potential reduce by 70.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. Fr HOM images are well optimized though.
Potential reduce by 822.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 822.3 kB or 75% of the original size.
Potential reduce by 237.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. Fr.hom.com needs all CSS files to be minified and compressed as it can save up to 237.0 kB or 87% of the original size.
Number of requests can be reduced by 110 (79%)
139
29
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fr HOM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
fr.hom.com
1133 ms
css
28 ms
global.css
303 ms
blockpermanentlinks.css
227 ms
blockviewed.css
228 ms
blockcontact.css
231 ms
blockcart.css
233 ms
blockspecials.css
247 ms
blocknewproducts.css
367 ms
blockmyaccount.css
366 ms
blockuserinfo.css
374 ms
blocktags.css
375 ms
jquery.autocomplete.css
398 ms
product_list.css
440 ms
blocksearch.css
506 ms
homefeatured.css
508 ms
blocknewsletter.css
517 ms
productcomments.css
517 ms
blockbestsellers.css
549 ms
perfeoblocklanguages.css
580 ms
blocksocial.css
647 ms
superfish-modified.css
648 ms
jquery.mmenu.all.css
664 ms
style.css
661 ms
refineslide.css
702 ms
slick.css
719 ms
mobile.css
793 ms
jquery-1.7.2.min.js
906 ms
jquery.easing.js
807 ms
tools.js
809 ms
ajax-cart.js
856 ms
treeManagement.js
859 ms
jquery.autocomplete.js
936 ms
nostotagging-auto-slots.js
951 ms
hoverIntent.js
953 ms
superfish-modified.js
1009 ms
menu-responsive.js
998 ms
js
51 ms
tag.js
114 ms
sizzle.min.js
17 ms
conversion.js
19 ms
c3b1dc4622.js
314 ms
ld.js
22 ms
atos.css
977 ms
jquery.mmenu.min.all.js
862 ms
jquery.refineslide.min.js
878 ms
homeslider.js
876 ms
modernizr-2.5.3.min.js
916 ms
slick.min.js
925 ms
grid_prestashop.css
888 ms
mobile.js
880 ms
analytics.js
27 ms
245392.js
269 ms
yuzu-latest.js
29 ms
capture-apps-4.6.0.js
26 ms
logo.jpg
179 ms
icon-facebook.png
180 ms
icon-twitter.png
180 ms
icon-youtube.png
178 ms
5.jpg
179 ms
1.jpg
178 ms
6.jpg
317 ms
10.jpg
324 ms
73ad4322909f38daddc981199544f38c.jpg
890 ms
61d49d1705d9bf42799c8bc07c431195.jpg
652 ms
f98b93044a062070a081b9c20f8f9043.jpg
813 ms
c42e36a6c62fb7c12bfdd7d87e5034d5.jpg
613 ms
450aaeb839115c04948705e25016bd8c.jpg
851 ms
b042413f11fd7555375ca32eecd95fb7.jpg
807 ms
lsvreinsurance-7-1-top.jpg
757 ms
lsvreinsurance-8-1-top.jpg
789 ms
26-home.jpg
987 ms
41-home.jpg
959 ms
ho1-original-new.jpg
955 ms
ho1-original-new.jpg
957 ms
sport-n-colors.jpg
993 ms
sport-n-colors.jpg
1043 ms
lsvreinsurance-7-1-bottom.jpg
1099 ms
lsvreinsurance-8-1-bottom.jpg
1098 ms
collect
17 ms
collect
32 ms
collect
64 ms
picto-cart.png
1084 ms
necqvs7v
15 ms
btn-newsletter-top.png
1127 ms
search.png
1126 ms
little_arrow_right.png
1150 ms
arrow-right.gif
1195 ms
collect
128 ms
iframeStorage.html
157 ms
its.tradelab.fr
235 ms
89.js
251 ms
350419.js
306 ms
seg.js
92 ms
103835_home.js
268 ms
fr.hom.com
1200 ms
footer-pipe.png
1119 ms
74 ms
conversion.js
60 ms
c3b1dc4622.js
91 ms
ld.js
59 ms
yuzu.gif
138 ms
event
29 ms
arrows-ffffff.png
1132 ms
shadow.png
1139 ms
sliderPlayPause.png
1181 ms
ga-audiences
133 ms
tags
188 ms
event
193 ms
138 ms
its.tradelab.fr
180 ms
its.tradelab.fr
181 ms
iframeStorage.js
13 ms
89.js
253 ms
4-783.js
23 ms
pixel.gif
32 ms
px
31 ms
px
9 ms
appsmanagerinit
236 ms
uid
14 ms
350388.js
249 ms
pixel
22 ms
UserMatch.ashx
20 ms
pixel
236 ms
116 ms
RtbHouse
214 ms
tagging
89 ms
Pug
26 ms
pixel
27 ms
uid
18 ms
iframe.html
169 ms
uid
21 ms
sd
10 ms
match
11 ms
tap.php
12 ms
cm
131 ms
its.tradelab.fr
86 ms
its.tradelab.fr
84 ms
103835_home_if.js
85 ms
1by1.png
5 ms
its.tradelab.fr
87 ms
350389.js
249 ms
its.tradelab.fr
86 ms
track.adv
168 ms
invisible.gif
260 ms
its.tradelab.fr
93 ms
its.tradelab.fr
87 ms
dis.aspx
187 ms
471461.js
253 ms
4-4678.js
527 ms
4-4678.js
115 ms
fr.hom.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
fr.hom.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fr.hom.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fr.hom.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fr.hom.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.
fr.hom.com
Open Graph description is not detected on the main page of Fr HOM. 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: