5.7 sec in total
271 ms
5.2 sec
236 ms
Visit fragonard.com now to see the best up-to-date Fragonard content for France and also check out these interesting facts you probably never knew about fragonard.com
Le parfumeur de Grasse propose parfums, eaux de toilette, bougies, diffuseurs, cosmétiques, savons dans ses usines, boutiques et sur son site internet.
Visit fragonard.comWe analyzed Fragonard.com page load time and found that the first response time was 271 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fragonard.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value12.0 s
0/100
25%
Value9.1 s
14/100
10%
Value1,240 ms
19/100
30%
Value0.105
88/100
15%
Value12.2 s
15/100
10%
271 ms
313 ms
254 ms
258 ms
364 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fragonard.com, 95% (60 requests) were made to Www-us.fragonard.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Www-us.fragonard.com.
Page size can be reduced by 712.9 kB (29%)
2.4 MB
1.7 MB
In fact, the total size of Fragonard.com main page is 2.4 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 57.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 57.0 kB or 84% of the original size.
Potential reduce by 17.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. Fragonard images are well optimized though.
Potential reduce by 442.5 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 442.5 kB or 73% of the original size.
Potential reduce by 196.2 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. Fragonard.com needs all CSS files to be minified and compressed as it can save up to 196.2 kB or 87% of the original size.
Number of requests can be reduced by 30 (49%)
61
31
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fragonard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fragonard.com
271 ms
313 ms
jquery-ui-1.8.16.custom.css
254 ms
commun.css
258 ms
eshop.css
364 ms
jquery.fileupload-ui.css
275 ms
video-js.css
288 ms
jshowoff.css
296 ms
prettyPhoto.css
502 ms
jquery.selectbox.css
501 ms
jquery-1.8.2.min.js
706 ms
jquery.alerts.js
556 ms
jquery-ui-1.9.1.custom.min.js
859 ms
jquery.hoverIntent.minified.js
661 ms
jquery.sharrre.min.js
785 ms
jquery.jshowoff.min.js
789 ms
jquery.selectbox-0.1.3.js
816 ms
jquery.prettyPhoto.js
933 ms
Klib.js
996 ms
App.js
1059 ms
video.js
1207 ms
App_eshop.js
1197 ms
qas.js
1149 ms
fragonard.js
1188 ms
pixel_semitransparent.png
388 ms
loader_barre.gif
491 ms
pixel_semitransparent.png
517 ms
delete.png
557 ms
loader.gif
569 ms
close.gif
601 ms
langue.png
635 ms
country.png
767 ms
search_icon.png
764 ms
basket_icon.png
839 ms
cart_up_arrow.png
871 ms
loader_small.gif
893 ms
logo_1.png
882 ms
barre.png
1015 ms
shadow.png
1035 ms
ban_menu_femme-anglais.jpg
1279 ms
ban_menu_homme_hongrie_gb.jpg
1355 ms
ban_menu_GB_cosme.jpg
1309 ms
GB-90-ans.jpg
1337 ms
homepage%20iris.jpg
1800 ms
naturellemartinHP2.jpg
1754 ms
home-boutiques.jpg
1916 ms
magazinehomepage.jpg
2004 ms
home-usines.jpg
1955 ms
homepage-5.jpg
1839 ms
minirotator3.jpg
2276 ms
minirotator4.jpg
2558 ms
TROUSSE.jpg
2319 ms
techniquehomepage.jpg
2395 ms
ga.js
61 ms
Iris_HP_anglais.jpg
2537 ms
__utm.gif
12 ms
facebook.jpg
2198 ms
twitter.jpg
2365 ms
pinterest.jpg
2324 ms
instagram.jpg
2284 ms
select-icons-fragonard.png
2299 ms
arrowTop.png
156 ms
arrowBottom.png
166 ms
fragonard.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
fragonard.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
fragonard.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Tap targets are not sized appropriately
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fragonard.com can be misinterpreted by Google and other search engines. Our service has detected that French 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 Fragonard.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.
fragonard.com
Open Graph description is not detected on the main page of Fragonard. 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: