Tools & Wizards About Us
ipv6.br screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ipv6.br

IPv6.br

Page Load Speed

16.3 sec in total

First Response

357 ms

Resources Loaded

15.4 sec

Page Rendered

577 ms

ipv6.br screenshot

About Website

Visit ipv6.br now to see the best up-to-date IPv6 content for Brazil and also check out these interesting facts you probably never knew about ipv6.br

IPv6

Visit ipv6.br

Key Findings

We analyzed Ipv6.br page load time and found that the first response time was 357 ms and then it took 15.9 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

ipv6.br performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.234

53/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

ipv6.br

357 ms

bootstrap.min.css

261 ms

theme.css

291 ms

392 ms

ipv6-ases.svg

12460 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 68% of them (38 requests) were addressed to the original Ipv6.br, 7% (4 requests) were made to Rosabaya.ceptro.br and 5% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (12.7 sec) relates to the external source Validador.ipv6.br.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

675.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 28.2 kB

  • Original 35.7 kB
  • After minification 27.5 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 23% 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 28.2 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 92.8 kB

  • Original 617.0 kB
  • After minification 524.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. Obviously, IPv6 needs image optimization as it can save up to 92.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 457.9 kB

  • Original 576.8 kB
  • After minification 403.7 kB
  • After compression 118.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 457.9 kB or 79% of the original size.

CSS Optimization

-83%

Potential reduce by 120.5 kB

  • Original 145.7 kB
  • After minification 145.4 kB
  • After compression 25.2 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. Ipv6.br needs all CSS files to be minified and compressed as it can save up to 120.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

48

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ipv6.br

ipv6.br

357 ms

bootstrap.min.css

bootstrap.min.css

261 ms

theme.css

theme.css

291 ms

392 ms

ipv6-ases.svg

ipv6-ases.svg

12460 ms

lacnic.php

lacnic.php

12731 ms

sflow_grapher

sflow_grapher

856 ms

agregado-bps6_bps-weekly.png

agregado-bps6_bps-weekly.png

359 ms

plotend.png

plotend.png

1006 ms

cgi.png

cgi.png

614 ms

subnet_home.js

subnet_home.js

260 ms

old_subnet.js

old_subnet.js

258 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

406 ms

bootstrap.min.js

bootstrap.min.js

260 ms

widgets.js

widgets.js

12 ms

main.js

main.js

371 ms

busca.js

busca.js

402 ms

bootstrap.youtubepopup.js

bootstrap.youtubepopup.js

401 ms

youtube-modal.js

youtube-modal.js

403 ms

afterload.js

afterload.js

453 ms

logo-nicbr-topo.png

logo-nicbr-topo.png

502 ms

logo-cgibr-topo.png

logo-cgibr-topo.png

609 ms

logo-ipv6.png

logo-ipv6.png

609 ms

icon-youtube-header.png

icon-youtube-header.png

610 ms

icon-twitter-header.png

icon-twitter-header.png

609 ms

icon-facebook-header.png

icon-facebook-header.png

618 ms

icon-rss-header.png

icon-rss-header.png

631 ms

banner_ipv6.png

banner_ipv6.png

1473 ms

V_SemanaInfra%20(1).jpg

V_SemanaInfra%20(1).jpg

909 ms

forum-ipv6.png

forum-ipv6.png

784 ms

393811_02_mini_banner_372x190_summit_ipv6.jpg

393811_02_mini_banner_372x190_summit_ipv6.jpg

1060 ms

spinner.gif

spinner.gif

896 ms

spinner_big.gif

spinner_big.gif

884 ms

background.jpg

background.jpg

613 ms

icons-s529668412f.png

icons-s529668412f.png

841 ms

footer.png

footer.png

882 ms

raleway-regular-webfont.woff

raleway-regular-webfont.woff

698 ms

montserrat-bold-webfont.woff

montserrat-bold-webfont.woff

721 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

826 ms

raleway-light-webfont.woff

raleway-light-webfont.woff

843 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

841 ms

88x31.png

88x31.png

124 ms

jsapi

jsapi

100 ms

jquery-1.11.2.js

jquery-1.11.2.js

582 ms

mainChart.js

mainChart.js

265 ms

piwik.js

piwik.js

550 ms

ui+en,table+en,controls+en,annotationchart+en.css

ui+en,table+en,controls+en,annotationchart+en.css

4 ms

format+en,default+en,ui+en,table+en,controls+en,corechart+en,annotationchart+en.I.js

format+en,default+en,ui+en,table+en,controls+en,corechart+en,annotationchart+en.I.js

28 ms

ipv6_data

ipv6_data

296 ms

tooltip.css

tooltip.css

96 ms

lacnic-ipv4runout-plot.png

lacnic-ipv4runout-plot.png

2274 ms

v6-test.js

v6-test.js

262 ms

subnet_home.js

subnet_home.js

274 ms

validador_site.js

validador_site.js

280 ms

record.php

record.php

133 ms

vermelho.png

vermelho.png

143 ms

Accessibility Review

ipv6.br accessibility score

61

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

ipv6.br best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ipv6.br SEO score

83

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

High

Image elements do not have [alt] attributes

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

ipv6.br

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