5.7 sec in total
356 ms
4.4 sec
996 ms
Visit lekopttorg.ru now to see the best up-to-date Lekopttorg content for Russia and also check out these interesting facts you probably never knew about lekopttorg.ru
Интернет-аптека ЛекОптТорг в Санкт-Петербурге предлагает как редкие и специализированные препараты
Visit lekopttorg.ruWe analyzed Lekopttorg.ru page load time and found that the first response time was 356 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lekopttorg.ru performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.9 s
29/100
25%
Value8.0 s
22/100
10%
Value4,410 ms
0/100
30%
Value0.121
84/100
15%
Value19.7 s
2/100
10%
356 ms
1057 ms
267 ms
548 ms
403 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 24% of them (27 requests) were addressed to the original Lekopttorg.ru, 45% (51 requests) were made to C42e3ab1-bcd6-4e72-9093-18bee9cf7109.selcdn.net and 8% (9 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source C42e3ab1-bcd6-4e72-9093-18bee9cf7109.selcdn.net.
Page size can be reduced by 309.9 kB (4%)
7.5 MB
7.2 MB
In fact, the total size of Lekopttorg.ru main page is 7.5 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. 65% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 206.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 49.9 kB, which is 21% 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 206.4 kB or 87% of the original size.
Potential reduce by 59.9 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. Lekopttorg images are well optimized though.
Potential reduce by 43.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.
Number of requests can be reduced by 39 (36%)
107
68
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lekopttorg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
lekopttorg.ru
356 ms
lekopttorg.ru
1057 ms
ui.design-tokens.min.css
267 ms
template_63f5f22aba377905bc1d36763ecef8d5_v1.css
548 ms
popup.min.css
403 ms
logo.png
401 ms
icons.svg
404 ms
f3e1ba3b1734a15c426047b3dae74fc3.png
1187 ms
76a2654c347c0368d1169ba7552c43ef.png
1440 ms
2b91c119a44ad0c7645ab9bb3e956b1f.png
1475 ms
cc495f50f5d3028efc0ba97150131d74.png
1442 ms
f8266bbaee68db79d919b32b690884e2.png
1242 ms
0260c48736009c2ae41edc41fa338ddd.png
1441 ms
f4a81a19945180a43bef86b6850cee1d.png
1502 ms
cae086d1a6f3a64848afbaad7d17467e.png
1503 ms
684fefb47c9230a5817545839ba4f09a.png
1533 ms
ecb82160f462e2b836c33d9e2c1d29d0.png
1586 ms
a3110267098b2646d00ccc861b817cf8.png
1738 ms
da10076a1a4589e5852e6e5c379a6c29.png
1624 ms
491d7c873697826e81f0b41dddd7fa90.png
1644 ms
af0bbb4100df1e6f0e68d49e6e1359d2.png
1636 ms
a10ddf4d32dd4d0ae5e196d431db724d.png
1714 ms
41cba774fb4d6252026d06b8c5ab905b.png
1793 ms
be43685063e3f8287ae9ded8e5625c7a.png
1756 ms
a5118e67ede4edd5946243c8814bb5f0.png
1753 ms
f86bfa7010186a2638a36293d278ab97.png
1766 ms
6f1a1378c8ef613e21a5f3bad2f8fca6.png
1841 ms
2d00aad3b5b2c321b503ae459cf91f01.jpg
1861 ms
7526717c7f0b8f1b2cdcfb20ef44b27b.jpg
1867 ms
no-photo.jpg
403 ms
0aba51d4-ce2b-11ed-9429-ac1f6bb19d3c.png
360 ms
d296854fe2f9e60aed19bfefcaca71fd.jpg
1750 ms
f289bd96ec0f237f3fb98b27ddca9585.jpg
1757 ms
07deb3b2270ccdf31dabb7c01070b159.jpg
1783 ms
facc9aa63268091ef1df898ac42abb9d.jpg
1824 ms
3074d19285db8c9419d07a1546709c9f.jpg
1863 ms
16a657faff7e99db3d7162c99f40ff6e.jpg
1855 ms
6afdb556048e4b0525e8bbae0f5276bb.png
1871 ms
f2e3f138b43d79efada631f34bfef944.jpg
1871 ms
2300a21310dea4105cd615334cd65193.jpg
1960 ms
817f36c3248f9d40d5060358ebac3bea.jpg
1960 ms
38a05b71324cc03a2cb329df126b4bd9.png
1969 ms
4855037b2a11d14d1523cf5f86f3be38.jpg
1989 ms
ec703a909c2e93c2be1bf378a57555a0.jpg
1986 ms
core.min.js
537 ms
kernel_main_v1.js
534 ms
protobuf.min.js
532 ms
model.min.js
401 ms
core_promise.min.js
526 ms
rest.client.min.js
535 ms
pull.client.min.js
549 ms
705 ms
template_a4916de097c9074627989e11747fa4a7_v1.js
934 ms
default_e8e4a74fffdb032b509c6b8651e0b9da_v1.js
665 ms
JVSviDlehm
304 ms
api.js
40 ms
js
60 ms
basket.js
620 ms
loader.js
660 ms
send.svg
663 ms
footer-phone-decor.png
957 ms
app-store.svg
666 ms
google-play.svg
668 ms
c4c0b2ac58aff718e5e884be0e2f19f3.jpg
1635 ms
preloader.gif
358 ms
royalty.png
360 ms
letter.png
363 ms
Montserrat-Medium.woff
459 ms
Montserrat-Regular.woff
798 ms
Montserrat-Bold.woff
799 ms
ba.js
362 ms
recaptcha__en.js
49 ms
code.js
753 ms
tracking.js
361 ms
tag.js
929 ms
gtm.js
101 ms
JVSviDlehm
184 ms
873ffa2ebfd2568ddb252dd6b8d7fdba.jpeg
939 ms
js
87 ms
analytics.js
16 ms
js
44 ms
eb3cd8e19ad02043a7eb0b20d975de8b.jpg
941 ms
collect
13 ms
JVSviDlehm
554 ms
collect
130 ms
d08dd4fdfa2ca37a6e41d44bbf0eb632.png
779 ms
e5e99d550d36574002bb21f8665c83ed.png
789 ms
3ed6fe3432362c9b64218d4a74c5bb29.png
807 ms
bx_stat
193 ms
64b693f89b5a1a8ddcce2e9fca9fb4a4.png
772 ms
9e8bc40623f3c81db5bd2899daea676b.png
761 ms
1c6cdcd47c7e67447ab59de5e28d9f08.png
797 ms
d6c8e7841b28e95cea38ac44da462d54.png
803 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
227 ms
5ffcd998742564983d94b1628f79ddb8.png
762 ms
3b144ec8ba5ba8b604d9cbc3542137e0.png
750 ms
08cb3253bf090a460784fc6c6a63eb16.png
744 ms
1d0b9baf1f5e7ca2e671ab34756fcb64.svg
735 ms
f00dfff2885571630297f5a009ddd818.png
710 ms
rtrg
128 ms
sync-loader.js
755 ms
counter
124 ms
750 ms
dyn-goal-config.js
250 ms
counter
379 ms
tracker
377 ms
counter
376 ms
advert.gif
738 ms
sync_cookie_image_decide
190 ms
bundle_ru_RU.js
48 ms
tracker
124 ms
tracker
123 ms
tracker
124 ms
lekopttorg.ru 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-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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.
lekopttorg.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
lekopttorg.ru 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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lekopttorg.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 Lekopttorg.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.
lekopttorg.ru
Open Graph description is not detected on the main page of Lekopttorg. 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: