Tools & Wizards About Us
w3c.br screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

w3c.br

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

Page Load Speed

9.2 sec in total

First Response

365 ms

Resources Loaded

8.3 sec

Page Rendered

587 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 365 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

w3c.br performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

w3c.br

365 ms

WebHome

3337 ms

style.css

257 ms

minimum-src.css

258 ms

advanced-src.css

260 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 96% of them (69 requests) were addressed to the original W3c.br, 1% (1 request) were made to W3.org and 1% (1 request) were made to Validador.ipv6.br. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain W3c.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.9 kB (47%)

Content Size

638.4 kB

After Optimization

336.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 43.0 kB

  • Original 56.8 kB
  • After minification 55.7 kB
  • After compression 13.8 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.0 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 12.6 kB

  • Original 229.4 kB
  • After minification 216.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. W3C images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 195.6 kB

  • Original 287.3 kB
  • After minification 286.0 kB
  • After compression 91.6 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 195.6 kB or 68% of the original size.

CSS Optimization

-78%

Potential reduce by 50.6 kB

  • Original 64.9 kB
  • After minification 52.9 kB
  • After compression 14.3 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 50.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (45%)

Requests Now

64

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 64 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 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

w3c.br

w3c.br

365 ms

WebHome

WebHome

3337 ms

style.css

style.css

257 ms

minimum-src.css

minimum-src.css

258 ms

advanced-src.css

advanced-src.css

260 ms

jquery.tablesorter.css

jquery.tablesorter.css

2510 ms

jquery-1.9.1.js

jquery-1.9.1.js

482 ms

jquery.migrate.js

jquery.migrate.js

286 ms

jquery.livequery.js

jquery.livequery.js

377 ms

jquery.foswiki.js

jquery.foswiki.js

383 ms

foswikiPref%25FWSRC%25.js

foswikiPref%25FWSRC%25.js

2838 ms

foswikiString%25FWSRC%25.js

foswikiString%25FWSRC%25.js

2658 ms

jquery.tablesorter.js

jquery.tablesorter.js

2856 ms

tables.js

tables.js

507 ms

foswikiForm%25FWSRC%25.js

foswikiForm%25FWSRC%25.js

2947 ms

pattern%25FWSRC%25.js

pattern%25FWSRC%25.js

2848 ms

main.js

main.js

2765 ms

base.css

base.css

2795 ms

valid-xhtml10

valid-xhtml10

84 ms

banipv62branco.png

banipv62branco.png

329 ms

page_bkg.jpg

page_bkg.jpg

144 ms

logo-w3c-screen-lg-br.png

logo-w3c-screen-lg-br.png

256 ms

logo-w3c-mobile-lg.png

logo-w3c-mobile-lg.png

129 ms

search-bg.png

search-bg.png

130 ms

google.gif

google.gif

142 ms

search-button.png

search-button.png

144 ms

logo-shadow.png

logo-shadow.png

256 ms

category-bg-fold.png

category-bg-fold.png

256 ms

category-bg.png

category-bg.png

283 ms

header-link.gif

header-link.gif

284 ms

theme-all.png

theme-all.png

285 ms

skip100.png

skip100.png

381 ms

Emmy_w3c.jpg

Emmy_w3c.jpg

765 ms

postcard_thumb.png

postcard_thumb.png

639 ms

todosnb.png

todosnb.png

424 ms

mobile.png

mobile.png

427 ms

external.gif

external.gif

429 ms

bannerdal.jpg

bannerdal.jpg

508 ms

videoAcessibilidade100.png

videoAcessibilidade100.png

565 ms

todosnaweb.jpg

todosnaweb.jpg

578 ms

Conf2011c.png

Conf2011c.png

578 ms

talks-bg-left.png

talks-bg-left.png

635 ms

talks-bg-right.png

talks-bg-right.png

705 ms

talks-bg.png

talks-bg.png

710 ms

calendar-sprite.png

calendar-sprite.png

710 ms

else.gif

else.gif

762 ms

pdf.gif

pdf.gif

765 ms

category-bg-right.png

category-bg-right.png

847 ms

64x.png

64x.png

851 ms

logo-nic.gif

logo-nic.gif

853 ms

logo-inweb.gif

logo-inweb.gif

889 ms

logo-puc.gif

logo-puc.gif

889 ms

logo-senac.gif

logo-senac.gif

891 ms

logo-serpro.gif

logo-serpro.gif

987 ms

logo-sevencards.gif

logo-sevencards.gif

993 ms

logo-ufal.gif

logo-ufal.gif

931 ms

piwik.js

piwik.js

494 ms

logo-ufes.gif

logo-ufes.gif

894 ms

logo-ufpe.gif

logo-ufpe.gif

893 ms

logo-usp.gif

logo-usp.gif

884 ms

timgov20.jpg

timgov20.jpg

991 ms

I_heart_validator.png

I_heart_validator.png

997 ms

footer-shadow.png

footer-shadow.png

889 ms

twitter-bird.png

twitter-bird.png

893 ms

identica-logo.png

identica-logo.png

894 ms

logo-cgi.gif

logo-cgi.gif

871 ms

logoW3C_br70px.jpg

logoW3C_br70px.jpg

992 ms

ico-minus.gif

ico-minus.gif

999 ms

ico-plus.gif

ico-plus.gif

905 ms

minimum.css

minimum.css

146 ms

print.css

print.css

144 ms

realprint.css

realprint.css

145 ms

Accessibility Review

w3c.br accessibility score

90

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

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

w3c.br best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

w3c.br SEO score

98

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

    UTF8

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

w3c.br

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