Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    53% of websites

br111.com

NameBright - Coming Soon

Page Load Speed

1.5 sec in total

First Response

211 ms

Resources Loaded

758 ms

Page Rendered

518 ms

About Website

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.com

Key Findings

We 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.

Performance Metrics

br111.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value12.8 s

3/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 342.6 kB (8%)

Content Size

4.1 MB

After Optimization

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.

HTML Optimization

-81%

Potential reduce by 100.3 kB

  • Original 123.2 kB
  • After minification 110.6 kB
  • After compression 23.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. 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.

Image Optimization

-2%

Potential reduce by 74.1 kB

  • Original 3.7 MB
  • After minification 3.6 MB

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.

JavaScript Optimization

-66%

Potential reduce by 137.8 kB

  • Original 209.5 kB
  • After minification 208.8 kB
  • After compression 71.7 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.

CSS Optimization

-82%

Potential reduce by 30.5 kB

  • Original 37.0 kB
  • After minification 32.6 kB
  • After compression 6.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.

Requests Breakdown

Number of requests can be reduced by 18 (22%)

Requests Now

83

After Optimization

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.

Accessibility Review

br111.com accessibility score

53

Accessibility Issues

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

High

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

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

High

Image elements do not have [alt] attributes

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

br111.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: