6.3 sec in total
1.4 sec
4.6 sec
347 ms
Visit eclatant.pt now to see the best up-to-date Eclatant content and also check out these interesting facts you probably never knew about eclatant.pt
A nossa coleção inclui perfumes, maquilhagem, cuidados de pele e produtos essenciais para cuidar do cabelo, juntamente com uma gama completa de conjuntos de oferta,
Visit eclatant.ptWe analyzed Eclatant.pt page load time and found that the first response time was 1.4 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 75% of websites can load faster.
eclatant.pt performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value14.4 s
0/100
25%
Value10.2 s
8/100
10%
Value920 ms
30/100
30%
Value0.162
72/100
15%
Value14.8 s
8/100
10%
1408 ms
73 ms
95 ms
97 ms
584 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 49% of them (21 requests) were addressed to the original Eclatant.pt, 19% (8 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Eclatant.pt.
Page size can be reduced by 123.6 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Eclatant.pt main page is 1.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 705.3 kB which makes up the majority of the site volume.
Potential reduce by 114.4 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. This page needs HTML code to be minified as it can gain 40.5 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 114.4 kB or 82% of the original size.
Potential reduce by 6.4 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. Eclatant images are well optimized though.
Potential reduce by 2.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 197 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. Eclatant.pt has all CSS files already compressed.
Number of requests can be reduced by 10 (36%)
28
18
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eclatant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.eclatant.pt
1408 ms
gtm.js
73 ms
css
95 ms
css
97 ms
theme-fa728a.css
584 ms
bottom-b19032.js
770 ms
api.js
42 ms
widget10_FB3.min.js
1320 ms
pa-5ef3ef30bb91310015000461.js
439 ms
js
117 ms
js
50 ms
recaptcha__en.js
34 ms
eclatant-logo-1525335628.jpg
138 ms
358db71487ba7d835dae33cf8da7f1cd2f74cedf_Eclatant-Dior2.jpg
373 ms
932dfd3ff0df53705e7112c6ecdae4e6ce91eaf1_Perfume_Yves%20Saint%20Laurent2.jpg
403 ms
9792ee0ab21ace6e1005f684d6f4b9f00a21932e_Perfume_Chanel.jpg
328 ms
2c6287608b9a5f9aa5f0faddb7f62c3d1a0ca79e_Perfume_CarolinaHerrera2.jpg
602 ms
reclamacoes.JPG
328 ms
1.jpg
329 ms
8.jpg
377 ms
9.jpg
417 ms
10.jpg
418 ms
11.jpg
467 ms
12.jpg
471 ms
pagamento.png
500 ms
97 ms
tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf
93 ms
tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf
107 ms
9f2144213fad53d4e0fdb26ecf93865f.woff
478 ms
892667349c5cff6fcf7e40439596b97c.woff
564 ms
ac327c4db6284ef64ebe872b6308f5da.woff
430 ms
012cf6a10129e2275d79d6adac7f3b02.woff
434 ms
fontawesome-webfont.woff
460 ms
fbevents.js
93 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf
79 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf
90 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSWaA.ttf
88 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWWaA.ttf
88 ms
tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf
80 ms
tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf
80 ms
widget10-right-562_script.js
789 ms
25 ms
1444067435697060
120 ms
eclatant.pt 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
eclatant.pt 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
eclatant.pt 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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eclatant.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Eclatant.pt 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.
eclatant.pt
Open Graph description is not detected on the main page of Eclatant. 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: