Tools & Wizards About Us
architecturebrio.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

architecturebrio.com

Architecture BRIO - Mumbai Architects – India, the Netherlands

Page Load Speed

14.1 sec in total

First Response

588 ms

Resources Loaded

13.4 sec

Page Rendered

92 ms

architecturebrio.com screenshot

About Website

Welcome to architecturebrio.com homepage info - get ready to check Architecture BRIO best content for India right away, or after learning these important things about architecturebrio.com

Mumbai architects - international firm in India, practicing architecture, sustainable, interior design - hospitality, residential, institutional projects

Visit architecturebrio.com

Key Findings

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

Performance Metrics

architecturebrio.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

architecturebrio.com

588 ms

www.architecturebrio.com

1365 ms

style.min.css

818 ms

css

70 ms

frontend.css

835 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 73% of them (62 requests) were addressed to the original Architecturebrio.com, 14% (12 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Architecturebrio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.0 kB (22%)

Content Size

845.3 kB

After Optimization

663.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Architecturebrio.com main page is 845.3 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. 50% of websites need less resources to load. Javascripts take 435.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 164.9 kB

  • Original 209.5 kB
  • After minification 206.8 kB
  • After compression 44.6 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 164.9 kB or 79% of the original size.

Image Optimization

-23%

Potential reduce by 1.4 kB

  • Original 5.9 kB
  • After minification 4.5 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. Obviously, Architecture BRIO needs image optimization as it can save up to 1.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 10.8 kB

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

CSS Optimization

-3%

Potential reduce by 5.0 kB

  • Original 194.3 kB
  • After minification 193.8 kB
  • After compression 189.4 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. Architecturebrio.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (94%)

Requests Now

67

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

architecturebrio.com

architecturebrio.com

588 ms

www.architecturebrio.com

www.architecturebrio.com

1365 ms

style.min.css

style.min.css

818 ms

css

css

70 ms

frontend.css

frontend.css

835 ms

gallery.css

gallery.css

827 ms

style.css

style.css

837 ms

swiper.min.css

swiper.min.css

860 ms

slick.min.css

slick.min.css

866 ms

magnific-popup.css

magnific-popup.css

1591 ms

css

css

82 ms

style.css

style.css

1607 ms

ionicons.min.css

ionicons.min.css

1625 ms

et-line-font.css

et-line-font.css

1590 ms

before-after.min.css

before-after.min.css

1602 ms

style.min.css

style.min.css

1928 ms

admin-ajax.php

admin-ajax.php

2640 ms

css

css

75 ms

css

css

75 ms

addthis_wordpress_public.min.css

addthis_wordpress_public.min.css

2375 ms

jquery.min.js

jquery.min.js

2652 ms

jquery-migrate.min.js

jquery-migrate.min.js

2376 ms

frontend.js

frontend.js

2399 ms

jquery.galleriffic.js

jquery.galleriffic.js

2693 ms

js

js

102 ms

jquery.instashow-lite.packaged.js

jquery.instashow-lite.packaged.js

3401 ms

css

css

61 ms

js_composer.min.css

js_composer.min.css

3438 ms

custom.css

custom.css

3181 ms

bootstrap.min.css

bootstrap.min.css

3654 ms

dashicons.min.css

dashicons.min.css

3649 ms

rs6.css

rs6.css

3495 ms

jquery-masionary.js

jquery-masionary.js

3974 ms

frontend.js

frontend.js

4166 ms

imagesloaded.min.js

imagesloaded.min.js

4182 ms

masonry.min.js

masonry.min.js

4236 ms

jquery.masonry.min.js

jquery.masonry.min.js

4422 ms

pinit.js

pinit.js

63 ms

rbtools.min.js

rbtools.min.js

4936 ms

rs6.min.js

rs6.min.js

5275 ms

scroll-back-to-top.js

scroll-back-to-top.js

4930 ms

swiper.min.js

swiper.min.js

5209 ms

file_picker.js

file_picker.js

5002 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

5205 ms

iframe_api

iframe_api

67 ms

addthis_widget.js

addthis_widget.js

54 ms

tweenMax.min.js

tweenMax.min.js

5967 ms

vivus.min.js

vivus.min.js

4925 ms

slick.min.js

slick.min.js

4981 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

5197 ms

hammer.min.js

hammer.min.js

5187 ms

foxlazy.min.js

foxlazy.min.js

5190 ms

all.js

all.js

6045 ms

kenburn.js

kenburn.js

4994 ms

jquery.multiscroll.js

jquery.multiscroll.js

5187 ms

countTo.js

countTo.js

5315 ms

skills.js

skills.js

5300 ms

parallax.min.js

parallax.min.js

5205 ms

owlcarousel.js

owlcarousel.js

5415 ms

split-slider.js

split-slider.js

5189 ms

banner_slider.js

banner_slider.js

5234 ms

wow.min.js

wow.min.js

5313 ms

before-after.min.js

before-after.min.js

5073 ms

comment-reply.min.js

comment-reply.min.js

5042 ms

js_composer_front.min.js

js_composer_front.min.js

5358 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

28 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

37 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

45 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

47 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

46 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

46 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

45 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

45 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

46 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

46 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5666 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5106 ms

BRIO-pvtltd_letterhead-logo-old2-1-300x35.png

BRIO-pvtltd_letterhead-logo-old2-1-300x35.png

5073 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDrMfJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDrMfJg.woff

4 ms

dummy.png

dummy.png

4954 ms

pinit_main.js

pinit_main.js

5 ms

www-widgetapi.js

www-widgetapi.js

3 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

916 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

958 ms

Accessibility Review

architecturebrio.com accessibility score

94

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

Links do not have a discernible name

Best Practices

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

Page has valid source maps

SEO Factors

architecturebrio.com SEO score

93

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 doesn't use legible font sizes

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

architecturebrio.com

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