4.4 sec in total
754 ms
3.4 sec
223 ms
Click here to check amazing Rafine content for Russia. Otherwise, check out these important facts you probably never knew about rafine.ru
Интернет-магазин уходовой органической косметики. Крема, скрабы
Visit rafine.ruWe analyzed Rafine.ru page load time and found that the first response time was 754 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
rafine.ru performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value4.5 s
37/100
25%
Value7.1 s
32/100
10%
Value730 ms
41/100
30%
Value0.08
94/100
15%
Value9.3 s
31/100
10%
754 ms
238 ms
365 ms
246 ms
385 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 85% of them (69 requests) were addressed to the original Rafine.ru, 9% (7 requests) were made to Cp.onicon.ru and 4% (3 requests) were made to Counter.megagroup.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Rafine.ru.
Page size can be reduced by 1.4 MB (59%)
2.4 MB
998.3 kB
In fact, the total size of Rafine.ru main page is 2.4 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 258.8 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 36.5 kB, which is 13% 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 258.8 kB or 92% of the original size.
Potential reduce by 7.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. Rafine images are well optimized though.
Potential reduce by 763.2 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 763.2 kB or 71% of the original size.
Potential reduce by 392.7 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. Rafine.ru needs all CSS files to be minified and compressed as it can save up to 392.7 kB or 85% of the original size.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rafine. 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 9 to 1 for CSS and as a result speed up the page load time.
rafine.ru
754 ms
styles_articles_tpl.css
238 ms
jquery.min.js
365 ms
highslide.min.css
246 ms
highslide-full.packed.js
385 ms
flowplayer-3.2.9.min.js
247 ms
calendar.css
248 ms
ru.js
356 ms
cookie.js
383 ms
widgets.js
390 ms
calendar.packed.js
391 ms
feedback.factory.min.js
476 ms
theme.less.css
485 ms
printme.js
498 ms
tpl.js
513 ms
baron.min.js
510 ms
shop2.2.js
633 ms
s3.eventable.js
596 ms
s3.math.js
604 ms
s3.menu.allin.js
604 ms
photoswipe.css
641 ms
default_skin.css
643 ms
photoswipe.min.js
717 ms
photoswipe_ui_default.min.js
724 ms
jquery.formstyler.min.js
726 ms
nouislider.min.js
757 ms
owl.carousel.min.js
761 ms
jquery.bxslider.min.js
764 ms
sly.min.js
838 ms
slick.min.js
844 ms
jquery.responsivetabs.min.js
848 ms
s3.includeform.js
879 ms
tap_file.js
880 ms
main.js
882 ms
styles.scss.css
1082 ms
gr-form.js
860 ms
flexfix.js
860 ms
logo.png
126 ms
1.jpg
446 ms
1.jpg
127 ms
97.jpg
445 ms
2.jpg
548 ms
2.jpg
441 ms
%D0%90%D0%BD%D1%82%D0%B8%D1%86%D0%B5%D0%BB%D0%BB%D1%8E%D0%BB%D0%B8%D1%82%D0%BD%D1%8B%D0%B9_%D0%BA%D1%80%D0%B5%D0%BC.jpg
440 ms
%D0%9A%D1%80%D0%B5%D0%BC_%D0%B4%D0%BB%D1%8F_%D0%BC%D0%B0%D1%81%D1%81%D0%B0%D0%B6%D0%B0.jpg
444 ms
%D0%9A%D1%80%D0%B5%D0%BC_%D0%BE%D1%82_%D1%80%D0%B0%D1%81%D1%82%D1%8F%D0%B6%D0%B5%D0%BA.jpg
446 ms
%D0%9A%D1%80%D0%B5%D0%BC_%D0%BB%D0%B8%D1%84%D1%82%D0%B8%D0%BD%D0%B3_%D0%B4%D0%BB%D1%8F_%D1%82%D0%B5%D0%BB%D0%B0.jpg
446 ms
%D0%9A%D1%80%D0%B5%D0%BC_%D0%BE%D0%BC%D0%BE%D0%BB%D0%B0%D0%B6%D0%B8%D0%B2%D0%B0%D1%8E%D1%89%D0%B8%D0%B9.jpg
447 ms
%D0%9A%D1%80%D0%B5%D0%BC-%D0%BC%D0%B0%D1%81%D0%BA%D0%B0_%D0%B4%D0%BB%D1%8F_%D0%B2%D0%BE%D0%BB%D0%BE%D1%81.jpg
447 ms
%D0%A1%D0%BA%D1%80%D0%B0%D0%B1_%D0%BB%D0%B8%D1%84%D1%82%D0%B8%D0%BD%D0%B3.jpg
493 ms
%D0%A8%D0%B0%D0%BC%D0%BF%D1%83%D0%BD%D0%B5%D0%B2%D0%BE%D0%B5_%D0%BC%D1%8B%D0%BB%D0%BE_%D0%B4%D0%BB%D1%8F_%D1%81%D1%83%D1%85%D0%B8%D1%85_%D0%B2%D0%BE%D0%BB%D0%BE%D1%81_%D1%81_%D0%AD%D0%9C_%D0%98%D0%BB%D0%B0%D0%BD%D0%B3-%D0%B8%D0%BB%D0%B0%D0%BD%D0%B3%D0%B0.jpg
508 ms
%D0%A1%D0%BA%D1%80%D0%B0%D0%B1_%D0%B0%D0%BD%D1%82%D0%B8%D1%86%D0%B5%D0%BB%D0%BB%D1%8E%D0%BB%D0%B8%D1%82%D0%BD%D1%8B%D0%B9_%D0%B0%D0%BF%D0%B5%D0%BB%D1%8C%D1%81%D0%B8%D0%BD_%D0%B8_%D0%BA%D0%BE%D1%80%D0%B8%D1%86%D0%B0.jpg
509 ms
%D0%A1%D0%BA%D1%80%D0%B0%D0%B1_%D0%B0%D0%BD%D1%82%D0%B8%D1%86%D0%B5%D0%BB%D0%BB%D1%8E%D0%BB%D0%B8%D1%82%D0%BD%D1%8B%D0%B9_%D0%9B%D0%B8%D0%BC%D0%BE%D0%BD.jpg
546 ms
no_image.png
572 ms
fon-bg5.png
409 ms
1.jpg
542 ms
97.jpg
687 ms
2.jpg
574 ms
logo.png
455 ms
ico1.png
454 ms
ico2.png
536 ms
ico3.png
588 ms
ico4.png
590 ms
hit
277 ms
roboto_condensed-r.woff
625 ms
roboto_condensed-l.woff
650 ms
roboto_condensed-b.woff
663 ms
simple_loader.js
533 ms
loader.js
209 ms
gr-form.less.css
493 ms
includeform.js
507 ms
api.js
112 ms
hit
137 ms
b8f949ee335ae8374551d3dbf1a41a1a.js
103 ms
bootstrap.min.js
199 ms
gr-form
148 ms
bootstrap.min.js
94 ms
onicon.site.min.css
98 ms
onicon.site.min.js
189 ms
onicon.site.min.css
191 ms
onicon.site.min.js
561 ms
rafine.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
Form elements do not have associated labels
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.
rafine.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
rafine.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Rafine.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 Rafine.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.
rafine.ru
Open Graph description is not detected on the main page of Rafine. 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: