8.5 sec in total
329 ms
8 sec
249 ms
Welcome to razormen.ru homepage info - get ready to check Razormen best content for Russia right away, or after learning these important things about razormen.ru
интернет-магазин опасных бритв, помазков, станков и аксессуаров для бритья
Visit razormen.ruWe analyzed Razormen.ru page load time and found that the first response time was 329 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
razormen.ru performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value7.7 s
3/100
25%
Value12.8 s
2/100
10%
Value1,420 ms
15/100
30%
Value0.23
54/100
15%
Value16.1 s
6/100
10%
329 ms
412 ms
147 ms
440 ms
287 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 10% of them (10 requests) were addressed to the original Razormen.ru, 39% (39 requests) were made to Assets3.insales.ru and 27% (27 requests) were made to Web.redhelper.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Assets3.insales.ru.
Page size can be reduced by 747.7 kB (36%)
2.1 MB
1.3 MB
In fact, the total size of Razormen.ru main page is 2.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. 60% of websites need less resources to load. Images take 967.5 kB which makes up the majority of the site volume.
Potential reduce by 46.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 6.5 kB, which is 11% 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 46.2 kB or 77% of the original size.
Potential reduce by 48.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. Razormen images are well optimized though.
Potential reduce by 187.5 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 187.5 kB or 61% of the original size.
Potential reduce by 465.9 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. Razormen.ru needs all CSS files to be minified and compressed as it can save up to 465.9 kB or 62% of the original size.
Number of requests can be reduced by 67 (70%)
96
29
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Razormen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
razormen.ru
329 ms
www.razormen.ru
412 ms
insales_counter.js
147 ms
stylesheet.css
440 ms
superfish.css
287 ms
slideshow.css
293 ms
jquery.rating.css
323 ms
jquery.fancybox.css
150 ms
jquery.min.js
12 ms
jquery.cookie.js
145 ms
common_ru.js
145 ms
cart.js
146 ms
site.js
328 ms
jcarousel.js
296 ms
nivoslider.js
460 ms
tabs.js
418 ms
superfish.js
458 ms
jquery.hoverIntent.js
460 ms
common.js
463 ms
script.js
1733 ms
jquery.MetaData.js
559 ms
jquery.rating.pack.js
628 ms
jquery.mousewheel.pack.js
147 ms
jquery.fancybox.pack.js
275 ms
widget.js
605 ms
main.js
788 ms
referer_code.js
278 ms
counter.insales.ru
408 ms
medium_IMG_1541.JPG
400 ms
medium_TR-001.jpg
692 ms
bg-loaded.png
543 ms
loaded_logo.png
295 ms
loaded_main_image_1.jpg
626 ms
loaded_main_image_2.jpg
743 ms
loaded_main_image_3.jpg
665 ms
loaded_banner1.jpg
313 ms
loaded_banner2.jpg
817 ms
loaded_image1.jpg
591 ms
loaded_image2.jpg
989 ms
loaded_image3.jpg
1521 ms
medium_IMG_1403.JPG
442 ms
medium_Image00021.jpg
434 ms
medium_IMG_1555.JPG
449 ms
ga.js
11 ms
7XgZbApGvJY
111 ms
shop-cart-button.svg.png
1756 ms
button-bg.svg.png
775 ms
trans.png
869 ms
left-bg.svg.png
930 ms
right-bg.svg.png
956 ms
separator.png
1031 ms
box-bg.gif
1069 ms
left-bg1.svg.png
1100 ms
vert-line.gif
1125 ms
line-border.png
1211 ms
loaded_footer_bg.png
2145 ms
footer-heading.svg.png
1231 ms
footer-marker.png
1291 ms
paggs-bg.png
1320 ms
paggs.svg.png
1675 ms
__utm.gif
11 ms
www-embed-player-vflfNyN_r.css
30 ms
www-embed-player.js
57 ms
base.js
97 ms
watch.js
465 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
ad_status.js
37 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
38 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
38 ms
advert.gif
91 ms
1
98 ms
main.js
1136 ms
start
387 ms
main.js
632 ms
jquery.min.js
759 ms
jquery-new.min.js
775 ms
14777
389 ms
common.css
887 ms
554786
256 ms
connector.html
152 ms
connector.html
215 ms
293d1bb3-669b-4607-ad31-8e4b14757504.png
368 ms
__utm.gif
14 ms
27266495
100 ms
mac.css
131 ms
connector-frame.css
709 ms
connector.js
746 ms
Ava_default.png
677 ms
381 ms
main.js
762 ms
mail_large.png
131 ms
icon-close.png
130 ms
warning-top.png
126 ms
warning-mid.png
131 ms
warning-bottom.png
146 ms
copyright-bottom-p1.png
251 ms
copyright-bottom-p3.png
256 ms
v42r9LwwxUv8H9mNOJwAAAAFVgBmSAAA=
3 ms
connector-popup.css
476 ms
flags.png
307 ms
mac.css
128 ms
razormen.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
razormen.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
Missing source maps for large first-party JavaScript
razormen.ru SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Razormen.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Razormen.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.
razormen.ru
Open Graph description is not detected on the main page of Razormen. 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: