4.3 sec in total
332 ms
3.7 sec
182 ms
Visit eisenberg.com now to see the best up-to-date EISENBERG content for Monaco and also check out these interesting facts you probably never knew about eisenberg.com
Explore skincare for all skin types and needs. Luxury skincare for women and men who expect rapid, visible results from their daily skincare routine.
Visit eisenberg.comWe analyzed Eisenberg.com page load time and found that the first response time was 332 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eisenberg.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value27.3 s
0/100
25%
Value10.8 s
7/100
10%
Value3,960 ms
1/100
30%
Value0.289
42/100
15%
Value24.5 s
0/100
10%
332 ms
639 ms
197 ms
191 ms
190 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 93% of them (82 requests) were addressed to the original Eisenberg.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Hello.myfonts.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Eisenberg.com.
Page size can be reduced by 1.1 MB (25%)
4.2 MB
3.2 MB
In fact, the total size of Eisenberg.com main page is 4.2 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. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 39.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 39.9 kB or 83% of the original size.
Potential reduce by 195.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. EISENBERG images are well optimized though.
Potential reduce by 769.7 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 769.7 kB or 78% of the original size.
Potential reduce by 45.6 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. Eisenberg.com needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 81% of the original size.
Number of requests can be reduced by 42 (51%)
83
41
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EISENBERG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
eisenberg.com
332 ms
www.eisenberg.com
639 ms
styles.css
197 ms
append.css
191 ms
webfonts.css
190 ms
jquery.carousel.skin.css
240 ms
lionbars.css
239 ms
nyroModal.css
238 ms
widgets.css
280 ms
cart.css
280 ms
mirasvit_seo.css
291 ms
sitemap.css
290 ms
prototype.js
481 ms
ccard.js
293 ms
validation.js
371 ms
builder.js
369 ms
effects.js
380 ms
dragdrop.js
380 ms
controls.js
381 ms
slider.js
462 ms
js.js
463 ms
form.js
471 ms
translate.js
474 ms
cookies.js
474 ms
jquery-1.7.1.min.js
747 ms
jquery-ui-1.8.17.custom.min.js
765 ms
jquery.nyroModal.custom.min.js
564 ms
jquery.jcarousel.min.js
566 ms
jquery.lionbars.0.3.min.js
564 ms
jquery.tinyscrollbar.js
565 ms
jquery.touchSwipe.js
656 ms
jquery.sequencer.js
657 ms
jquery.backstretch.min.js
658 ms
menu.js
658 ms
jquery.flashembed.js
784 ms
lemmon-slider.js
783 ms
jquery.transform2d.js
784 ms
gallery.min.js
783 ms
2cfdf7
52 ms
content.js
655 ms
main.js
661 ms
basket.png
160 ms
nav-btn.png
159 ms
logo.png
158 ms
je.png
223 ms
Bildschirmfoto_2012-12-28_um_11.00.02_Kopie.png
158 ms
bubbles.png
227 ms
press_1.png
589 ms
mail-icon_1.png
225 ms
video.png
319 ms
brochures.png
227 ms
woman_2013_1.png
587 ms
pureWhiteRangePicture_1.png
500 ms
EXCELLENCE-EYE-CONTOURS2.png
542 ms
EXCELLENCE-FACE-BODY-HAIR_8.png
412 ms
5FDTS-LE-MAQUILLAGE_2013.png
691 ms
Perfume-Woman-2014.png
1350 ms
les-extraits_4.jpg
684 ms
men_2.png
731 ms
Perfume-Man-2014.png
1265 ms
visage1.png
769 ms
Body2014.png
867 ms
After_Sun.png
879 ms
Filters.png
824 ms
Silk-Scarf-_UK_2014_2.png
1503 ms
search-btn.png
918 ms
logo_318x65.png
959 ms
ga.js
122 ms
gradient-bottom.png
971 ms
gradient-top.png
1011 ms
main-bg.png
1049 ms
back-btn.png
1053 ms
start.png
1374 ms
navigationWrapper-top-shine.png
1129 ms
pureWhiteBackground.png
1334 ms
navigationWrapper-shine.png
1221 ms
footer_gradient.png
1499 ms
footer_shine_700x600.png
1340 ms
iframe_api
126 ms
__utm.gif
23 ms
2CFDF7_0_0.woff
1386 ms
2CFDF7_1_0.woff
1480 ms
logo-footer.png
1297 ms
ajaxLoader.gif
1331 ms
www-widgetapi.js
39 ms
collect
68 ms
styles-ipad.css
96 ms
print.css
94 ms
eisenberg.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
eisenberg.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eisenberg.com 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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eisenberg.com 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 Eisenberg.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.
eisenberg.com
Open Graph description is not detected on the main page of EISENBERG. 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: