Access oemail.oi.com.br. Planos de internet Oi Fibra, Oi Play, 2ª via

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

oemail.oi.com.br

741 ms

www.oi.com.br

464 ms

gtm.js

99 ms

gtm.js

126 ms

css2

47 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oemail.oi.com.br, 93% (97 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 (4.8 sec) relates to the external source Oi.com.br.

Content Size

287.0 kB

After Optimization

98.2 kB

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

HTML Optimization

-78%

Potential reduce by 186.5 kB

Original 237.7 kB
After minification 234.5 kB
After compression 51.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 186.5 kB or 78% of the original size.

Image Optimization

-14%

Potential reduce by 869 B

Original 6.3 kB
After minification 5.4 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, Oemail Oi needs image optimization as it can save up to 869 B or 14% 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. Oemail.oi.com.br has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oemail 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.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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

oemail.oi.com.br

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

Report Summary

Performance

Accessibility

Best Practices

SEO

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

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

oemail.oi.com.br

www.oi.com.br

gtm.js

gtm.js

css2

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

oemail.oi.com.br

www.oi.com.br

gtm.js

gtm.js

css2

LumisPortal.js

main.css

main.js

vlibras-plugin.js

LumisDouiErrorSummary.js

LumisDoui.js

log.js

header-logo-icon.svg

location-light-mode.svg

chevron-down-black.svg

fileDownload.jsp

acessibility-icon.svg

contrast-icon-black.svg

libras-icon-black.svg

already-client-black.svg

menu-icon-black.svg

search-icon-black.svg

user-support.svg

fileDownload.jsp

whatsapp-icon-white.svg

close-icon-black.svg

user-support-white.svg

chevron-left-black.svg

smart-house.svg

chevron-right-green.svg

category.svg

plus.svg

products-and-services-menu-card-bg.webp

briefcase.svg

arrow-right.svg

gift.svg

group-people.svg

why-oi-menu-card-bg.webp

flash.svg

router.svg

smartphone.svg

phone.svg

signfiber-home.svg