8.8 sec in total
318 ms
7.7 sec
767 ms
Visit brilia.com now to see the best up-to-date Brilia content for Brazil and also check out these interesting facts you probably never knew about brilia.com
Luz muda tudo.
Visit brilia.comWe analyzed Brilia.com page load time and found that the first response time was 318 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
brilia.com performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value31.1 s
0/100
25%
Value26.9 s
0/100
10%
Value2,280 ms
5/100
30%
Value0.672
8/100
15%
Value39.9 s
0/100
10%
318 ms
3671 ms
369 ms
245 ms
362 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 83% of them (110 requests) were addressed to the original Brilia.com, 3% (4 requests) were made to Scontent.cdninstagram.com and 2% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Brilia.com.
Page size can be reduced by 1.6 MB (19%)
8.5 MB
6.8 MB
In fact, the total size of Brilia.com main page is 8.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.9 MB which makes up the majority of the site volume.
Potential reduce by 97.4 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 42.8 kB, which is 39% 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 97.4 kB or 88% of the original size.
Potential reduce by 405.6 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. Brilia images are well optimized though.
Potential reduce by 990.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 990.8 kB or 77% of the original size.
Potential reduce by 131.1 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. Brilia.com needs all CSS files to be minified and compressed as it can save up to 131.1 kB or 84% of the original size.
Number of requests can be reduced by 47 (38%)
124
77
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brilia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
brilia.com
318 ms
www.brilia.com
3671 ms
font-awesome.min.css
369 ms
reset.css
245 ms
base.css
362 ms
lazyYT.css
245 ms
owl.carousel_.css
246 ms
owl.transitions.css
377 ms
carrossel.css
374 ms
layerslider.css
483 ms
d034ff2d06b65fd19e695ad5934c273c.css
592 ms
prototype.js
913 ms
ccard.js
485 ms
validation.js
602 ms
builder.js
485 ms
effects.js
720 ms
dragdrop.js
724 ms
controls.js
725 ms
slider.js
709 ms
js.js
720 ms
form.js
828 ms
menu.js
839 ms
translate.js
839 ms
cookies.js
844 ms
jquery-1.7.1-min.js
1088 ms
noconflict.js
947 ms
jquery.treeview.pack.js
959 ms
category_tree.js
960 ms
lightbox.js
966 ms
jquery.js
1146 ms
jquery-ui.js
1548 ms
css_browser_selector.js
1076 ms
jquery.placeholder.js
1076 ms
imgLiquid-min.js
1084 ms
greensock.js
1317 ms
layerslider.transitions.js
1196 ms
lazyYT.js
1204 ms
css
23 ms
colors.css
972 ms
owl.carousel.js
1032 ms
ig.js
1082 ms
init.js
984 ms
scripts-base.js
974 ms
scripts-control.js
1025 ms
menu.js
1072 ms
iframe_api
346 ms
analytics.js
224 ms
fbds.js
25 ms
sdk.js
219 ms
logo-brilia.png
305 ms
icon-menu.png
304 ms
social_header.png
296 ms
ico-search.png
294 ms
seta_prev.png
296 ms
seta_next.png
291 ms
light_gray_arrow.png
352 ms
arquiteto.png
444 ms
logo_expert.png
349 ms
arquiteto.png
360 ms
logo_intelligent.png
348 ms
arquiteto.png
350 ms
logo_smart.png
450 ms
icon_calculadora.png
460 ms
icon_led.png
455 ms
brilia_insight.png
453 ms
thumb_1.png
450 ms
blue-arrow.png
560 ms
pink_arrow.png
568 ms
ico_rev4_1.png
569 ms
icon-revista-3.png
570 ms
icon-revista-2.png
574 ms
icon-revista-1.png
576 ms
line_youtube.jpg
681 ms
blue_arrow.png
687 ms
light_blue_arrow_right.png
686 ms
light_blue_arrow.png
689 ms
thumb_youtube1.png
688 ms
thumb_youtube2.png
692 ms
thumb_youtube3.png
800 ms
red_arrow.png
801 ms
gray_arrow.png
802 ms
logo_brilha_footer.png
804 ms
12142325_929008230524815_773887866_n.jpg
286 ms
12132841_547561325407621_1071403000_n.jpg
138 ms
12070664_1746800735542965_1137897305_n.jpg
169 ms
12139632_853328544788863_1929504184_n.jpg
172 ms
bg_banner.jpg
622 ms
banner_5_1.jpg
749 ms
banner-expert_2.png
1947 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
129 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
156 ms
233 ms
collect
96 ms
Montserrat-Bold-webfont.woff
641 ms
Montserrat-Light-webfont.woff
648 ms
josefinsans-semibold-webfont.woff
761 ms
Montserrat-Regular-webfont.woff
648 ms
banner-intelligent_2.png
1121 ms
191 ms
banner-smart_2.png
1467 ms
xd_arbiter.php
61 ms
xd_arbiter.php
89 ms
www-widgetapi.js
122 ms
btn-lancamentos.jpg
714 ms
android-store.png
714 ms
ios-store.png
823 ms
brilia_banner_revista_site_1.png
1661 ms
img_facebook.jpg
1306 ms
collect
101 ms
social_footer.png
852 ms
hqdefault.jpg
36 ms
hqdefault.jpg
49 ms
hqdefault.jpg
57 ms
bulbo_12w_dimerizavel_400x400_5.png
1207 ms
vela_lisa_leitosa_400x400.png
1082 ms
vela_lisa_400x400_2.png
1199 ms
vela_lisa_400x400_3.png
1319 ms
vela_chama_filamento_400x400.png
1318 ms
sku430422_1.png
1225 ms
sku430576.png
1326 ms
fita_led_multitemperatura_de_cor_2m_400x400.png
1327 ms
ar70_refletora_400x400.png
1564 ms
bulbo_autodimerizavel_400x400.png
1331 ms
430675_par-20_produto.png
1438 ms
SKU430507_6.png
1337 ms
projetor_10w.png
1341 ms
projetores_20w.png
1449 ms
projetor_30w.png
1448 ms
projetor_50w.png
1448 ms
btn-youtube.png
1456 ms
e58144676d363bdf3ab07e371ea4d90f.css
122 ms
63 ms
xd_arbiter.php
10 ms
brilia.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
[aria-hidden="true"] elements contain focusable descendents
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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
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.
brilia.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
brilia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brilia.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Brilia.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.
brilia.com
Open Graph description is not detected on the main page of Brilia. 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: