4.5 sec in total
427 ms
3.9 sec
220 ms
Click here to check amazing DUST And CREAM content for Greece. Otherwise, check out these important facts you probably never knew about dustandcream.gr
Ο καθημερινός προορισμός σας για προϊόντα μακιγιάζ, καλλυντικά, προϊόντα περιποίησης, αρώματα, body mist και όλα τα είδη ομορφιάς! Βρείτε τα όλα εδώ!
Visit dustandcream.grWe analyzed Dustandcream.gr page load time and found that the first response time was 427 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dustandcream.gr performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value18.6 s
0/100
25%
Value19.4 s
0/100
10%
Value6,500 ms
0/100
30%
Value1.142
2/100
15%
Value45.5 s
0/100
10%
427 ms
1540 ms
166 ms
346 ms
265 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original Dustandcream.gr, 8% (5 requests) were made to Creamteam.blob.core.windows.net and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dustandcream.gr.
Page size can be reduced by 263.8 kB (9%)
3.1 MB
2.8 MB
In fact, the total size of Dustandcream.gr main page is 3.1 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 104.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. This page needs HTML code to be minified as it can gain 13.3 kB, which is 11% 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 104.9 kB or 85% of the original size.
Potential reduce by 12.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. DUST And CREAM images are well optimized though.
Potential reduce by 5.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 5.3 kB or 20% of the original size.
Potential reduce by 141.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. Dustandcream.gr needs all CSS files to be minified and compressed as it can save up to 141.2 kB or 85% of the original size.
Number of requests can be reduced by 25 (45%)
56
31
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DUST And CREAM. 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 from 7 to 1 for CSS and as a result speed up the page load time.
dustandcream.gr
427 ms
www.dustandcream.gr
1540 ms
Coloring.css
166 ms
Theme.css
346 ms
System.css
265 ms
jquery.fancybox.css
269 ms
ScriptResource.axd
300 ms
ScriptResource.axd
411 ms
ScriptResource.axd
783 ms
cloud-zoom.1.0.2_custom.js
223 ms
jquery.checkbox.js
224 ms
Clothes_B2C.js
274 ms
css
24 ms
css
34 ms
ed8000828d81407f919cc9040fb897bb.jpg
255 ms
cartIconTop.png
87 ms
wishlistIconTop.png
139 ms
AccountIconTop.png
141 ms
loginIconTop.png
110 ms
GR.png
200 ms
EU.png
173 ms
Logo.png
192 ms
Search.png
270 ms
WebResource.axd
273 ms
WorkingData.ashx
868 ms
WorkingData.ashx
609 ms
WorkingData.ashx
1533 ms
WorkingData.ashx
1382 ms
WorkingData.ashx
1522 ms
ImageView.ashx
488 ms
ImageView.ashx
579 ms
ImageView.ashx
668 ms
facebookIcon.png
690 ms
instagramIcon.png
756 ms
youtubeIcon.png
773 ms
googleplusIcon.png
843 ms
creditCards.png
856 ms
ESLogo.png
931 ms
43c5c190f0824d2eb41c0dc76a527795.jpg
239 ms
80e22220e40b45f49c69e0d260c147c1.jpg
218 ms
db710b2b93074f248d0b2837e8fc2438.jpg
242 ms
c631609ac28a4812b0c93be0a34dc24a.jpg
233 ms
WebResource.axd
913 ms
ScriptResource.axd
107 ms
HeaderBackground.png
83 ms
searchInputBg.gif
88 ms
navBackground.png
152 ms
dropShadowBg.jpg
167 ms
cartIcon.png
174 ms
infoIcon.png
240 ms
wishlistIcon.png
248 ms
ga.js
13 ms
__utm.gif
18 ms
collect
68 ms
topCart.png
90 ms
arrowRightCart.png
84 ms
arrowLeftCart.png
132 ms
bullet.png
88 ms
bulletSelected.png
127 ms
dustandcream.gr 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 input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
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.
dustandcream.gr 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
User Experience
Impact
Issue
Serves images with low resolution
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
dustandcream.gr 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
EL
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dustandcream.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek 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 Dustandcream.gr main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
dustandcream.gr
Open Graph description is not detected on the main page of DUST And CREAM. 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: