10.3 sec in total
686 ms
9.3 sec
300 ms
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.brWe 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.
gprs.oi.com.br performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value20.3 s
0/100
25%
Value4.3 s
77/100
10%
Value1,810 ms
9/100
30%
Value0
100/100
15%
Value19.3 s
2/100
10%
686 ms
447 ms
114 ms
159 ms
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 size can be reduced by 180.7 kB (67%)
270.4 kB
89.7 kB
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.
Potential reduce by 178.4 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.
Potential reduce by 869 B
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.
Potential reduce by 735 B
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.
Potential reduce by 660 B
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.
Number of requests can be reduced by 31 (31%)
101
70
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.
gprs.oi.com.br
686 ms
www.oi.com.br
447 ms
gtm.js
114 ms
gtm.js
159 ms
css2
37 ms
LumisPortal.js
11 ms
main.css
19 ms
main.js
18 ms
vlibras-plugin.js
548 ms
LumisDouiErrorSummary.js
17 ms
LumisDoui.js
18 ms
log.js
14 ms
header-logo-icon.svg
61 ms
location-light-mode.svg
9 ms
chevron-down-black.svg
11 ms
fileDownload.jsp
501 ms
acessibility-icon.svg
11 ms
contrast-icon-black.svg
546 ms
libras-icon-black.svg
894 ms
already-client-black.svg
32 ms
menu-icon-black.svg
29 ms
search-icon-black.svg
30 ms
user-support.svg
32 ms
fileDownload.jsp
527 ms
whatsapp-icon-white.svg
35 ms
close-icon-black.svg
34 ms
user-support-white.svg
38 ms
chevron-left-black.svg
36 ms
smart-house.svg
39 ms
chevron-right-green.svg
40 ms
category.svg
41 ms
plus.svg
43 ms
products-and-services-menu-card-bg.webp
47 ms
briefcase.svg
44 ms
arrow-right.svg
45 ms
gift.svg
88 ms
group-people.svg
47 ms
why-oi-menu-card-bg.webp
48 ms
flash.svg
49 ms
router.svg
52 ms
smartphone.svg
82 ms
phone.svg
83 ms
signfiber-home.svg
85 ms
arrow-right-black.svg
86 ms
signfiber-briefcase.svg
89 ms
signfiber-user.svg
91 ms
contactButtonv2-shopcart-light.svg
91 ms
contactbuttonv2-user-light.svg
92 ms
contactbuttonv2-whatsapp-light.svg
91 ms
contactbuttonv2-usersupport-light.svg
807 ms
contactbuttonv2-briefcase-light.svg
565 ms
contactbuttonv2-chatmessages-light.svg
1024 ms
contactbuttonv2-star-light.svg
1276 ms
icon-whatsapp-primary-light.svg
1037 ms
fileDownload.jsp
1221 ms
fileDownload.jsp
1846 ms
fileDownload.jsp
1385 ms
fileDownload.jsp
1191 ms
wifi.svg
1542 ms
round-check.svg
1650 ms
credit-card.svg
1381 ms
gift.svg
1435 ms
fileDownload.jsp
1841 ms
arrow-right-green.svg
1550 ms
fileDownload.jsp
2290 ms
fileDownload.jsp
1710 ms
fileDownload.jsp
2181 ms
rio-connection-background.webp
1823 ms
globoplay-icon.svg
2447 ms
reality-show-background.webp
2467 ms
paramount-icon.svg
2609 ms
soccer-player-background.webp
3004 ms
premiere-icon.svg
2633 ms
customer-service-background.webp
3378 ms
logo-joice.webp
3462 ms
fileDownload.jsp
3225 ms
fileDownload.jsp
2774 ms
user-support.svg
2810 ms
lamp-charging.svg
3286 ms
internet-normal-fiber.svg
2979 ms
device-responsive.svg
3141 ms
vlibras-plugin.js
33 ms
SimplonBP-Regular.woff
7075 ms
SimplonBP-Medium.woff
3788 ms
SimplonBP-Light.woff
3614 ms
SimplonOi-2018.otf
3167 ms
oi-saude-background.webp
2958 ms
oi-saude-logo.svg
2977 ms
arrow-right-oi-saude.svg
2860 ms
oi-energia-background.webp
3296 ms
oi-energia-logo.svg
3106 ms
arrow-right-oi-energia.svg
2826 ms
fileDownload.jsp
3077 ms
fileDownload.jsp
3414 ms
fileDownload.jsp
4185 ms
fileDownload.jsp
3209 ms
chevron-down.svg
3206 ms
arrow-right-green.svg
3175 ms
fileDownload.jsp
3169 ms
fileDownload.jsp
3200 ms
fileDownload.jsp
3078 ms
fileDownload.jsp
3132 ms
fileDownload.jsp
3144 ms
fileDownload.jsp
2892 ms
logo-oi.svg
2792 ms
logo-oi-dark.svg
3003 ms
search-icon-gray.svg
2588 ms
Pix.gif
1098 ms
gprs.oi.com.br accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
gprs.oi.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
gprs.oi.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
PT
PT
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.
gprs.oi.com.br
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: