4.8 sec in total
567 ms
4.1 sec
208 ms
Click here to check amazing Olvex content. Otherwise, check out these important facts you probably never knew about olvex.ru
Компания ООО «ОЛЬВЕКС-ДАЙМОНД» оказание услуг демонтажных работы методом алмазной резки. Техническое оснащение, профессиональная подготовка специалистов компании и опыт решения задач повышенной сложно...
Visit olvex.ruWe analyzed Olvex.ru page load time and found that the first response time was 567 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
olvex.ru performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value8.4 s
2/100
25%
Value7.2 s
30/100
10%
Value80 ms
99/100
30%
Value0.155
74/100
15%
Value10.4 s
24/100
10%
567 ms
1165 ms
130 ms
252 ms
634 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 95% of them (57 requests) were addressed to the original Olvex.ru, 3% (2 requests) were made to Counter.yadro.ru and 2% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Olvex.ru.
Page size can be reduced by 523.7 kB (44%)
1.2 MB
658.1 kB
In fact, the total size of Olvex.ru main page is 1.2 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. 30% of websites need less resources to load. Images take 552.9 kB which makes up the majority of the site volume.
Potential reduce by 21.7 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 3.5 kB, which is 12% 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 21.7 kB or 78% of the original size.
Potential reduce by 63.4 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, Olvex needs image optimization as it can save up to 63.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 381.4 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 381.4 kB or 72% of the original size.
Potential reduce by 57.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. Olvex.ru needs all CSS files to be minified and compressed as it can save up to 57.2 kB or 82% of the original size.
Number of requests can be reduced by 32 (58%)
55
23
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olvex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
olvex.ru
567 ms
www.olvex.ru
1165 ms
modal.css
130 ms
style.css
252 ms
mootools.js
634 ms
modal.js
254 ms
k2.js
139 ms
silverlight.js
256 ms
wmvplayer.js
411 ms
swfobject.js
276 ms
avreloaded.js
381 ms
system.css
392 ms
general.css
390 ms
template.css
429 ms
mainmenu.css
507 ms
sidenav.css
519 ms
feedback.css
520 ms
template.css
543 ms
homemenu.css
569 ms
jquery-1.3.2.min.js
919 ms
jquery-1.5.1.min.js
927 ms
jquery-ui-1.8.11.custom.min.js
1284 ms
jquery-ui-1.8.11.custom.css
809 ms
subnav-slide.js
705 ms
roll-down.js
757 ms
dialog.js
843 ms
tips.js
885 ms
tips.css
939 ms
k2.js
849 ms
bg-line.jpg
153 ms
bg.jpg
534 ms
header-bg.jpg
161 ms
logo.png
154 ms
menu-bg.jpg
150 ms
menu-left.jpg
157 ms
menu-right.jpg
283 ms
menu-separator.jpg
281 ms
search-bg.jpg
285 ms
order-btn.jpg
296 ms
home-menu-1-thmb.jpg
287 ms
home-menu-1-large.jpg
405 ms
home-menu-1-third.jpg
410 ms
home-menu-2-thmb.jpg
416 ms
home-menu-2-large.jpg
415 ms
home-menu-2-third.jpg
431 ms
home-menu-3-thmb.jpg
528 ms
home-menu-3-large.jpg
538 ms
home-menu-3-third.jpg
676 ms
home-menu-4-thmb.jpg
542 ms
home-menu-4-large.jpg
565 ms
home-menu-4-third.jpg
653 ms
home-menu-5-thmb.jpg
654 ms
home-menu-5-large.jpg
666 ms
home-menu-5-third.jpg
670 ms
bg-foot.png
1016 ms
logo-diagnost-over.png
776 ms
logo-diagnost-over-en.png
780 ms
hit
341 ms
watch.js
31 ms
hit
147 ms
olvex.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
Form elements do not have associated labels
Links do not have a discernible name
olvex.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
olvex.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 Olvex.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 Olvex.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.
olvex.ru
Open Graph description is not detected on the main page of Olvex. 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: