8.3 sec in total
69 ms
8 sec
201 ms
Visit brillianteers.com now to see the best up-to-date Brillianteers content for India and also check out these interesting facts you probably never knew about brillianteers.com
"I've made multiple orders from this company & they exceeded my expectations every time.". Free Shipping | 30 Day Return Policy | Appraisal Certificate | Lifetime Warranty.
Visit brillianteers.comWe analyzed Brillianteers.com page load time and found that the first response time was 69 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.
brillianteers.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value11.0 s
0/100
25%
Value6.3 s
41/100
10%
Value1,690 ms
11/100
30%
Value0.941
3/100
15%
Value16.0 s
6/100
10%
69 ms
1316 ms
109 ms
75 ms
79 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 64% of them (112 requests) were addressed to the original Brillianteers.com, 3% (6 requests) were made to Api1.shoptimally.com and 3% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source Staticw2.yotpo.com.
Page size can be reduced by 1.4 MB (60%)
2.4 MB
942.0 kB
In fact, the total size of Brillianteers.com 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 277.0 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 55.1 kB, which is 17% 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 277.0 kB or 84% of the original size.
Potential reduce by 30.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. Brillianteers images are well optimized though.
Potential reduce by 842.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 842.4 kB or 71% of the original size.
Potential reduce by 291.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. Brillianteers.com needs all CSS files to be minified and compressed as it can save up to 291.7 kB or 87% of the original size.
Number of requests can be reduced by 89 (55%)
162
73
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brillianteers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
brillianteers.com
69 ms
www.brillianteers.com
1316 ms
styles.css
109 ms
widgets.css
75 ms
category.css
79 ms
amshopby.css
77 ms
brands.css
75 ms
ultra-slideshow.css
126 ms
generic-nav.css
121 ms
itemgrid.css
120 ms
accordion.css
126 ms
ultra-megamenu.css
143 ms
wide.css
146 ms
reveal.css
146 ms
styles-infortis.css
150 ms
jquery.css
152 ms
generic-cck.css
170 ms
dropdown.css
177 ms
icons.css
179 ms
itemslider.css
180 ms
tabs.css
187 ms
icons-theme.css
186 ms
icons-social.css
202 ms
common.css
210 ms
design_brillianteersultimo.css
213 ms
override-theme.css
214 ms
grid12.css
222 ms
grid_brillianteersultimo.css
223 ms
layout_brillianteersultimo.css
237 ms
custom.css
245 ms
f9ae548c6d70dd7869e068b011eecb9f.js
376 ms
3219930069.js
33 ms
css
24 ms
shoptimally.min.js
3 ms
pinit.js
7 ms
conversion.js
14 ms
css
14 ms
css
22 ms
css
24 ms
analytics.js
5544 ms
widget.js
5552 ms
fbds.js
5551 ms
event
57 ms
inspectlet.js
54 ms
ic_lock.png
84 ms
logo.png
83 ms
sprite.png
83 ms
13535-r.gif
201 ms
best-sellers-sqr.jpg
82 ms
nav-value.jpg
82 ms
diamond-earrings-banner.jpg
77 ms
diamond-sets-banner.jpg
93 ms
diamond-bands-banner.jpg
93 ms
diamond-pendants.jpg
88 ms
swarovski-banner.jpg
89 ms
swarovski-set-banner.jpg
123 ms
swarovski-bracelet-banner.jpg
121 ms
swarovski-earrings.jpg
131 ms
red-swarovski-banner.jpg
132 ms
office_map_sm.jpg
171 ms
map.jpg
171 ms
banner4b.jpg
243 ms
cat1.jpg
181 ms
cat2.jpg
181 ms
cat3.jpg
182 ms
cat4.jpg
205 ms
cat9.jpg
205 ms
cat5.jpg
224 ms
0151bw1.jpg
222 ms
0006ww1.jpg
223 ms
0006hw1.jpg
243 ms
0152by1.jpg
244 ms
0132ww1.jpg
255 ms
0132hw1.jpg
254 ms
0040ww1.jpg
254 ms
0040bw1.jpg
264 ms
0210ww1.jpg
280 ms
0210ww2.jpg
282 ms
0183ww1.jpg
300 ms
0183hw1.jpg
302 ms
0092ww1.jpg
303 ms
collect
44 ms
collect
80 ms
widget.css
98 ms
40 ms
WZDISdyil4HsmirlOdBRFInF5uFdDttMLvmWuJdhhgs.ttf
32 ms
get_id
211 ms
get_adapters
30 ms
3007128888
26 ms
0092wy2.jpg
237 ms
0147ww1.jpg
261 ms
0147hw1.jpg
262 ms
0163ww1.jpg
264 ms
0202ww1.jpg
262 ms
0202hw1.jpg
268 ms
0307ww1.jpg
262 ms
0307ww4.jpg
287 ms
0189ww1.jpg
285 ms
0189ww2.jpg
286 ms
ga-audiences
68 ms
0305ww1.jpg
290 ms
0305ww4.jpg
289 ms
0303ww1.jpg
280 ms
0303ww4.jpg
310 ms
css
12 ms
pixel.gif
274 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
12 ms
bottom_logos.gif
272 ms
lock.png
262 ms
logo.png
263 ms
info.png
262 ms
Ogj-3NtjunoTAuueCcfSTQ.ttf
6 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
13 ms
one.png
267 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
16 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
4 ms
two.png
267 ms
three.png
249 ms
four.png
249 ms
script.js
129 ms
a6c5941b-b19b-454b-a061-90e5b655c229.js
172 ms
31 ms
phone.png
233 ms
email.png
231 ms
promo.png
324 ms
fmrs-1.0.js
115 ms
delivery.png
321 ms
pinit_main.js
36 ms
amazon-feedback.png
313 ms
ebay-feedback.png
313 ms
payment.gif
312 ms
send_user_data
59 ms
get_features_list
22 ms
ic_blog.png
303 ms
29 ms
for-chat.png
289 ms
for-bag.png
287 ms
link-separator.png
267 ms
arrow-dropdown-w.png
266 ms
trust_trans.png
264 ms
dots_v_gray.gif
274 ms
shadow2.png
263 ms
socials.png
269 ms
modal-gloss.png
261 ms
bullet.png
271 ms
bullet.png
269 ms
jquery.FMRSBox.js
78 ms
FMRSBox.css
134 ms
FMRSBoxCaller.js
107 ms
runtime.2.2.5.js
11 ms
submit
45 ms
blank.gif
19 ms
56922db40443d959f700002b.js
56 ms
loader.gif
46 ms
visit_url
104 ms
i
24 ms
batch
110 ms
slider-arrows.png
61 ms
opener-w.png
116 ms
tagjs
15 ms
59 ms
livechat_green_bottom_en.png
91 ms
adsct
125 ms
Pug
98 ms
pixel
92 ms
sign_in_url
34 ms
print.css
69 ms
ncm
23 ms
sd
10 ms
cb
14 ms
cb
4 ms
tap.php
27 ms
cb
5 ms
3 ms
brillianteers.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
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
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
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
brillianteers.com 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
brillianteers.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brillianteers.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Brillianteers.com 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.
brillianteers.com
Open Graph description is not detected on the main page of Brillianteers. 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: