Tools & Wizards About Us
brazilrio.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

brazilrio.org

Rio de Janeiro in Brazil - Travel site to the Marvellous City

Page Load Speed

19.1 sec in total

First Response

2.7 sec

Resources Loaded

16 sec

Page Rendered

368 ms

brazilrio.org screenshot

About Website

Visit brazilrio.org now to see the best up-to-date Brazil Rio content and also check out these interesting facts you probably never knew about brazilrio.org

Rio de Janeiro in Brazil - the Marvellous City. We have the best travel guide for gringos visiting Rio.

Visit brazilrio.org

Key Findings

We analyzed Brazilrio.org page load time and found that the first response time was 2.7 sec and then it took 16.4 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

brazilrio.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value5,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

www.brazilrio.org

2698 ms

wp-emoji-release.min.js

744 ms

googlePlus.css

1119 ms

columns.css

1289 ms

styles.css

1395 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 31% of them (34 requests) were addressed to the original Brazilrio.org, 13% (14 requests) were made to Tpc.googlesyndication.com and 5% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (9.5 sec) belongs to the original domain Brazilrio.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 611.2 kB (58%)

Content Size

1.0 MB

After Optimization

434.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brazilrio.org 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 578.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 40.5 kB

  • Original 53.1 kB
  • After minification 51.2 kB
  • After compression 12.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 40.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 179.2 kB
  • After minification 179.2 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. Brazil Rio images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 371.7 kB

  • Original 578.9 kB
  • After minification 540.7 kB
  • After compression 207.2 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 371.7 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 199.0 kB

  • Original 234.9 kB
  • After minification 186.1 kB
  • After compression 35.9 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. Brazilrio.org needs all CSS files to be minified and compressed as it can save up to 199.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

103

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.brazilrio.org

www.brazilrio.org

2698 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

744 ms

googlePlus.css

googlePlus.css

1119 ms

columns.css

columns.css

1289 ms

styles.css

styles.css

1395 ms

pagination.css

pagination.css

1401 ms

bootstrap.css

bootstrap.css

2052 ms

ticker-style.css

ticker-style.css

1398 ms

owl.carousel.css

owl.carousel.css

1452 ms

css

css

519 ms

style.css

style.css

1707 ms

widget.css

widget.css

1546 ms

style.css

style.css

1552 ms

font-awesome.css

font-awesome.css

1931 ms

sharebar.css

sharebar.css

1720 ms

widgets.js

widgets.js

151 ms

buttons.js

buttons.js

154 ms

adsbygoogle.js

adsbygoogle.js

85 ms

wp_clock.php

wp_clock.php

284 ms

AlpinePhotoTiles_style.css

AlpinePhotoTiles_style.css

222 ms

googleCards.min.js

googleCards.min.js

224 ms

jquery.min.js

jquery.min.js

148 ms

jquery-migrate.min.js

jquery-migrate.min.js

9512 ms

sharebar.js

sharebar.js

1161 ms

mailchimp-widget-min.js

mailchimp-widget-min.js

403 ms

jquery.form.min.js

jquery.form.min.js

399 ms

scripts.js

scripts.js

562 ms

sbp-lazy-load.min.js

sbp-lazy-load.min.js

564 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

571 ms

bootstrap.js

bootstrap.js

891 ms

owl.carousel.min.js

owl.carousel.min.js

743 ms

jquery.ticker.js

jquery.ticker.js

741 ms

default.js

default.js

749 ms

widget.js

widget.js

927 ms

wp-embed.min.js

wp-embed.min.js

944 ms

AlpinePhotoTiles_script.js

AlpinePhotoTiles_script.js

1156 ms

easy-table.css

easy-table.css

1044 ms

analytics.js

analytics.js

105 ms

riodejaneiro.png

riodejaneiro.png

2451 ms

home.png

home.png

174 ms

1x1.trans.gif

1x1.trans.gif

175 ms

rss.png

rss.png

174 ms

buttons.js

buttons.js

