Tools & Wizards About Us
brgy.info screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

brgy.info

www.brgy.info - barangay information - philippine zipcodes

Page Load Speed

2.9 sec in total

First Response

472 ms

Resources Loaded

2.2 sec

Page Rendered

179 ms

brgy.info screenshot

About Website

Visit brgy.info now to see the best up-to-date Brgy content for Philippines and also check out these interesting facts you probably never knew about brgy.info

philippines zipcodes,current time in the philippines,brgy information and road maps from google

Visit brgy.info

Key Findings

We analyzed Brgy.info page load time and found that the first response time was 472 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

brgy.info performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

brgy.info

472 ms

brand

14 ms

show_ads.js

4 ms

paypal_mrb_banner.gif

1426 ms

80x15.png

33 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brgy.info, 24% (12 requests) were made to Pagead2.googlesyndication.com and 16% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Images.paypal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 586.3 kB (65%)

Content Size

899.9 kB

After Optimization

313.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brgy.info main page is 899.9 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 846.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.8 kB

  • Original 26.1 kB
  • After minification 25.3 kB
  • After compression 6.3 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 19.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 kB
  • After minification 1.8 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. Brgy images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 542.9 kB

  • Original 846.9 kB
  • After minification 844.6 kB
  • After compression 304.0 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 542.9 kB or 64% of the original size.

CSS Optimization

-94%

Potential reduce by 23.6 kB

  • Original 25.1 kB
  • After minification 9.9 kB
  • After compression 1.5 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. Brgy.info needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 94% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (74%)

Requests Now

46

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brgy.info

brgy.info

472 ms

brand

brand

14 ms

show_ads.js

show_ads.js

4 ms

paypal_mrb_banner.gif

paypal_mrb_banner.gif

1426 ms

80x15.png

80x15.png

33 ms

brand

brand

34 ms

ca-pub-0363845375718303.js

ca-pub-0363845375718303.js

40 ms

zrt_lookup.html

zrt_lookup.html

25 ms

show_ads_impl.js

show_ads_impl.js

36 ms

googlelogo_lightgrey_46x16dp.png

googlelogo_lightgrey_46x16dp.png

67 ms

cloudflare.js

cloudflare.js

16 ms

ads

ads

182 ms

osd.js

osd.js

2 ms

ads

ads

150 ms

badge.js

badge.js

34 ms

ads

ads

184 ms

ads

ads

140 ms

ads

ads

107 ms

extra.js

extra.js

3 ms

abg.js

abg.js

32 ms

osd_listener.js

osd_listener.js

63 ms

gen_204

gen_204

14 ms

ad

ad

49 ms

o16FtOAn.js

o16FtOAn.js

81 ms

m_window_focus_non_hydra.js

m_window_focus_non_hydra.js

73 ms

m_qs_click_protection.js

m_qs_click_protection.js

72 ms

abg.js

abg.js

27 ms

lidar.js

lidar.js

30 ms

d5qAyLYU.js

d5qAyLYU.js

30 ms

pixel

pixel

39 ms

i_all_aol2.js

i_all_aol2.js

40 ms

9im3l02I.html

9im3l02I.html

18 ms

pixel

pixel

88 ms

pixel

pixel

100 ms

transparent.png

transparent.png

8 ms

T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js

T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js

4 ms

polyfills.promise.js

polyfills.promise.js

53 ms

polyfills.intersection-observer.js

polyfills.intersection-observer.js

58 ms

stormtrooper.css

stormtrooper.css

71 ms

sync

sync

37 ms

vast.js

vast.js

27 ms

jwpsrv.js

jwpsrv.js

24 ms

related.js

related.js

33 ms

jwplayer.controls.js

jwplayer.controls.js

33 ms

load_pixelbadge.js

load_pixelbadge.js

340 ms

badges-small.png

badges-small.png

108 ms

activeview

activeview

12 ms

activeview

activeview

13 ms

activeview

activeview

16 ms

activeview

activeview

15 ms

Accessibility Review

brgy.info accessibility score

81

Accessibility Issues

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-*] attributes do not match their roles

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

brgy.info best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

brgy.info SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brgy.info can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Brgy.info main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

brgy.info

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