Tools & Wizards About Us
briti.in screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

briti.in

Page Load Speed

1.1 sec in total

First Response

142 ms

Resources Loaded

901 ms

Page Rendered

101 ms

briti.in screenshot

About Website

Click here to check amazing Briti content for India. Otherwise, check out these important facts you probably never knew about briti.in

BRiTi utilizes potential of Social Networking to enhance user's buying, selling and renting experience.

Visit briti.in

Key Findings

We analyzed Briti.in page load time and found that the first response time was 142 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

briti.in performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.092

91/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

briti.in

142 ms

www.briti.in

128 ms

bootstrap.min.css

74 ms

style.css

73 ms

base.css

86 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 26% of them (15 requests) were addressed to the original Briti.in, 17% (10 requests) were made to Static.xx.fbcdn.net and 10% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (162 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 698.6 kB (70%)

Content Size

1.0 MB

After Optimization

306.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Briti.in main page is 1.0 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. 60% of websites need less resources to load. Javascripts take 516.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.2 kB

  • Original 48.1 kB
  • After minification 35.2 kB
  • After compression 8.9 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. This page needs HTML code to be minified as it can gain 13.0 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.2 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 7.1 kB

  • Original 69.4 kB
  • After minification 62.3 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. Briti images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 345.2 kB

  • Original 516.3 kB
  • After minification 515.8 kB
  • After compression 171.1 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 345.2 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 307.0 kB

  • Original 370.8 kB
  • After minification 367.2 kB
  • After compression 63.8 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. Briti.in needs all CSS files to be minified and compressed as it can save up to 307.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (55%)

Requests Now

51

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

briti.in

briti.in

142 ms

www.briti.in

www.briti.in

128 ms

bootstrap.min.css

bootstrap.min.css

74 ms

style.css

style.css

73 ms

base.css

base.css

86 ms

css

css

43 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

115 ms

jqueryform-min.js

jqueryform-min.js

86 ms

all.js

all.js

7 ms

bootstrap.min.js

bootstrap.min.js

85 ms

base-min.js

base-min.js

105 ms

client.js

client.js

85 ms

analytics.js

analytics.js

27 ms

JJzFcf26j3M

JJzFcf26j3M

136 ms

1327

1327

146 ms

LOGO1.png

LOGO1.png

84 ms

1.png

1.png

100 ms

f_tip.png

f_tip.png

85 ms

g_tip.png

g_tip.png

85 ms

rightPeakRed.png

rightPeakRed.png

84 ms

youtube-image.jpg

youtube-image.jpg

99 ms

158 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

46 ms

s-BiyweUPV0v-yRb-cjciMDdSZkkecOE1hvV7ZHvhyU.ttf

s-BiyweUPV0v-yRb-cjciMDdSZkkecOE1hvV7ZHvhyU.ttf

72 ms

EFpQQyG9GqCrobXxL-KRMcBaWKZ57bY3RXgXH6dOjZ0.ttf

EFpQQyG9GqCrobXxL-KRMcBaWKZ57bY3RXgXH6dOjZ0.ttf

81 ms

xd_arbiter.php

xd_arbiter.php

80 ms

xd_arbiter.php

xd_arbiter.php

123 ms

collect

collect

43 ms

postmessageRelay

postmessageRelay

73 ms

collect

collect

84 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

47 ms

www-embed-player.js

www-embed-player.js

73 ms

page.php

page.php

162 ms

init

init

98 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

44 ms

rpc:shindig_random.js

rpc:shindig_random.js

99 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

57 ms

ad_status.js

ad_status.js

51 ms

doorbell.min.css

doorbell.min.css

22 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

14 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

37 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

45 ms

4n08FrZmW0I.css

4n08FrZmW0I.css

48 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

54 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

73 ms

ihptErjAmMX.js

ihptErjAmMX.js

72 ms

11203004_864091653637368_2916129478298748431_n.jpg

11203004_864091653637368_2916129478298748431_n.jpg

47 ms

11188149_861930740520126_1482521853270877314_n.png

11188149_861930740520126_1482521853270877314_n.png

17 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

13 ms

11234971_1040314589346571_7505324650439939099_n.jpg

11234971_1040314589346571_7505324650439939099_n.jpg

15 ms

10357121_1528493670786367_845420054311066379_n.jpg

10357121_1528493670786367_845420054311066379_n.jpg

20 ms

12321316_907281846016559_5554649538694222909_n.jpg

12321316_907281846016559_5554649538694222909_n.jpg

19 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

10 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

11 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

4 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

4 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

6 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

8 ms

Accessibility Review

briti.in accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

briti.in 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

SEO Factors

briti.in SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Briti.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Briti.in 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

briti.in

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