3.6 sec in total
625 ms
2.6 sec
376 ms
Visit altaivita.ru now to see the best up-to-date Altaivita content for Russia and also check out these interesting facts you probably never knew about altaivita.ru
Интернет-магазин алтайских лечебных трав и продуктов для здоровья «Алтайвита» предлагает большой ассортимент травяного чая, алтайского меда, кедровых орехов и масла. Доставка по России и всему миру
Visit altaivita.ruWe analyzed Altaivita.ru page load time and found that the first response time was 625 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
altaivita.ru performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value8.3 s
2/100
25%
Value11.2 s
5/100
10%
Value15,510 ms
0/100
30%
Value0.011
100/100
15%
Value27.1 s
0/100
10%
625 ms
116 ms
559 ms
226 ms
69 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 59% of them (47 requests) were addressed to the original Altaivita.ru, 15% (12 requests) were made to Vk.com and 5% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (881 ms) belongs to the original domain Altaivita.ru.
Page size can be reduced by 393.8 kB (35%)
1.1 MB
741.9 kB
In fact, the total size of Altaivita.ru main page is 1.1 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. 40% of websites need less resources to load. Images take 657.3 kB which makes up the majority of the site volume.
Potential reduce by 22.0 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.4 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 22.0 kB or 77% of the original size.
Potential reduce by 31.8 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. Altaivita images are well optimized though.
Potential reduce by 236.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 236.9 kB or 71% of the original size.
Potential reduce by 103.2 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. Altaivita.ru needs all CSS files to be minified and compressed as it can save up to 103.2 kB or 89% of the original size.
Number of requests can be reduced by 40 (54%)
74
34
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Altaivita. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
altaivita.ru
625 ms
niftycube.js
116 ms
jquery.min.js
559 ms
up_script.js
226 ms
css
69 ms
css
83 ms
overridestyles.css
224 ms
head.js
225 ms
main.css
466 ms
general.css
233 ms
style.css
338 ms
functions.js
446 ms
behavior.js
339 ms
widget_checkout.js
464 ms
frame.js
448 ms
jquery.fancybox.pack.js
579 ms
jquery.mousewheel-3.0.6.pack.js
578 ms
jquery.fancybox.css
578 ms
cookie.jquery.js
583 ms
init_cookie.js
582 ms
init_why.js
661 ms
openapi.js
400 ms
ga.js
51 ms
bg.jpg
225 ms
logo.png
121 ms
ruspost.jpg
116 ms
%D0%BA%D0%B0%D0%BC%D0%B5%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BC%D0%B0%D1%81%D0%BB%D0%BE1_thm.JPG
117 ms
%D0%BC%D1%83%D0%BC%D0%B8%D0%B51_thm.JPG
115 ms
%D1%80%D0%B0%D1%81%D1%82%D0%BE%D1%80%D0%BE%D0%BF%D1%88%D0%B0%20%282%29_thm.jpg
121 ms
%D0%BB%D0%B0%D0%BF%D1%87%D0%B0%D1%82%D0%BA%D0%B01_thm.JPG
227 ms
cat166.jpg
230 ms
%D1%82%D1%80%D0%B0%D0%B2%D1%8B_%D0%B0%D0%B2%D0%B0hu.jpg
232 ms
loi1.jpg
237 ms
%D0%9C%D1%91%D0%B4_%D0%93%D0%BE%D1%80%D0%BD%D1%8B%D0%B9_resize4p.jpg
236 ms
%D0%BD%D0%B0_%D0%B3%D0%BB%D0%B0%D0%B2%D0%BD%D1%83%D1%8E_%D0%BD%D0%BE%D0%B2je.jpg
334 ms
nabor-bodr3_resizekb.jpg
334 ms
IMG_7657l9.jpg
337 ms
watch.js
170 ms
bg-top-right2.png
334 ms
bg-bot-left.png
696 ms
bg-bot-right.png
577 ms
bg-top-left.png
777 ms
bg-top-right.png
881 ms
bg_header_left.jpg
435 ms
bg_header_right.jpg
439 ms
ico_basket.png
548 ms
ico_phone.gif
551 ms
shadow_menu.png
658 ms
ico_menu.png
662 ms
menu2.png
693 ms
wave.gif
768 ms
7ScxVbQobRlSVgZveDbDiA.ttf
112 ms
UyYrYy3ltEffJV9QueSi4aUdwd0g3YZvPtKezrP11hs.ttf
148 ms
upload.gif
140 ms
widget_community.php
267 ms
trackjs.js
552 ms
watch.js
434 ms
loader_nav19130_3.js
129 ms
lite.css
132 ms
lite.js
382 ms
lang3_0.js
255 ms
widget_community.css
257 ms
xdm.js
260 ms
al_community.js
258 ms
advert.gif
85 ms
track.php
285 ms
__utm.gif
18 ms
collect
104 ms
Olly1wekQrM.jpg
388 ms
0rGEvwqhLc0.jpg
388 ms
e_0e26185d.jpg
389 ms
XA1xuRzRwOk.jpg
389 ms
2yKslWR42-4.jpg
394 ms
SCkQGUf1SrM.jpg
392 ms
wfOCK7EE8ts.jpg
400 ms
camera_50.png
129 ms
w_logo.png
131 ms
1
85 ms
niftyCorners.css
113 ms
altaivita.ru accessibility score
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.
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.
altaivita.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
altaivita.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Altaivita.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 Altaivita.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.
altaivita.ru
Open Graph description is not detected on the main page of Altaivita. 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: