Tools & Wizards About Us
emolium.ru screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

emolium.ru

Официальный сайт препарата Эмолентум: где купить, инструкция, отзывы | Эмолентум

Page Load Speed

6.9 sec in total

First Response

528 ms

Resources Loaded

5.6 sec

Page Rendered

755 ms

emolium.ru screenshot

About Website

Visit emolium.ru now to see the best up-to-date Emolium content for Russia and also check out these interesting facts you probably never knew about emolium.ru

Посетите официальный сайт препарата Эмолентум. Узнайте, где купить, прочитайте инструкцию и отзывы. Получите всю необходимую информацию о препарате Эмолентум.

Visit emolium.ru

Key Findings

We analyzed Emolium.ru page load time and found that the first response time was 528 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

emolium.ru performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value270 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

emolium.ru

528 ms

emolentum.ru

1583 ms

style.css

384 ms

bootstrap.css

528 ms

cards.css

524 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Emolium.ru, 91% (58 requests) were made to Emolentum.ru and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Emolentum.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.0 kB (8%)

Content Size

4.4 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Emolium.ru main page is 4.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. 50% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 35.0 kB

  • Original 45.9 kB
  • After minification 39.8 kB
  • After compression 10.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 6.1 kB, which is 13% 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 35.0 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 308.3 kB

  • Original 4.0 MB
  • After minification 3.7 MB

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. Emolium images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.4 kB

  • Original 306.6 kB
  • After minification 306.6 kB
  • After compression 301.2 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.

CSS Optimization

-10%

Potential reduce by 5.3 kB

  • Original 53.6 kB
  • After minification 53.6 kB
  • After compression 48.3 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. Emolium.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (40%)

Requests Now

58

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Emolium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

emolium.ru

emolium.ru

528 ms

emolentum.ru

emolentum.ru

1583 ms

style.css

style.css

384 ms

bootstrap.css

bootstrap.css

528 ms

cards.css

cards.css

524 ms

animate.min.css

animate.min.css

396 ms

new-logo.png

new-logo.png

390 ms

1178k1xp4gwo92oimtm2g06nn4fichee.webp

1178k1xp4gwo92oimtm2g06nn4fichee.webp

932 ms

835uztwmzb9eboj61ug4r4l4catc4m8a.gif

835uztwmzb9eboj61ug4r4l4catc4m8a.gif

2271 ms

2nktavftut20och51sm5bxly184lxb72.gif

2nktavftut20och51sm5bxly184lxb72.gif

2589 ms

ocbk2pkmi9m773utt0k9d365pk4wqiy7.gif

ocbk2pkmi9m773utt0k9d365pk4wqiy7.gif

2597 ms

le3oq5zxc46lrsfvzhcy60sxm6jbe040.gif

le3oq5zxc46lrsfvzhcy60sxm6jbe040.gif

2977 ms

t375zp4ewyh4appipj9mtpt6t2yqlrbf.png

t375zp4ewyh4appipj9mtpt6t2yqlrbf.png

915 ms

mwzyjyurw7ltvfozkq1fgbqgh6d322cg.png

mwzyjyurw7ltvfozkq1fgbqgh6d322cg.png

1046 ms

xnbqmrdad71sykd6nqhzys9vh926jzm1.png

xnbqmrdad71sykd6nqhzys9vh926jzm1.png

1064 ms

ekb69ju9ukoa0jlldhv0fuffud78mq1d.png

ekb69ju9ukoa0jlldhv0fuffud78mq1d.png

1176 ms

0lszqbpmi1r1crkdfyh8liihivhtx86l.png

0lszqbpmi1r1crkdfyh8liihivhtx86l.png

1198 ms

5wiepon0qxu17uqt1g6usutvh5x0i6z1.png

5wiepon0qxu17uqt1g6usutvh5x0i6z1.png

1436 ms

d879ubvrz3e13nk5fcf86y4gtw1gjllp.png

d879ubvrz3e13nk5fcf86y4gtw1gjllp.png

1598 ms

kcvm5qbkgcmeyed4xbte81ekls1ld054.png

kcvm5qbkgcmeyed4xbte81ekls1ld054.png

1567 ms

l4di8cehgp8bl6ew7xw90n54k0327z23.png

l4di8cehgp8bl6ew7xw90n54k0327z23.png

1699 ms

6rw0p2g9osxfs0xm82gsqzwwxjpr3v20.png

6rw0p2g9osxfs0xm82gsqzwwxjpr3v20.png

1735 ms

693xkivflkm3bzlawvjgv0h762idq2fv.png

693xkivflkm3bzlawvjgv0h762idq2fv.png

1830 ms

y21yirzd4bt2cwa0w0pb03p5sut8wk8a.png

y21yirzd4bt2cwa0w0pb03p5sut8wk8a.png

1870 ms

y73exg70fhrmck9bqscmxl0kvi6nm8p0.png

y73exg70fhrmck9bqscmxl0kvi6nm8p0.png

1961 ms

snhiz9akleme0zqg2rpbhtidy5ug1625.png

snhiz9akleme0zqg2rpbhtidy5ug1625.png

2005 ms

a2vg95d99buph7v05g15rfz71xn6005m.webp

a2vg95d99buph7v05g15rfz71xn6005m.webp

2093 ms

s58ez58cjrw9yyxbxt8y4bgadh4gobo8.png

s58ez58cjrw9yyxbxt8y4bgadh4gobo8.png

2139 ms

emolium.png

emolium.png

2223 ms

core.min.js

core.min.js

2251 ms

kernel_main_v1.js

kernel_main_v1.js

2317 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

2363 ms

footer-logo.png

footer-logo.png

2386 ms

bootstrap.js

bootstrap.js

2361 ms

cards.js

cards.js

2399 ms

callback-response.js

callback-response.js

2428 ms

wow.min.js

wow.min.js

2491 ms

gsap.min.js

gsap.min.js

25 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

39 ms

fullpage.min.js

fullpage.min.js

2531 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

2440 ms

smooth-scrollbar.js

smooth-scrollbar.js

2465 ms

star-ajax.js

star-ajax.js

2468 ms

star-ajax.min.js

star-ajax.min.js

2357 ms

gsap.min.js

gsap.min.js

2304 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

1915 ms

ScrollSmoother.min.js

ScrollSmoother.min.js

1924 ms

custom.js

custom.js

1813 ms

cookie.js

cookie.js

1818 ms

VelaSans.woff

VelaSans.woff

1746 ms

PlayfairDisplay-Italic.ttf

PlayfairDisplay-Italic.ttf

1765 ms

d_kallisto.otf

d_kallisto.otf

1548 ms

menu.png

menu.png

1422 ms

arrow.png

arrow.png

1413 ms

vg6jkpiwwmpkag6il2j0q5xkcrdq5qzu.png

vg6jkpiwwmpkag6il2j0q5xkcrdq5qzu.png

1351 ms

vanatm8qgkujxi0dw2izwxe1k1nu5qmq.png

vanatm8qgkujxi0dw2izwxe1k1nu5qmq.png

1363 ms

b66y2hv21lcglh0bo8zf35p2dmj239mq.png

b66y2hv21lcglh0bo8zf35p2dmj239mq.png

1278 ms

wue6udu6quuvcxvjkukug8bkwp8unpm5.png

wue6udu6quuvcxvjkukug8bkwp8unpm5.png

1246 ms

read.png

read.png

1157 ms

ba.js

ba.js

278 ms

tag.js

tag.js

841 ms

1178k1xp4gwo92oimtm2g06nn4fichee.webp

1178k1xp4gwo92oimtm2g06nn4fichee.webp

392 ms

a2vg95d99buph7v05g15rfz71xn6005m.webp

a2vg95d99buph7v05g15rfz71xn6005m.webp

426 ms

bx_stat

bx_stat

195 ms

Accessibility Review

emolium.ru accessibility score

88

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

emolium.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

emolium.ru SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emolium.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Emolium.ru 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.

Social Sharing Optimization

emolium.ru

Open Graph description is not detected on the main page of Emolium. 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: