Tools & Wizards About Us
brics.it screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

brics.it

BRIC'S US

Page Load Speed

7.4 sec in total

First Response

166 ms

Resources Loaded

6.5 sec

Page Rendered

732 ms

brics.it screenshot

About Website

Visit brics.it now to see the best up-to-date BRIC S content for Germany and also check out these interesting facts you probably never knew about brics.it

Bric's Milano: Luxury Luggage & Travel Accessories Since 1952—The Finest in Italian Craftsmanship, Embodying Elegance & Sophistication in Every Suitcase.

Visit brics.it

Key Findings

We analyzed Brics.it page load time and found that the first response time was 166 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

brics.it performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

brics.it

166 ms

www.brics.it

483 ms

179 ms

icon

34 ms

stub.js

37 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Brics.it, 71% (25 requests) were made to Cdn.brics.it.filoblu.com and 6% (2 requests) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn.brics.it.filoblu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 481.0 kB (59%)

Content Size

813.2 kB

After Optimization

332.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Brics.it main page is 813.2 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. 15% of websites need less resources to load. HTML takes 549.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 476.4 kB

  • Original 549.6 kB
  • After minification 549.3 kB
  • After compression 73.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 476.4 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 3.3 kB

  • Original 56.0 kB
  • After minification 52.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. BRIC S images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 207.6 kB
  • After minification 207.6 kB
  • After compression 206.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 21 (68%)

Requests Now

31

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BRIC S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

brics.it

brics.it

166 ms

www.brics.it

www.brics.it

483 ms

179 ms

icon

icon

34 ms

stub.js

stub.js

37 ms

iubenda_cs.js

iubenda_cs.js

55 ms

logo.png

logo.png

70 ms

logo_lg.png

logo_lg.png

235 ms

Rectangle_9_1__1.jpg

Rectangle_9_1__1.jpg

219 ms

arrow2-left.svg

arrow2-left.svg

147 ms

arrow2-right.svg

arrow2-right.svg

233 ms

logo_lg-white.svg

logo_lg-white.svg

2511 ms

bundle.js

bundle.js

316 ms

3468.bundle.js

3468.bundle.js

213 ms

3169.bundle.js

3169.bundle.js

286 ms

6228.bundle.js

6228.bundle.js

303 ms

4974.bundle.js

4974.bundle.js

305 ms

612.bundle.js

612.bundle.js

308 ms

8120.bundle.js

8120.bundle.js

883 ms

5372.bundle.js

5372.bundle.js

876 ms

5085.bundle.js

5085.bundle.js

877 ms

6424.bundle.js

6424.bundle.js

587 ms

9629.bundle.js

9629.bundle.js

587 ms

2446.bundle.js

2446.bundle.js

588 ms

7587.bundle.js

7587.bundle.js

587 ms

9110.bundle.js

9110.bundle.js

646 ms

9382.bundle.js

9382.bundle.js

631 ms

961.bundle.js

961.bundle.js

721 ms

5868.bundle.js

5868.bundle.js

739 ms

4677.bundle.js

4677.bundle.js

808 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

0 ms

init

init

432 ms

api.js

api.js

342 ms

error.svg

error.svg

1836 ms

recaptcha__en.js

recaptcha__en.js

24 ms

Accessibility Review

brics.it accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Links do not have a discernible name

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.

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

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Best Practices

brics.it best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

brics.it SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brics.it can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Brics.it 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

brics.it

Open Graph data is detected on the main page of BRIC S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: