Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gprs.oi.com.br

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

Page Load Speed

10.3 sec in total

First Response

686 ms

Resources Loaded

9.3 sec

Page Rendered

300 ms

About Website

Welcome to gprs.oi.com.br homepage info - get ready to check Gprs Oi best content for Brazil right away, or after learning these important things about gprs.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 gprs.oi.com.br

Key Findings

We analyzed Gprs.oi.com.br page load time and found that the first response time was 686 ms and then it took 9.6 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

gprs.oi.com.br performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value4.3 s

77/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

gprs.oi.com.br

686 ms

www.oi.com.br

447 ms

gtm.js

114 ms

gtm.js

159 ms

css2

37 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gprs.oi.com.br, 94% (101 requests) were made to Oi.com.br and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (7.1 sec) relates to the external source Oi.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.7 kB (67%)

Content Size

270.4 kB

After Optimization

89.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gprs.oi.com.br main page is 270.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. 60% of websites need less resources to load. HTML takes 224.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 178.4 kB

  • Original 224.5 kB
  • After minification 221.0 kB
  • After compression 46.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 178.4 kB or 79% of the original size.

Image Optimization

-30%

Potential reduce by 869 B

  • Original 2.9 kB
  • After minification 2.0 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, Gprs Oi needs image optimization as it can save up to 869 B or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 735 B

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 26.7 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.

CSS Optimization

-4%

Potential reduce by 660 B

  • Original 15.6 kB
  • After minification 15.6 kB
  • After compression 14.9 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. Gprs.oi.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (31%)

Requests Now

101

After Optimization

70

  • Images
  • JavaScript
  • CSS

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gprs 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

gprs.oi.com.br accessibility score

65

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Best Practices

gprs.oi.com.br best practices score

67

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

High

Page has valid source maps

SEO Factors

gprs.oi.com.br SEO score

86

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

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 Gprs.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 Gprs.oi.com.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

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