347 ms

EQ3GOVycA7M

EQ3GOVycA7M

402 ms

H3fDjNZTjAA

H3fDjNZTjAA

478 ms

qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff

qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff

253 ms

collect

collect

65 ms

ca-pub-1983509704878454.js

ca-pub-1983509704878454.js

397 ms

zrt_lookup.html

zrt_lookup.html

355 ms

show_ads_impl.js

show_ads_impl.js

673 ms

collect

collect

810 ms

linkid.js

linkid.js

57 ms

ga.js

ga.js

191 ms

collect

collect

318 ms

__utm.gif

__utm.gif

66 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

431 ms

www-embed-player.js

www-embed-player.js

541 ms

base.js

base.js

687 ms

collect

collect

582 ms

ads

ads

496 ms

osd.js

osd.js

178 ms

ads

ads

557 ms

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

308 ms

ad_status.js

ad_status.js

287 ms

13675885760701278932

13675885760701278932

388 ms

abg.js

abg.js

400 ms

m_js_controller.js

m_js_controller.js

440 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

371 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

355 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

374 ms

GpaGenericImage_SingleImg_NameTag_970x90.html

GpaGenericImage_SingleImg_NameTag_970x90.html

387 ms

s

s

55 ms

x_button_blue2.png

x_button_blue2.png

81 ms

common_styles_v2.css

common_styles_v2.css

33 ms

GpaGenericImage_SingleImg_NameTag_common.css

GpaGenericImage_SingleImg_NameTag_common.css

31 ms

angular.min.js

angular.min.js

94 ms

utils_min.js

utils_min.js

22 ms

addata.js

addata.js

22 ms

layouts_bootstrap_v3.js

layouts_bootstrap_v3.js

26 ms

common_scripts_v4.js

common_scripts_v4.js

25 ms

GpaGenericImage_SingleImg_NameTag.js

GpaGenericImage_SingleImg_NameTag.js

119 ms

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

102 ms

1851213986573582968

1851213986573582968

48 ms

_i1883027.jpg-width=300_1429654743691__i1883027.jpg

_i1883027.jpg-width=300_1429654743691__i1883027.jpg

47 ms

activeview

activeview

130 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

236 ms

getAllAppDefault.esi

getAllAppDefault.esi

250 ms

loggo_rio_2016_olympics.gif

loggo_rio_2016_olympics.gif

318 ms

94c53f9ef5fab92fe111710e6594ecfe.jpg

94c53f9ef5fab92fe111710e6594ecfe.jpg

307 ms

0976861d45ddc22351218c35c63f24e4.jpg

0976861d45ddc22351218c35c63f24e4.jpg

424 ms

185b0007e98467296c75c13b00ee7fbf.jpg

185b0007e98467296c75c13b00ee7fbf.jpg

613 ms

5440c2993d4c580a86500ec285c468f6.jpg

5440c2993d4c580a86500ec285c468f6.jpg

424 ms

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

69 ms

getSegment.php

getSegment.php

53 ms

checkOAuth.esi

checkOAuth.esi

30 ms

t.dhj

t.dhj

136 ms

t.dhj

t.dhj

170 ms

cm

cm

117 ms

x35248

x35248

194 ms

s-3271.xgi

s-3271.xgi

36 ms

36 ms

17 ms

jot.html

jot.html

6 ms

index.a8fc48294ca4cc10eb440189d9f22d7c.html

index.a8fc48294ca4cc10eb440189d9f22d7c.html

97 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

51 ms

getCount2.php

getCount2.php

97 ms

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

43 ms

hbpix

hbpix

260 ms

pixel

pixel

384 ms

52154.gif

52154.gif

41 ms

2981

2981

109 ms

Accessibility Review

brazilrio.org 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

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

High

Links do not have a discernible name

Best Practices

brazilrio.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

brazilrio.org SEO score

96

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

High

Tap targets are not sized appropriately

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 Brazilrio.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 Brazilrio.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

brazilrio.org

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