7.4 sec in total
475 ms
6.4 sec
495 ms
Click here to check amazing Royalstone content for Russia. Otherwise, check out these important facts you probably never knew about royalstone.ru
Интернет-магазин Royalstone: большой каталог керамической плитки, керамогранита, мозайки и другой керамики для дома. Прямые поставки из Европы, приемлемые цены, быстрая отгрузка и комплектование заказ...
Visit royalstone.ruWe analyzed Royalstone.ru page load time and found that the first response time was 475 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
royalstone.ru performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value10.9 s
0/100
25%
Value10.4 s
8/100
10%
Value5,560 ms
0/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
475 ms
895 ms
231 ms
291 ms
556 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 54% of them (33 requests) were addressed to the original Royalstone.ru, 10% (6 requests) were made to Leadback.ru and 7% (4 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source App.comagic.ru.
Page size can be reduced by 277.4 kB (50%)
557.3 kB
279.9 kB
In fact, the total size of Royalstone.ru main page is 557.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 254.8 kB which makes up the majority of the site volume.
Potential reduce by 215.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 215.1 kB or 84% of the original size.
Potential reduce by 3.5 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. Royalstone images are well optimized though.
Potential reduce by 58.8 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 58.8 kB or 68% of the original size.
Number of requests can be reduced by 23 (43%)
53
30
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalstone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
royalstone.ru
475 ms
www.royalstone.ru
895 ms
css
231 ms
colorbox.css
291 ms
cs.min.js
556 ms
share.js
481 ms
analytics.js
255 ms
fon11.gif
1102 ms
sprite.png
980 ms
xls-x.png
981 ms
contacts.png
1098 ms
ec261d9e4a2a87ea8239886f5ccd50c5.gif
1205 ms
9bda0cc49b793a94233a027a12ac383e.gif
1261 ms
d24afd71d9ceb8572eea49dfd25c44c0.jpg
1394 ms
a593e1518636f9a0ea71568593608b7c.jpg
1908 ms
5star.gif
1396 ms
4624c51d28749da569fd2463e3b32e7f.jpg
1701 ms
73c857ed16f7dceb8975c655cc411b5d.jpg
1432 ms
b-share-icon.png
1557 ms
pay.png
1700 ms
k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff
848 ms
RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff
969 ms
collect
831 ms
816 ms
leadback.js
1375 ms
watch.js
695 ms
rtrg
821 ms
fbevents.js
925 ms
1851 ms
2158 ms
2122 ms
b-share-form-button.png
239 ms
watch.js
12 ms
dlya_pola.jpg
733 ms
matovaya.jpg
855 ms
glyantsevaya.jpg
1102 ms
dlya_vannoy.jpg
934 ms
dlya_kukhni.jpg
1856 ms
strukturirovannaya.jpg
1982 ms
pod_derevo.jpg
1653 ms
pod_kamen.jpg
1104 ms
dlya_ulitsy.jpg
2218 ms
rtrg
926 ms
b-share-form-button_share__icon.png
292 ms
b-share-icon.png
379 ms
b-share-popup_down__tail.png
381 ms
2764 ms
collect
1553 ms
295 ms
collect
38 ms
jquery.cookie.js
1462 ms
ga-audiences
703 ms
widget_uuid.php
338 ms
widget_data.php
297 ms
_assets.min.js
269 ms
widget_event.php
273 ms
widget.php
570 ms
border1.png
170 ms
border2.png
194 ms
loading.gif
531 ms
info
421 ms
royalstone.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
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.
royalstone.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
royalstone.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
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 Royalstone.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 Royalstone.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.
royalstone.ru
Open Graph description is not detected on the main page of Royalstone. 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: