4.7 sec in total
1.2 sec
2.9 sec
634 ms
Click here to check amazing E Apteka content for Russia. Otherwise, check out these important facts you probably never knew about e-apteka.ru
Электронная АПТЕКА: поиск, заказ, доставка лекарств в московских аптеках
Visit e-apteka.ruWe analyzed E-apteka.ru page load time and found that the first response time was 1.2 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
e-apteka.ru performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.7 s
59/100
25%
Value7.0 s
33/100
10%
Value230 ms
86/100
30%
Value0.236
53/100
15%
Value7.2 s
51/100
10%
1200 ms
332 ms
164 ms
289 ms
324 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 82% of them (27 requests) were addressed to the original E-apteka.ru, 6% (2 requests) were made to U8196.26.spylog.com and 3% (1 request) were made to Tools.spylog.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain E-apteka.ru.
Page size can be reduced by 35.9 kB (51%)
70.5 kB
34.6 kB
In fact, the total size of E-apteka.ru main page is 70.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Images take 29.3 kB which makes up the majority of the site volume.
Potential reduce by 23.1 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 4.3 kB, which is 15% 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 23.1 kB or 80% of the original size.
Potential reduce by 5.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. Obviously, E Apteka needs image optimization as it can save up to 5.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.9 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.9 kB or 56% of the original size.
Potential reduce by 1.7 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. E-apteka.ru needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 82% of the original size.
Number of requests can be reduced by 18 (62%)
29
11
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Apteka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
e-apteka.ru
1200 ms
css3.css
332 ms
s1.gif
164 ms
s1-1.gif
289 ms
s2.gif
324 ms
s2-2.gif
326 ms
2.gif
323 ms
lgm-lg.gif
487 ms
lgm-0.gif
325 ms
lgm-l.gif
454 ms
lgm-k.gif
485 ms
lgm-ea0.gif
484 ms
lgm-ea000.gif
484 ms
shapka-fn.gif
484 ms
poisk.gif
611 ms
VoltarenEmulgel.jpg
683 ms
Bilobil-apt.jpg
823 ms
Persen.jpg
677 ms
Exoderil.jpg
649 ms
fofrstu.gif
642 ms
fofrstb.gif
768 ms
fn.jpg
777 ms
22.gif
783 ms
fofztr.gif
810 ms
fofrstc.gif
816 ms
fofrstcr.gif
902 ms
fofrstcc.gif
935 ms
counter2.2.js
404 ms
cnt
749 ms
hit
255 ms
counter2
135 ms
u8196.26.spylog.com
251 ms
cnt
252 ms
e-apteka.ru 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
e-apteka.ru 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
e-apteka.ru SEO score
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
N/A
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-apteka.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that E-apteka.ru main page’s claimed encoding is windows-1251. 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.
e-apteka.ru
Open Graph description is not detected on the main page of E Apteka. 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: