5.5 sec in total
313 ms
4.6 sec
544 ms
Visit brillante.ru now to see the best up-to-date Brillante content for Russia and also check out these interesting facts you probably never knew about brillante.ru
В интернет- магазине «Сокровищница Якутии» представлен ювелирный каталог с высококачественными изделиями из золота с использованием драгоценных и полудрагоценных камней, где покупателей ждет богатый а...
Visit brillante.ruWe analyzed Brillante.ru page load time and found that the first response time was 313 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
brillante.ru performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value7.0 s
6/100
25%
Value7.2 s
30/100
10%
Value220 ms
87/100
30%
Value0.019
100/100
15%
Value7.2 s
50/100
10%
313 ms
408 ms
400 ms
394 ms
395 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Brillante.ru, 51% (69 requests) were made to Brillante.ru.opt-images.1c-bitrix-cdn.ru and 24% (33 requests) were made to Brillante.ru.opt-css.1c-bitrix-cdn.ru. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Brillante.ru.opt-images.1c-bitrix-cdn.ru.
Page size can be reduced by 810.6 kB (13%)
6.3 MB
5.5 MB
In fact, the total size of Brillante.ru main page is 6.3 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. 70% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 132.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. 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 132.7 kB or 82% of the original size.
Potential reduce by 10.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. Brillante images are well optimized though.
Potential reduce by 571.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 571.5 kB or 69% of the original size.
Potential reduce by 95.8 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. Brillante.ru needs all CSS files to be minified and compressed as it can save up to 95.8 kB or 84% of the original size.
Number of requests can be reduced by 39 (30%)
132
93
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brillante. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
brillante.ru
313 ms
www.brillante.ru
408 ms
jquery-1.7.2.min.js
400 ms
kernel_main.css
394 ms
template_f5110cd16dc9847fbf01d88c8e25eeab.css
395 ms
kernel_main.js
652 ms
core_db.min.js
277 ms
core_frame_cache.min.js
278 ms
jquery-1.8.3.min.js
422 ms
cphttprequest.min.js
288 ms
template_83036684914edfe0b31d8710990812ec.js
421 ms
jquery.nivo.slider.js
421 ms
nivo-slider.css
420 ms
cusel-min-2.5.js
422 ms
jScrollPane.js
522 ms
jquery.mousewheel.js
527 ms
cusel.css
418 ms
jquery.jcarousel.min.js
532 ms
jquery.trackbar.js
536 ms
trackbar.css
419 ms
jquery.placeholder.min.js
548 ms
jquery.cookie.js
644 ms
jquery.fancybox.css
418 ms
jquery.fancybox.js
771 ms
jquery.cloud-carousel.1.0.5.min.js
774 ms
swfobject.js
774 ms
scripts.js
776 ms
ba.js
164 ms
d_client.js
285 ms
analytics.js
18 ms
bg2.jpg
143 ms
836022fc99edc2c1e60c0b70c6edd850.jpg
682 ms
captcha.php
249 ms
c1b91386b0501ff47d016bc5a7521a09.jpg
692 ms
ea6312086bb4b2004bcc28ac5a9c44d8.jpg
693 ms
6b3b43d6f104721fbb07f0df0de4a5eb.jpg
696 ms
c2f26b126dbc0b294c3bf8d61658a19c.jpg
703 ms
afa0b159bb854fc40fe3746dc029e3b1.jpg
704 ms
4f43ccf2ff60bd43d45979d042d8b917.jpg
802 ms
22c6ad56dceeccc9b59b59ad8e8a4c0e.jpg
1447 ms
617deb1084c2fa09d0e6fdbdebc46fb5.jpg
821 ms
efb2d4ae153e1e84e6f3e37d986ca85e.jpg
1077 ms
2cffeeb1d97c8f6b469e78430d604991.png
1393 ms
9e5025b0f171a8ad9eb5b9e91b71aebb.png
1391 ms
5654a22f65bc1543911249f605995384.jpg
921 ms
3af85479d16494ea11deb94e555c463a.jpg
946 ms
34dc97d13fb188e32716efb763495342.jpg
2014 ms
d538b5746417dba98d0a02d39e8e12d0.png
1574 ms
9f80e5289b6398e84a073a7a0369a6b3.png
1708 ms
4fda1b0b1bf5285428b0cbc355d32228.jpg
1648 ms
0fd792b8c9945d96644b600277a86064.gif
1521 ms
058b183e5bd4397012a05889f8ae6840.jpg
1570 ms
2e7002d49149bb46c45a59aec4cffee4.png
1909 ms
50b2378f8fd238e740feae9c83d2168a.jpg
1697 ms
50b2378f8fd238e740feae9c83d2168a.jpg
1699 ms
66310b1b14ae37e0a69488fcccf1a0dd.jpg
1777 ms
66310b1b14ae37e0a69488fcccf1a0dd.jpg
1821 ms
9e6b746ab902a17b7706bcf6d2000d6a.jpg
1824 ms
9e6b746ab902a17b7706bcf6d2000d6a.jpg
1833 ms
1ccd7e354b750545d357f2d39e1152ee.jpg
1905 ms
1ccd7e354b750545d357f2d39e1152ee.jpg
1958 ms
22c6ad56dceeccc9b59b59ad8e8a4c0e.jpg
1958 ms
617deb1084c2fa09d0e6fdbdebc46fb5.jpg
1962 ms
efb2d4ae153e1e84e6f3e37d986ca85e.jpg
2034 ms
2cffeeb1d97c8f6b469e78430d604991.png
2168 ms
9e5025b0f171a8ad9eb5b9e91b71aebb.png
2206 ms
06b79ef733ce987d2383e3b15a688ee6.png
2208 ms
3af85479d16494ea11deb94e555c463a.jpg
2093 ms
watch.js
472 ms
bot_bg.jpg
253 ms
bg_all.jpg
792 ms
collect
13 ms
auth_bg.png
122 ms
cart_bg.png
127 ms
content_bg.png
122 ms
sunduk.png
345 ms
bot_line.gif
240 ms
left_line.gif
253 ms
top_line.gif
254 ms
slider_right.jpg
349 ms
ugol_r_top.png
360 ms
ugol_r_bot.png
377 ms
slider_left.png
883 ms
find_btn.gif
466 ms
input_bg.gif
461 ms
input_btn.gif
466 ms
left_col_btn.gif
480 ms
special_bg.jpg
578 ms
special_foto_bg.gif
574 ms
bot_slider_bg.png
681 ms
botmenu_bg.png
581 ms
delimiter.png
687 ms
hit
253 ms
select-fon.png
640 ms
select.png
649 ms
slider_bot_arr.png
748 ms
sprite-1x.png
208 ms
bx_stat
210 ms
advert.gif
90 ms
1
93 ms
21c1b8d4ba51a369ae8e83de1093ac67.jpg
1459 ms
0fd792b8c9945d96644b600277a86064.gif
1480 ms
34dc97d13fb188e32716efb763495342.jpg
1537 ms
9f80e5289b6398e84a073a7a0369a6b3.png
1574 ms
5654a22f65bc1543911249f605995384.jpg
1600 ms
d538b5746417dba98d0a02d39e8e12d0.png
1731 ms
2e7002d49149bb46c45a59aec4cffee4.png
1667 ms
4fda1b0b1bf5285428b0cbc355d32228.jpg
1523 ms
058b183e5bd4397012a05889f8ae6840.jpg
1435 ms
fdb8242191af6748200862a70f5ad3a1.jpg
1443 ms
dd77748573f7d5252a2bd3db3c6cd7db.jpg
1488 ms
f1c333c0ee1137acb7f60b0c76e543fb.jpg
1080 ms
small.jpg
1090 ms
small2.jpg
1066 ms
small3.jpg
1040 ms
small4.jpg
1021 ms
82cceabb45dea006bdc81910109df0d0.png
1021 ms
cb97b1fa500bbd8746f4e5554765d435.png
960 ms
d358cffb7e1fb6f1a9a35b0cebb4e1b9.png
934 ms
686e6e1694045e8574ea2ec3a8cb1751.png
991 ms
a65f809ba2b26ccc2c79697371544889.png
985 ms
df4953fdc7b815a644078065c4d1c197.png
940 ms
be6f6db09bd4b04d400ee4bbb66d7ba4.png
900 ms
0d7d92f6e9ad3889d25c85cb75143677.png
909 ms
8cc5706b012ef03217b90e824b7ca837.png
918 ms
6c9d280376c7904f1118cc1c17ba5bfb.png
913 ms
ffaf301f32261e25b422b6e9f1cdeb99.png
913 ms
48ec16847826672fbdf9bfe529aaf4e2.png
883 ms
486e13556cd6f16e20a5263968021f4f.png
886 ms
937d1bf2bec55f197878a122dce47844.png
897 ms
cd1b567194997e0129b3f3dc25ab7a1a.png
862 ms
95ff7b74a9e42ccc7fcfd5232cbd198b.png
913 ms
87d84ab35b90872552ad6c8ee5ba2a56.png
854 ms
slider_btn.png
132 ms
www.brillante.ru
242 ms
brillante.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
brillante.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
brillante.ru SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brillante.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 Brillante.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.
brillante.ru
Open Graph description is not detected on the main page of Brillante. 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: