Tools & Wizards About Us
community.oas.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

community.oas.org

OAS Community

Page Load Speed

2.2 sec in total

First Response

725 ms

Resources Loaded

1.3 sec

Page Rendered

206 ms

community.oas.org screenshot

About Website

Click here to check amazing Community OAS content for Peru. Otherwise, check out these important facts you probably never knew about community.oas.org

OAS, Community, OEA, Organization of American Sates

Visit community.oas.org

Key Findings

We analyzed Community.oas.org page load time and found that the first response time was 725 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

community.oas.org performance score

0

Network Requests Diagram

community.oas.org

725 ms

layout.css

32 ms

screen.css

13 ms

DynamicStyle.aspx

17 ms

WebResource.axd

26 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 70% of them (46 requests) were addressed to the original Community.oas.org, 11% (7 requests) were made to Apis.google.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (725 ms) belongs to the original domain Community.oas.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (67%)

Content Size

1.6 MB

After Optimization

535.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Community.oas.org 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. 45% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 43.9 kB

  • Original 58.4 kB
  • After minification 56.5 kB
  • After compression 14.5 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 43.9 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 96.6 kB
  • After minification 94.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. Community OAS images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 775.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 386.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 775.2 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 276.7 kB

  • Original 315.7 kB
  • After minification 277.2 kB
  • After compression 39.0 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. Community.oas.org needs all CSS files to be minified and compressed as it can save up to 276.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (80%)

Requests Now

64

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

community.oas.org

community.oas.org

725 ms

layout.css

layout.css

32 ms

screen.css

screen.css

13 ms

DynamicStyle.aspx

DynamicStyle.aspx

17 ms

WebResource.axd

WebResource.axd

26 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

40 ms

jquery-ui-1.7.custom.min.js

jquery-ui-1.7.custom.min.js

48 ms

WebResource.axd

WebResource.axd

26 ms

WebResource.axd

WebResource.axd

26 ms

WebResource.axd

WebResource.axd

29 ms

WebResource.axd

WebResource.axd

30 ms

WebResource.axd

WebResource.axd

29 ms

WebResource.axd

WebResource.axd

31 ms

WebResource.axd

WebResource.axd

32 ms

jsapi

jsapi

23 ms

translate-this.js

translate-this.js

143 ms

addthis_widget.js

addthis_widget.js

50 ms

Search.js

Search.js

34 ms

GroupNavigation.js

GroupNavigation.js

35 ms

CustomWidgets.css

CustomWidgets.css

35 ms

UserInfoPopup.js

UserInfoPopup.js

41 ms

base.css

base.css

45 ms

header-fragments.css

header-fragments.css

47 ms

content-fragments.css

content-fragments.css

42 ms

footer-fragments.css

footer-fragments.css

43 ms

content-fragments-core.css

content-fragments-core.css

14 ms

content-fragments-forums.css

content-fragments-forums.css

19 ms

content-fragments-groups.css

content-fragments-groups.css

24 ms

content-fragments-mediagalleries.css

content-fragments-mediagalleries.css

16 ms

content-fragments-weblogs.css

content-fragments-weblogs.css

9 ms

content-fragments-wikis.css

content-fragments-wikis.css

10 ms

content-fragments-messages.css

content-fragments-messages.css

21 ms

homebackground-gris.gif

homebackground-gris.gif

7 ms

body.gif

body.gif

8 ms

bannernewnew_5F00_1.jpg

bannernewnew_5F00_1.jpg

19 ms

2627.azulito.jpg_2D00_200x0.jpg

2627.azulito.jpg_2D00_200x0.jpg

135 ms

1323.main_5F00_bldg_5F00_3.jpg_2D00_370x250.jpg

1323.main_5F00_bldg_5F00_3.jpg_2D00_370x250.jpg

9 ms

6747.asmblea.jpg_2D00_200x0.jpg

6747.asmblea.jpg_2D00_200x0.jpg

129 ms

7658.featured_5F00_culture.jpg_2D00_200x0.jpg

7658.featured_5F00_culture.jpg_2D00_200x0.jpg

128 ms

analytics.js

analytics.js

148 ms

ga.js

ga.js

53 ms

_ate.track.config_resp

_ate.track.config_resp

74 ms

300lo.json

300lo.json

71 ms

search-field-input.png

search-field-input.png

46 ms

group-nav-bkg.gif

group-nav-bkg.gif

44 ms

group-nav-sep.gif

group-nav-sep.gif

43 ms

group-nav-sep-with-children.gif

group-nav-sep-with-children.gif

43 ms

content-fragment-page-background-bottom-right.png

content-fragment-page-background-bottom-right.png

44 ms

content-fragment-page-background-bottom-left.png

content-fragment-page-background-bottom-left.png

45 ms

ltbluegradient.png

ltbluegradient.png

67 ms

icon-rss.png

icon-rss.png

66 ms

descending.gif

descending.gif

67 ms

sh.48536d49e4da3bdba54606b4.html

sh.48536d49e4da3bdba54606b4.html

63 ms

__utm.gif

__utm.gif

59 ms

print.css

print.css

30 ms

plusone.js

plusone.js

49 ms

collect

collect

13 ms

collect

collect

77 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

34 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

55 ms

fastbutton

fastbutton

66 ms

postmessageRelay

postmessageRelay

52 ms

rs=AGLTcCOUSJIRFuWfIxRmYNF0NPW_T9054A

rs=AGLTcCOUSJIRFuWfIxRmYNF0NPW_T9054A

3 ms

971028622-postmessagerelay.js

971028622-postmessagerelay.js

23 ms

rpc:shindig_random.js

rpc:shindig_random.js

39 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

SEO Factors

community.oas.org SEO score

0

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 Community.oas.org 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 Community.oas.org 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

community.oas.org

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