3.3 sec in total
820 ms
2.2 sec
268 ms
Welcome to brillaro.de homepage info - get ready to check Brillaro best content for Germany right away, or after learning these important things about brillaro.de
This domain may be for sale!
Visit brillaro.deWe analyzed Brillaro.de page load time and found that the first response time was 820 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
brillaro.de performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.4 s
66/100
25%
Value3.2 s
92/100
10%
Value70 ms
99/100
30%
Value0.245
51/100
15%
Value3.5 s
92/100
10%
820 ms
289 ms
17 ms
509 ms
58 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 38% of them (43 requests) were addressed to the original Brillaro.de, 35% (39 requests) were made to D31wqjhd6b3ojv.cloudfront.net and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Brillaro.de.
Page size can be reduced by 764.7 kB (40%)
1.9 MB
1.1 MB
In fact, the total size of Brillaro.de main page is 1.9 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. 65% of websites need less resources to load. Images take 909.0 kB which makes up the majority of the site volume.
Potential reduce by 196.3 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 74.7 kB, which is 35% 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 196.3 kB or 92% of the original size.
Potential reduce by 4.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. Brillaro images are well optimized though.
Potential reduce by 364.3 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 364.3 kB or 66% of the original size.
Potential reduce by 200.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. Brillaro.de needs all CSS files to be minified and compressed as it can save up to 200.1 kB or 84% of the original size.
Number of requests can be reduced by 38 (38%)
101
63
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brillaro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
brillaro.de
820 ms
z1.css
289 ms
conversion.js
17 ms
c-de.js
509 ms
css
58 ms
j.php
65 ms
fbevents.js
190 ms
main-brillaro3.jpg
131 ms
logo-de.png
132 ms
front10400jsh.jpg
193 ms
front1039991y.jpg
331 ms
front10394rbr.jpg
216 ms
front10391ssh.jpg
330 ms
front10241mrr.jpg
330 ms
front10229ic3.jpg
330 ms
front5642jpg
331 ms
tv-ad-brillaro.jpg
351 ms
checkbox.png
415 ms
full_rim.jpg
420 ms
rimless.jpg
422 ms
half_rim.jpg
418 ms
wayfarer.jpg
430 ms
rectangular.jpg
432 ms
oval.jpg
507 ms
cat_eye.jpg
510 ms
round.jpg
511 ms
aviator.jpg
513 ms
transparent.gif
519 ms
side.gif
520 ms
front.gif
601 ms
try.gif
605 ms
payment.png
605 ms
us.png
609 ms
nl.png
616 ms
fr.png
610 ms
es.png
694 ms
cz.png
701 ms
it.png
699 ms
dc.js
121 ms
facet-size.png
651 ms
color-sprite.png
648 ms
webicon-facebook-m.png
660 ms
webicon-pinterest-m.png
734 ms
webicon-google-m.png
770 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
63 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
187 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
186 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
198 ms
foundation-icons.woff
701 ms
v.gif
55 ms
__utm.gif
105 ms
172 ms
161 ms
glyphicons-halflings-regular.woff
609 ms
cc8b6a16d74a2462a1be02e79a57fb95.js
209 ms
56d9fc8006b3bc138700002c.js
156 ms
webicon-twitter-m.png
617 ms
webicon-instagram-m.png
545 ms
Aspen-Vollrand-Wayfarer-9721front9721fnr.jpg
49 ms
Aspen-Vollrand-Wayfarer-9721threefourth9721jpa.jpg
44 ms
Wirt-Halbrand-Rechteckig-9836front9836k0g.jpg
42 ms
Wirt-Halbrand-Rechteckig-9836threefourth9836wu0.jpg
44 ms
Sigel-Vollrand-Schmetterling-10412front104122hs.jpg
42 ms
Sigel-Vollrand-Schmetterling-10412threefourth104120qm.jpg
43 ms
Faolan-Vollrand-Wayfarer-10398front1039802g.jpg
45 ms
Faolan-Vollrand-Wayfarer-10398threefourth10398nii.jpg
45 ms
Quyen-Vollrand-Wayfarer-9816front9816qwn.jpg
46 ms
Quyen-Vollrand-Wayfarer-9816threefourth9816z7z.jpg
48 ms
Amasa-Vollrand-Schmetterling-10391front10391ssh.jpg
47 ms
Amasa-Vollrand-Schmetterling-10391threefourth10391kf4.jpg
45 ms
Argyle-Vollrand-Wayfarer-10383front10383mnm.jpg
47 ms
Argyle-Vollrand-Wayfarer-10383threefourth10383dnn.jpg
48 ms
Peaine-Vollrand-Oval-10369front10369crw.jpg
56 ms
Peaine-Vollrand-Oval-10369threefourth10369tnw.jpg
50 ms
Rudyard-Vollrand-Schmetterling-10365front10365mmt.jpg
49 ms
Rudyard-Vollrand-Schmetterling-10365threefourth10365ma7.jpg
48 ms
Seneca-Vollrand-Schmetterling-10358threefourth10358ilj.jpg
56 ms
Fowler-Vollrand-Wayfarer-10356threefourth10356alb.jpg
55 ms
Bavaria-Vollrand-Wayfarer-10189threefourth10189fdq.jpg
57 ms
Stuttgart-Vollrand-Wayfarer-9969threefourth9969zoq.jpg
59 ms
Steyr-Vollrand-Oval-9948threefourth9948qaf.jpg
338 ms
Rayen-Vollrand-Wayfarer-9777threefourth977700p.jpg
59 ms
Annaberg-Vollrand-Wayfarer-9651threefourth9651wy8.jpg
58 ms
Ranell-Vollrand-Wayfarer-9729threefourth9729146.jpg
60 ms
Grimgerde-Randlos-Rechteckig-9469threefourth9469frx.jpg
59 ms
Daneil-Vollrand-Wayfarer-9868threefourth9868eql.jpg
61 ms
Faxon-Vollrand-Rechteckig-9855threefourth98550hn.jpg
60 ms
Tacita-Vollrand-Wayfarer-9700threefourth9700cpz.jpg
66 ms
Cortez-Vollrand-Rund-9006threefourth900606z.jpg
61 ms
Feisal-Halbrand-Wayfarer-9765threefourth9765ph0.jpg
61 ms
Walcott-Vollrand-Wayfarer-9764threefourth9764926.jpg
66 ms
Vitalis-Vollrand-Aviator-9756threefourth97568u6.jpg
66 ms
Bobby-Kinderbrille-Vollrand-Wayfarer-10147threefourth101472p9.jpg
67 ms
Monroe-Vollrand-Rechteckig-10307threefourth10307yj7.jpg
65 ms
webicon-youtube-m.png
559 ms
Laage-Vollrand-Oval-10094threefourth10094f4h.jpg
32 ms
Walenty-Randlos-Oval-10296threefourth10296i4m.jpg
30 ms
Kassel-Randlos-Rechteckig-10027threefourth10027kat.jpg
29 ms
45 ms
47 ms
tagjs
24 ms
51 ms
adsct
127 ms
Pug
85 ms
pixel
75 ms
47 ms
ncm
38 ms
cb
23 ms
sd
10 ms
cb
9 ms
tap.php
25 ms
cb
4 ms
brillaro.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
brillaro.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Uses deprecated APIs
brillaro.de 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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brillaro.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Brillaro.de 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.
brillaro.de
Open Graph description is not detected on the main page of Brillaro. 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: