Tools & Wizards About Us
brii.pk screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

brii.pk

BRii - Digital Ampere Meter - Multi meter - Voltmeter - Digital Energy Meter

Page Load Speed

5.5 sec in total

First Response

586 ms

Resources Loaded

3.8 sec

Page Rendered

1.1 sec

brii.pk screenshot

About Website

Welcome to brii.pk homepage info - get ready to check BRii best content right away, or after learning these important things about brii.pk

For the First Time in Pakistan, BRii introducing real-time Digital Ampere Meter / multimeter / eneryg meter for monitoring of home & office appliances Watts , Ampere , kWh , Time Duration & Bill Amoun...

Visit brii.pk

Key Findings

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

Performance Metrics

brii.pk performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value4,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

brii.pk

586 ms

js

335 ms

fbevents.js

221 ms

css

327 ms

bootstrap.css

394 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 53% of them (33 requests) were addressed to the original Brii.pk, 15% (9 requests) were made to Youtube.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Stats.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 986.1 kB (61%)

Content Size

1.6 MB

After Optimization

640.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brii.pk main page is 1.6 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 638.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.6 kB

  • Original 24.3 kB
  • After minification 17.7 kB
  • After compression 5.7 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 6.6 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 18.6 kB or 77% of the original size.

Image Optimization

-35%

Potential reduce by 225.7 kB

  • Original 638.6 kB
  • After minification 412.9 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, BRii needs image optimization as it can save up to 225.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 237.7 kB

  • Original 364.1 kB
  • After minification 283.7 kB
  • After compression 126.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 237.7 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 504.1 kB

  • Original 599.9 kB
  • After minification 562.9 kB
  • After compression 95.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. Brii.pk needs all CSS files to be minified and compressed as it can save up to 504.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (72%)

Requests Now

53

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brii.pk

brii.pk

586 ms

js

js

335 ms

fbevents.js

fbevents.js

221 ms

css

css

327 ms

bootstrap.css

bootstrap.css

394 ms

font-awesome.css

font-awesome.css

457 ms

simple-line-icons.css

simple-line-icons.css

327 ms

magnific-popup.css

magnific-popup.css

328 ms

aos.css

aos.css

453 ms

flexslider.css

flexslider.css

392 ms

style.css

style.css

542 ms

color-5.css

color-5.css

458 ms

modernizr.js

modernizr.js

551 ms

html5shiv.js

html5shiv.js

527 ms

respond.min.js

respond.min.js

527 ms

jquery.min.js

jquery.min.js

171 ms

bootstrap.min.js

bootstrap.min.js

718 ms

device.min.js

device.min.js

725 ms

retina.min.js

retina.min.js

750 ms

nav.js

nav.js

748 ms

smooth-scroll.min.js

smooth-scroll.min.js

751 ms

parallax.js

parallax.js

752 ms

flexslider.js

flexslider.js

753 ms

youtubebackground.js

youtubebackground.js

757 ms

magnific-popup.min.js

magnific-popup.min.js

756 ms

init.js

init.js

780 ms

placeholders.js

placeholders.js

781 ms

init-for-ie.js

init-for-ie.js

783 ms

368622590839011

368622590839011

851 ms

bg1.jpg

bg1.jpg

330 ms

8I6pwOs9WUA

8I6pwOs9WUA

531 ms

digital_Ampere_meter.png

digital_Ampere_meter.png

410 ms

digital_Ampere_meter_ac.png

digital_Ampere_meter_ac.png

585 ms

logo.png

logo.png

403 ms

Product_Back.png

Product_Back.png

403 ms

style.css

style.css

402 ms

LCD_modes.jpg

LCD_modes.jpg

404 ms

pins.jpg

pins.jpg

503 ms

background-contact.jpg

background-contact.jpg

402 ms

analytics.js

analytics.js

545 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

282 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

407 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

213 ms

www-player.css

www-player.css

230 ms

www-embed-player.js

www-embed-player.js

289 ms

base.js

base.js

448 ms

fetch-polyfill.js

fetch-polyfill.js

227 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

670 ms

collect

collect

111 ms

iframe_api

iframe_api

238 ms

collect

collect

1017 ms

asset_composer.js

asset_composer.js

686 ms

www-widgetapi.js

www-widgetapi.js

374 ms

ad_status.js

ad_status.js

558 ms

GMxt2AoYqj2WXpyEdgkoen9XiD3znMxv6lengZkwUWM.js

GMxt2AoYqj2WXpyEdgkoen9XiD3znMxv6lengZkwUWM.js

804 ms

embed.js

embed.js

194 ms

2cOKqeDXzHE

2cOKqeDXzHE

258 ms

ga-audiences

ga-audiences

494 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

51 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

489 ms

id

id

477 ms

id

id

84 ms

Accessibility Review

brii.pk accessibility score

85

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

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.

Best Practices

brii.pk best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

brii.pk SEO score

92

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

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 Brii.pk 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 Brii.pk 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

brii.pk

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