1.5 sec in total
211 ms
758 ms
518 ms
Welcome to br111.com homepage info - get ready to check Br 111 best content for United States right away, or after learning these important things about br111.com
Visit br111.comWe analyzed Br111.com page load time and found that the first response time was 211 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
br111.com performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value13.2 s
0/100
25%
Value12.8 s
3/100
10%
Value640 ms
47/100
30%
Value0.263
47/100
15%
Value12.9 s
13/100
10%
211 ms
6 ms
11 ms
10 ms
10 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 74% of them (63 requests) were addressed to the original Br111.com, 9% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (256 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 342.6 kB (8%)
4.1 MB
3.7 MB
In fact, the total size of Br111.com main page is 4.1 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. 80% 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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 100.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. 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 100.3 kB or 81% of the original size.
Potential reduce by 74.1 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. Br 111 images are well optimized though.
Potential reduce by 137.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 137.8 kB or 66% of the original size.
Potential reduce by 30.5 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. Br111.com needs all CSS files to be minified and compressed as it can save up to 30.5 kB or 82% of the original size.
Number of requests can be reduced by 18 (22%)
83
65
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Br 111. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
br111.com
211 ms
styles.css
6 ms
jquery-1.7.2.min.js
11 ms
jquery-ui-1.8.22.custom.min.js
10 ms
jquery.validate.min.js
10 ms
clear-inputs.js
8 ms
scripts.js
8 ms
Rhone_Oakp_swatch2-223x253.jpg
61 ms
all.js
176 ms
pinit.js
50 ms
widgets.js
49 ms
plusone.js
118 ms
Brittany_Oakp_swatch2-223x253.jpg
30 ms
Driftp_swatch2-223x253-223x253.jpg
31 ms
Chambordp_swatch2-223x253-223x253.jpg
33 ms
Normandy_Oakp_swatch2-223x253.jpg
32 ms
Vellum_Oakp_swatch2-223x253-223x253.jpg
34 ms
Kingsbridgep_swatch2-223x253-223x253.jpg
35 ms
nubuck_Oakp_swatch2-223x253-223x253.jpg
41 ms
avignon_oakp_swatch2-223x253.jpg
40 ms
bg-body.gif
28 ms
kravit-back.jpg
60 ms
shadow-01.png
31 ms
shadow-02.png
32 ms
bg-panel.gif
34 ms
logo2-br.png
36 ms
img-small-73.jpg
34 ms
img-small-79.jpg
39 ms
img-small-82.jpg
39 ms
img-small-83.jpg
42 ms
img-small-59.jpg
42 ms
img-small-102.jpg
42 ms
img-small-87.jpg
43 ms
sep-02.png
43 ms
img-small-91.jpg
48 ms
img-small-92.jpg
49 ms
img-small-93.jpg
49 ms
img-small-62.jpg
55 ms
img-small-95.jpg
53 ms
img-small-98.jpg
55 ms
img-small-99.jpg
56 ms
img-small-100.jpg
58 ms
sep-03.png
73 ms
arrow-02.png
71 ms
verl-o.jpg
93 ms
overlay.png
72 ms
sep-01.gif
73 ms
bg-number.png
74 ms
icon_shopping-cart.png
89 ms
ico-01.gif
91 ms
sample-br-new.jpg
95 ms
kravitz-top-banner1.jpg
94 ms
br-designer-banner.jpg
98 ms
home-oak-2.jpg
97 ms
engine-123.png
95 ms
din-regularitalic-webfont.woff
93 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
20 ms
dinregular-webfont.woff
74 ms
Gotham-Book.woff
70 ms
Gotham-Medium.woff
71 ms
gotham-light-webfont.woff
69 ms
NoticiaText-Italic-webfont.woff
69 ms
pinit_main.js
61 ms
logos-br-footer.gif
68 ms
img-05.png
66 ms
img-06.png
65 ms
img-07.png
64 ms
bbbarated.png
88 ms
logo3.png
63 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
19 ms
info.json
134 ms
cb=gapi.loaded_0
46 ms
cb=gapi.loaded_1
88 ms
fastbutton
136 ms
27 ms
postmessageRelay
42 ms
xd_arbiter.php
128 ms
xd_arbiter.php
256 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
22 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
69 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
43 ms
cb=gapi.loaded_0
9 ms
jot
88 ms
br111.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
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.
br111.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Br111.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Br111.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.
br111.com
Open Graph description is not detected on the main page of Br 111. 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: