Tools & Wizards About Us
biffi.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

biffi.com

Biffi Boutiques

Page Load Speed

3.7 sec in total

First Response

220 ms

Resources Loaded

3.1 sec

Page Rendered

357 ms

biffi.com screenshot

About Website

Welcome to biffi.com homepage info - get ready to check Biffi best content for Japan right away, or after learning these important things about biffi.com

On Biffi.com, discover a refined online shopping experience, featuring a curated selection of clothing, bags, and accessories from the most prestigious fashion houses and the most innovative designers...

Visit biffi.com

Key Findings

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

Performance Metrics

biffi.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value5,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.076

2/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

220 ms

uc.js

217 ms

cd.js

977 ms

klaviyo.js

24 ms

klaviyo.js

135 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 85% of them (100 requests) were addressed to the original Biffi.com, 4% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (977 ms) relates to the external source Consent.cookiebot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.4 kB (69%)

Content Size

496.5 kB

After Optimization

154.1 kB

  • HTML
  • JavaScript

In fact, the total size of Biffi.com main page is 496.5 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. 70% of websites need less resources to load. HTML takes 304.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 243.0 kB

  • Original 304.4 kB
  • After minification 296.4 kB
  • After compression 61.4 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 243.0 kB or 80% of the original size.

JavaScript Optimization

-52%

Potential reduce by 99.4 kB

  • Original 192.1 kB
  • After minification 192.1 kB
  • After compression 92.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 99.4 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 101 (93%)

Requests Now

109

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

220 ms

uc.js

uc.js

217 ms

cd.js

cd.js

977 ms

klaviyo.js

klaviyo.js

24 ms

klaviyo.js

klaviyo.js

135 ms

ca688a99cbfe735a1370.css

ca688a99cbfe735a1370.css

275 ms

106093e77157659c416a.css

106093e77157659c416a.css

290 ms

24498a1d235021fb1286.css

24498a1d235021fb1286.css

247 ms

5218abfcbaa75b1eca04.css

5218abfcbaa75b1eca04.css

245 ms

18af23be6f06696bcfa9.css

18af23be6f06696bcfa9.css

327 ms

6745a6e1af24caadb903.css

6745a6e1af24caadb903.css

258 ms

f3416d646037f6a7cfbc.css

f3416d646037f6a7cfbc.css

334 ms

da7e991adbf8c33e5e26.css

da7e991adbf8c33e5e26.css

291 ms

a2fcabb7e1c2694a6972.css

a2fcabb7e1c2694a6972.css

332 ms

0da9b4e16e20dbb5f5d3.css

0da9b4e16e20dbb5f5d3.css

346 ms

8449cd515780fc423ed6.css

8449cd515780fc423ed6.css

363 ms

ddf44030245d757d1de2.css

ddf44030245d757d1de2.css

360 ms

e11fe4813f5fc45d9875.css

e11fe4813f5fc45d9875.css

398 ms

6096f94ea1fc45ed5cea.css

6096f94ea1fc45ed5cea.css

400 ms

5afa96db4a3977a516c3.css

5afa96db4a3977a516c3.css

401 ms

e131975d1ecb47b97e51.css

e131975d1ecb47b97e51.css

463 ms

3a24a72471ccabc8d59c.css

3a24a72471ccabc8d59c.css

433 ms

5543a6026d0a44797edd.css

5543a6026d0a44797edd.css

431 ms

bfdc1d54505de47f3bee.css

bfdc1d54505de47f3bee.css

510 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

22 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

20 ms

runtime.797d0919a947775d46ef.js

runtime.797d0919a947775d46ef.js

3 ms

sharedUtils.9a6c7cead1cefc328bca.js

sharedUtils.9a6c7cead1cefc328bca.js

13 ms

1bb8d6c9c0d6f831952c.js

1bb8d6c9c0d6f831952c.js

411 ms

bbcbfec246743b02dae0.js

bbcbfec246743b02dae0.js

411 ms

01e4bc644fbc88349c40.js

01e4bc644fbc88349c40.js

445 ms

e0c72e08e6e628559b31.js

e0c72e08e6e628559b31.js

445 ms

c5c60f5c2c0393d7c2e4.js

c5c60f5c2c0393d7c2e4.js

515 ms

80623616034194253894.js

80623616034194253894.js

635 ms

9150b56bd0c60e44ad72.js

9150b56bd0c60e44ad72.js

526 ms

1408bcaaee21b60651d7.js

1408bcaaee21b60651d7.js

515 ms

7613ce686ee24789b1d1.js

7613ce686ee24789b1d1.js

517 ms

a8b43d73b479ef3e320c.js

a8b43d73b479ef3e320c.js

525 ms

e4b935e7cfc7370d1a41.js

e4b935e7cfc7370d1a41.js

553 ms

a16a7f777e8d4c78f8d1.js

a16a7f777e8d4c78f8d1.js

587 ms

1f5520dc8a3aea54bdf7.js

1f5520dc8a3aea54bdf7.js

632 ms

2a9800353edab6b527d3.js

2a9800353edab6b527d3.js

643 ms

29e633a17a84e324836a.js

29e633a17a84e324836a.js

648 ms

6678ceae31c26f35476d.js

6678ceae31c26f35476d.js

621 ms

gtm.js

gtm.js

82 ms

css2

css2

55 ms

1674663776357.png

1674663776357.png

39 ms

1674663856578.png

1674663856578.png

41 ms

1674663725271.png

1674663725271.png

39 ms

39996aebaf8b22523385.js

39996aebaf8b22523385.js

625 ms

fcbf2edc2adb804efc6f.js

fcbf2edc2adb804efc6f.js

511 ms

713223b4343cb185fe6a.js

713223b4343cb185fe6a.js

606 ms

00452ece6fae828a28c1.js

00452ece6fae828a28c1.js

511 ms

20686e3da104c5057250.js

20686e3da104c5057250.js

544 ms

ebf66ca5d904653f6c7a.js

ebf66ca5d904653f6c7a.js

561 ms

9d4d73f32441b30fd015.js

9d4d73f32441b30fd015.js

536 ms

fcb50cc551abe56a3887.js

fcb50cc551abe56a3887.js

506 ms

b81ef7767fc4406a92e9.js

b81ef7767fc4406a92e9.js

549 ms

3b55e7f88e945d342da4.js

3b55e7f88e945d342da4.js

604 ms

db1e279cf0c1fb0ba183.js

db1e279cf0c1fb0ba183.js

550 ms

eb22c3ac3d8a5847897b.js

eb22c3ac3d8a5847897b.js

570 ms

3b0a2b629975e485ed83.js

3b0a2b629975e485ed83.js

605 ms

0f45ccdc2a3c85088369.js

0f45ccdc2a3c85088369.js

567 ms

d16c32abef725d410e81.js

d16c32abef725d410e81.js

627 ms

87d97f98e60364bb4b68.js

87d97f98e60364bb4b68.js

566 ms

b804230d96368f37e585.js

b804230d96368f37e585.js

615 ms

20b8385fe4b8ab3ce3c9.js

20b8385fe4b8ab3ce3c9.js

573 ms

4c6f9450a402f27827e1.js

4c6f9450a402f27827e1.js

613 ms

1c389f071daa24077a77.js

1c389f071daa24077a77.js

616 ms

a766995a9f5f36323003.js

a766995a9f5f36323003.js

585 ms

3066b83e93799bcb74b0.js

3066b83e93799bcb74b0.js

616 ms

a4fa395bc6393f135da0.js

a4fa395bc6393f135da0.js

615 ms

de0def97e0bcd8d3eaff.js

de0def97e0bcd8d3eaff.js

622 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf

19 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf

30 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf

39 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf

38 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebukDQ.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebukDQ.ttf

48 ms

7da4b1af9e6c2dd50004.js

7da4b1af9e6c2dd50004.js

594 ms

f588b417b0d92cb77f1a.js

f588b417b0d92cb77f1a.js

576 ms

79063832b40aef2f1e51.js

79063832b40aef2f1e51.js

579 ms

35358bd4e394442b4eb4.js

35358bd4e394442b4eb4.js

650 ms

c1f0be74a587aa121e64.js

c1f0be74a587aa121e64.js

749 ms

37daf5247aae7e22c9c7.js

37daf5247aae7e22c9c7.js

601 ms

88833bfa613f5883590b.js

88833bfa613f5883590b.js

627 ms

093ecf7c43c6b52ed26a.js

093ecf7c43c6b52ed26a.js

558 ms

cf9d3acbfe63d679c217.js

cf9d3acbfe63d679c217.js

616 ms

c52c0cd1a76d2d538382.js

c52c0cd1a76d2d538382.js

602 ms

6af12d22c2184e7832d5.js

6af12d22c2184e7832d5.js

643 ms

2bee6579ebe3a15fbc4c.js

2bee6579ebe3a15fbc4c.js

809 ms

c7b04aa29514b0b49e4b.js

c7b04aa29514b0b49e4b.js

638 ms

f6fc4f910f17518ca83c.js

f6fc4f910f17518ca83c.js

605 ms

50be8db3775a4cea4bcc.js

50be8db3775a4cea4bcc.js

657 ms

b7d2180569463680f7f9.js

b7d2180569463680f7f9.js

643 ms

32606d99f0a7f5ff34c9.js

32606d99f0a7f5ff34c9.js

595 ms

a0599539591a4ff97e42.js

a0599539591a4ff97e42.js

648 ms

6445a384c77f5f19f176.js

6445a384c77f5f19f176.js

658 ms

e9134f8e8c4db37d33f5.js

e9134f8e8c4db37d33f5.js

643 ms

275cfb6d9c7e4da4de91.js

275cfb6d9c7e4da4de91.js

614 ms

fb06263912a237f8eacb.js

fb06263912a237f8eacb.js

670 ms

3011c10ce33f75d15fdc.js

3011c10ce33f75d15fdc.js

624 ms

05195922a332f2499f74.js

05195922a332f2499f74.js

634 ms

ef3b1487178177ed09e0.js

ef3b1487178177ed09e0.js

600 ms

bd3b8b978942637e485c.js

bd3b8b978942637e485c.js

651 ms

9f8fb3dc4072e9c4d9d3.js

9f8fb3dc4072e9c4d9d3.js

622 ms

cdreport.js

cdreport.js

471 ms

78225ae6874920dd8a6c.js

78225ae6874920dd8a6c.js

620 ms

43b7edf9cec92f3756be.js

43b7edf9cec92f3756be.js

607 ms

8eadb72312dcf58470dd.js

8eadb72312dcf58470dd.js

631 ms

f89c1a35cc267879f83e.js

f89c1a35cc267879f83e.js

586 ms

71896614dc894242a374.js

71896614dc894242a374.js

584 ms

86e71c0a82c6f927658e.js

86e71c0a82c6f927658e.js

607 ms

hamburger.svg

hamburger.svg

627 ms

biffi_logo_svg.svg

biffi_logo_svg.svg

627 ms

search.svg

search.svg

562 ms

bag.svg

bag.svg

621 ms

plus.svg

plus.svg

627 ms

scalapay.svg

scalapay.svg

571 ms

Accessibility Review

biffi.com accessibility score

98

Accessibility Issues

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.

Best Practices

biffi.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

biffi.com SEO score

99

Search Engine Optimization Advices

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

    IT

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

biffi.com

Open Graph description is not detected on the main page of Biffi. 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: