Tools & Wizards About Us
w3c.br screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

w3c.br

Consórcio World Wide Web (W3C) - Capítulo São Paulo

Page Load Speed

4.6 sec in total

First Response

612 ms

Resources Loaded

3.6 sec

Page Rendered

381 ms

w3c.br screenshot

About Website

Welcome to w3c.br homepage info - get ready to check W3C best content for Brazil right away, or after learning these important things about w3c.br

O Consórcio World Wide Web (W3C) é uma comunidade internacional que desenvolve padrões com o objetivo de garantir o crescimento da web.

Visit w3c.br

Key Findings

We analyzed W3c.br page load time and found that the first response time was 612 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

w3c.br performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

w3c.br

612 ms

w3c.br

849 ms

wp-emoji-release.min.js

1 ms

style.min.css

522 ms

style.build.css

662 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 85% of them (33 requests) were addressed to the original W3c.br, 8% (3 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain W3c.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 681.7 kB (51%)

Content Size

1.3 MB

After Optimization

652.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of W3c.br main page is 1.3 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. 30% of websites need less resources to load. Images take 659.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 106.3 kB

  • Original 129.5 kB
  • After minification 125.7 kB
  • After compression 23.2 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 106.3 kB or 82% of the original size.

Image Optimization

-22%

Potential reduce by 142.0 kB

  • Original 659.1 kB
  • After minification 517.1 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, W3C needs image optimization as it can save up to 142.0 kB or 22% 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 84.9 kB

  • Original 130.8 kB
  • After minification 130.8 kB
  • After compression 45.9 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 84.9 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 348.5 kB

  • Original 415.2 kB
  • After minification 411.2 kB
  • After compression 66.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. W3c.br needs all CSS files to be minified and compressed as it can save up to 348.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (58%)

Requests Now

31

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

w3c.br

w3c.br

612 ms

w3c.br

w3c.br

849 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1 ms

style.min.css

style.min.css

522 ms

style.build.css

style.build.css

662 ms

bootstrap.min.css

bootstrap.min.css

941 ms

theme.css

theme.css

695 ms

css2

css2

34 ms

all.min.css

all.min.css

970 ms

main.js

main.js

718 ms

style.min.css

style.min.css

975 ms

css

css

52 ms

jquery.min.js

jquery.min.js

1098 ms

jquery-migrate.min.js

jquery-migrate.min.js

1067 ms

singular.min.js

singular.min.js

961 ms

tipr.min.js

tipr.min.js

1067 ms

fortune.min.js

fortune.min.js

1067 ms

cropped-Captura-de-Tela-2021-06-02-%C3%A0s-15.36.21.png

cropped-Captura-de-Tela-2021-06-02-%C3%A0s-15.36.21.png

143 ms

Prancheta-%E2%80%93-1-760x300.png

Prancheta-%E2%80%93-1-760x300.png

257 ms

Prancheta-%E2%80%93-1-1.png

Prancheta-%E2%80%93-1-1.png

256 ms

Web-1920-%E2%80%93-4-760x300.png

Web-1920-%E2%80%93-4-760x300.png

188 ms

Prancheta-%E2%80%93-1-2.png

Prancheta-%E2%80%93-1-2.png

419 ms

Web-1920-%E2%80%93-3-760x300.png

Web-1920-%E2%80%93-3-760x300.png

314 ms

Web-1920-%E2%80%93-126-760x300.png

Web-1920-%E2%80%93-126-760x300.png

635 ms

ceweb.svg

ceweb.svg

384 ms

NIC-logo-footer.svg

NIC-logo-footer.svg

441 ms

CGI-logo-footer.svg

CGI-logo-footer.svg

509 ms

css-vars-ponyfill.min.js

css-vars-ponyfill.min.js

493 ms

css-var-ie-support.min.js

css-var-ie-support.min.js

506 ms

font

font

22 ms

font

font

32 ms

fa-brands-400.woff

fa-brands-400.woff

795 ms

fa-solid-900.woff

fa-solid-900.woff

919 ms

fa-regular-400.woff

fa-regular-400.woff

562 ms

style.min.css

style.min.css

141 ms

print-style.min.css

print-style.min.css

128 ms

css

css

21 ms

cropped-Captura-de-Tela-2021-06-02-%C3%A0s-15.36.21.png

cropped-Captura-de-Tela-2021-06-02-%C3%A0s-15.36.21.png

273 ms

print-style.min.css

print-style.min.css

141 ms

Accessibility Review

w3c.br accessibility score

97

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.

Best Practices

w3c.br 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

w3c.br SEO score

91

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise W3c.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that W3c.br 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

w3c.br

Open Graph data is detected on the main page of W3C. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: