9.3 sec in total
757 ms
8.2 sec
408 ms
Welcome to lektrava.ru homepage info - get ready to check Lektrava best content for Russia right away, or after learning these important things about lektrava.ru
Энциклопедия лекарственных растений, фото, статьи фитотерапевтов, советы по применению, отзывы, инструкции по применению, противопоказания
Visit lektrava.ruWe analyzed Lektrava.ru page load time and found that the first response time was 757 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lektrava.ru performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value28.4 s
0/100
25%
Value27.0 s
0/100
10%
Value51,760 ms
0/100
30%
Value0.066
97/100
15%
Value68.2 s
0/100
10%
757 ms
71 ms
64 ms
186 ms
209 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 78% of them (69 requests) were addressed to the original Lektrava.ru, 6% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Lektrava.ru.
Page size can be reduced by 1.4 MB (47%)
2.9 MB
1.5 MB
In fact, the total size of Lektrava.ru main page is 2.9 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 67.2 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 19.7 kB, which is 25% 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 67.2 kB or 83% of the original size.
Potential reduce by 120.0 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. Lektrava images are well optimized though.
Potential reduce by 902.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 902.7 kB or 76% of the original size.
Potential reduce by 264.4 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. Lektrava.ru needs all CSS files to be minified and compressed as it can save up to 264.4 kB or 84% of the original size.
Number of requests can be reduced by 44 (54%)
82
38
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lektrava. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
lektrava.ru
757 ms
bootstrap.css
71 ms
bootstrap-theme.min.css
64 ms
ss.css
186 ms
core.css
209 ms
imyie.littleadmin.css
206 ms
jquery.formstyler.css
209 ms
slick.css
213 ms
webkit.css
208 ms
popup.css
793 ms
style.css
601 ms
style.css
605 ms
styles.css
370 ms
template_styles.css
542 ms
jquery-1.11.2.min.js
82 ms
bootstrap.js
54 ms
ss.js
361 ms
core.js
632 ms
core_ajax.js
537 ms
core_window.js
757 ms
jquery-ui-1.10.4.custom.css
629 ms
jquery.fancybox.css
708 ms
css
63 ms
css
65 ms
css
76 ms
jquery.js
926 ms
raphael.js
865 ms
jquery.mousewheel.js
745 ms
mapsvg.js
965 ms
jquery-ui-1.10.4.custom.min.js
965 ms
jquery.ui.touch-punch.min.js
863 ms
jquery.formstyler.min.js
875 ms
jquery.fancybox.js
1008 ms
jQuery-UI-Dialog-ClickOutside.js
956 ms
jquery.maskedinput.min.js
1009 ms
jquery.columnizer.js
1030 ms
jquery.form.plugin.js
1104 ms
jquery.placeholder.min.js
1105 ms
indi.js
1100 ms
template.js
1107 ms
slick.min.js
1721 ms
script.js
1165 ms
script.js
1271 ms
ba.js
303 ms
logo.gif
288 ms
icons.gif
289 ms
47753809fa93aee8d46e95bfe6cd2a51.png
2251 ms
aeb5df18bcf3784e9ffece685fe68a62.png
3688 ms
f524b4d0b74d7571a421e0a17bdcda47.jpg
851 ms
20a5ac2a471cf4fc00dd098f86c3b146.png
1178 ms
dbea9d55341fafee5f2287665eafc8be.png
1576 ms
main-action.jpg
290 ms
9c59964946e9fc84d47f6fcc7f8a913c.jpg
451 ms
3e609b06f1de6234273148fd87f84428.jpg
564 ms
6d57cbef06ab87a45bc84911681cf907.jpg
689 ms
8545271162c46fb6e293c83df9dc86e8.JPG
843 ms
e91e75cc7862110742615105f2873c74.jpg
949 ms
c0a0f8b6e3871b27fe9e6872991f522a.jpg
1076 ms
3c8b0e08aede62a6ca1145201b2e6555.jpg
1071 ms
3e609b06f1de6234273148fd87f84428.jpg
1970 ms
6d57cbef06ab87a45bc84911681cf907.jpg
1463 ms
8545271162c46fb6e293c83df9dc86e8.JPG
1659 ms
e91e75cc7862110742615105f2873c74.jpg
1722 ms
c0a0f8b6e3871b27fe9e6872991f522a.jpg
1940 ms
3c8b0e08aede62a6ca1145201b2e6555.jpg
1892 ms
97ed298d37a8ad94fd9ad26cfd99b22d.jpg
2402 ms
4804c1f7f3f39961acd071919bcaaff0.jpg
2827 ms
94fe25ff32c010e282dea4d468e77b34.jpg
2466 ms
37406fa146af3a9dd72d010241caeb36.jpg
2925 ms
025af61d81d5eaa587ef4b177eccbc85.jpg
2492 ms
3ad562e187bad7d4418a3a2322c16a37.jpg
2760 ms
about.jpg
2575 ms
search-icon.png
2570 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
245 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
249 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
302 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
303 ms
EInbV5DfGHOiMmvb1Xr-hmeP1y_Bkidl4ESyB_O2G_c.ttf
303 ms
main-herb.png
5457 ms
icons-types.png
2668 ms
green-list.png
2876 ms
footer-folium.png
2904 ms
analytics.js
167 ms
watch.js
163 ms
code.js
334 ms
collect
28 ms
bx_stat
258 ms
counter
172 ms
tracker
186 ms
lektrava.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Form elements do not have associated labels
Links do not have a discernible name
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
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.
lektrava.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lektrava.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
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lektrava.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Lektrava.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.
lektrava.ru
Open Graph description is not detected on the main page of Lektrava. 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: