9.6 sec in total
3.1 sec
6.3 sec
229 ms
Click here to check amazing Brilio content. Otherwise, check out these important facts you probably never knew about brilio.ro
Default Description
Visit brilio.roWe analyzed Brilio.ro page load time and found that the first response time was 3.1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
brilio.ro performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value21.8 s
0/100
25%
Value15.7 s
0/100
10%
Value1,480 ms
14/100
30%
Value0.426
22/100
15%
Value36.9 s
0/100
10%
3099 ms
630 ms
760 ms
439 ms
140 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 81% of them (46 requests) were addressed to the original Brilio.ro, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Brilio.ro.
Page size can be reduced by 190.7 kB (23%)
817.7 kB
627.1 kB
In fact, the total size of Brilio.ro main page is 817.7 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. 25% of websites need less resources to load. Images take 707.0 kB which makes up the majority of the site volume.
Potential reduce by 44.2 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 44.2 kB or 78% of the original size.
Potential reduce by 112.8 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. Obviously, Brilio needs image optimization as it can save up to 112.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 33.6 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 33.6 kB or 62% of the original size.
Number of requests can be reduced by 11 (20%)
56
45
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brilio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
www.brilio.ro
3099 ms
widgets.css
630 ms
lightbox.js
760 ms
all.js
439 ms
bkg_bodyV2.gif
140 ms
logo.png
156 ms
get_flash_player.gif
141 ms
bic1g04_fata.jpg
281 ms
prelucrate03-finisata.jpg
274 ms
bcc5a03.jpg
282 ms
bcc2a03_3.jpg
381 ms
bcc3g04_2.jpg
381 ms
stanga.gif
402 ms
dreapta.gif
480 ms
prelucrate03-finisata.jpg
481 ms
bip1sg06_fata_3.jpg
480 ms
bcc5a03.jpg
504 ms
bcc2a03_3.jpg
506 ms
masina.jpg
540 ms
brilio.jpg
609 ms
icon_carduri.png
735 ms
chestionar.gif
613 ms
fidelizare.gif
635 ms
ghidul.gif
635 ms
tel-verde_2.png
917 ms
brilio-produs-in-ro.jpg
1109 ms
10zile.jpg
883 ms
logo-mic.jpg
889 ms
brilio-mic.jpg
891 ms
ga.js
69 ms
bkg_page.png
1614 ms
bkg_header_v3.gif
1009 ms
background_search.png
1005 ms
bkg_nav0.jpg
993 ms
bkg_nav1.gif
1022 ms
bkg_nav2.gif
1136 ms
filtre.gif
1388 ms
tip.gif
1144 ms
piatra.gif
1157 ms
culoare.gif
1208 ms
bkg_main1.gif
1358 ms
__utm.gif
33 ms
bkg_main2.png
1178 ms
132 ms
bara_cupoane.jpg
1304 ms
xd_arbiter.php
480 ms
seal.min.js
199 ms
envelop.png
1193 ms
like.php
124 ms
i_rss.gif
1168 ms
loading.gif
1237 ms
closelabel.gif
1284 ms
xd_arbiter.php
410 ms
qeKvIRsJabD.js
481 ms
LVx-xkvaJ0b.png
540 ms
print.css
138 ms
144 ms
brilio.ro 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
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.
brilio.ro 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
brilio.ro 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
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brilio.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Brilio.ro 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.
brilio.ro
Open Graph description is not detected on the main page of Brilio. 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: