Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

jogai.oi.com.br

Planos de internet Oi Fibra, Oi Play, 2ª via | Oi

Page Load Speed

37.4 sec in total

First Response

703 ms

Resources Loaded

31.6 sec

Page Rendered

5.1 sec

jogai.oi.com.br screenshot

About Website

Visit jogai.oi.com.br now to see the best up-to-date Jogai Oi content for Brazil and also check out these interesting facts you probably never knew about jogai.oi.com.br

Consulte disponibilidade de Oi Fibra no seu CEP e tenha até 1 Giga pra navegar à vontade. Acesse 2ª via e outros serviços.

Visit jogai.oi.com.br

Key Findings

We analyzed Jogai.oi.com.br page load time and found that the first response time was 703 ms and then it took 36.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

jogai.oi.com.br performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value31.6 s

0/100

25%

SI (Speed Index)

Value50.5 s

0/100

10%

TBT (Total Blocking Time)

Value57,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value76.7 s

0/100

10%

Network Requests Diagram

jogai.oi.com.br

703 ms

www.oi.com.br

224 ms

www.oi.com.br

344 ms

client.css

488 ms

jquery-3.4.1.min.js

456 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jogai.oi.com.br, 26% (24 requests) were made to Oi.com.br and 14% (13 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (12.3 sec) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 994.8 kB (16%)

Content Size

6.2 MB

After Optimization

5.2 MB

In fact, the total size of Jogai.oi.com.br main page is 6.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 496.9 kB

  • Original 876.0 kB
  • After minification 873.6 kB
  • After compression 379.1 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 496.9 kB or 57% of the original size.

Image Optimization

-10%

Potential reduce by 497.0 kB

  • Original 5.2 MB
  • After minification 4.7 MB

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. Jogai Oi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 851 B

  • Original 126.2 kB
  • After minification 126.2 kB
  • After compression 125.4 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 54 (66%)

Requests Now

82

After Optimization

28

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

Accessibility Review

jogai.oi.com.br accessibility score

63

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

button, link, and menuitem elements do not have accessible names.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

jogai.oi.com.br best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jogai.oi.com.br SEO score

79

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jogai.oi.com.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 Jogai.oi.com.br main page’s claimed encoding is iso-8859-1. 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

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