Tools & Wizards About Us
g20.org screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

g20.org

G20 Brasil 2024 - Português (Brasil)

Page Load Speed

33.4 sec in total

First Response

3.4 sec

Resources Loaded

29.7 sec

Page Rendered

275 ms

g20.org screenshot

About Website

Visit g20.org now to see the best up-to-date G20 content for Indonesia and also check out these interesting facts you probably never knew about g20.org

2016年G20峰会官网

Visit g20.org

Key Findings

We analyzed G20.org page load time and found that the first response time was 3.4 sec and then it took 29.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 28 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

g20.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value22.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.4 s

0/100

25%

SI (Speed Index)

Value54.6 s

0/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.289

41/100

15%

TTI (Time to Interactive)

Value45.5 s

0/100

10%

Network Requests Diagram

g20.org

3436 ms

css.css

3913 ms

style.css

1827 ms

jquery.min.js

3519 ms

SuperSlide.2.1.js

967 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that all of those requests were addressed to G20.org and no external sources were called. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain G20.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.9 kB (23%)

Content Size

289.0 kB

After Optimization

223.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of G20.org main page is 289.0 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. Only 10% of websites need less resources to load. Images take 220.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.2 kB

  • Original 24.5 kB
  • After minification 20.3 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 17% 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 19.2 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 16.1 kB

  • Original 220.5 kB
  • After minification 204.4 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. G20 images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 19.4 kB

  • Original 29.5 kB
  • After minification 28.8 kB
  • After compression 10.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 19.4 kB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 11.2 kB

  • Original 14.5 kB
  • After minification 12.3 kB
  • After compression 3.4 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. G20.org needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

g20.org

g20.org

3436 ms

css.css

css.css

3913 ms

style.css

style.css

1827 ms

jquery.min.js

jquery.min.js

3519 ms

SuperSlide.2.1.js

SuperSlide.2.1.js

967 ms

daimabiji.js

daimabiji.js

996 ms

koala.min.1.5.js

koala.min.1.5.js

5861 ms

logo.png

logo.png

3038 ms

head_bg.jpg

head_bg.jpg

20435 ms

W020160309470657434052.jpg

W020160309470657434052.jpg

20435 ms

W020160302331379078177.jpg

W020160302331379078177.jpg

20436 ms

W020160301617242928496.jpg

W020160301617242928496.jpg

20435 ms

W020160203567159794075.jpg

W020160203567159794075.jpg

20435 ms

W020160118597104619454.jpg

W020160118597104619454.jpg

20436 ms

bg.png

bg.png

20436 ms

W020160408422876848655.jpg

W020160408422876848655.jpg

20436 ms

W020160408423393360652.jpg

W020160408423393360652.jpg

20436 ms

W020160408517485357578.jpg

W020160408517485357578.jpg

20437 ms

bg1.png

bg1.png

20436 ms

btn.png

btn.png

20436 ms

W020160203554034187780.jpg

W020160203554034187780.jpg

20436 ms

W020160203563032909180.jpg

W020160203563032909180.jpg

20435 ms

W020151123602387602576.jpg

W020151123602387602576.jpg

20436 ms

W020160229487297287928.jpg

W020160229487297287928.jpg

20436 ms

W020151130708688649265.jpg

W020151130708688649265.jpg

20436 ms

W020151130707127628587.jpg

W020151130707127628587.jpg

20435 ms

W020151027598973400758.png

W020151027598973400758.png

20436 ms

W020151027598974156786.png

W020151027598974156786.png

20436 ms

W020151027598974542146.png

W020151027598974542146.png

20435 ms

W020151027608605201506.jpg

W020151027608605201506.jpg

20435 ms

W020151027608606216254.jpg

W020151027608606216254.jpg

20436 ms

W020151130734259499640.jpg

W020151130734259499640.jpg

20436 ms

W020151214360913947649.png

W020151214360913947649.png

20436 ms

W020160215596378661789.png

W020160215596378661789.png

20435 ms

footer_bg.jpg

footer_bg.jpg

20436 ms

di_logo.png

di_logo.png

20436 ms

terminator2.2.min.js

terminator2.2.min.js

20355 ms

Accessibility Review

g20.org accessibility score

81

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

g20.org SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G20.org 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 G20.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

g20.org

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