Tools & Wizards About Us
rogercom.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

rogercom.com

Page Load Speed

1.1 sec in total

First Response

161 ms

Resources Loaded

706 ms

Page Rendered

191 ms

rogercom.com screenshot

About Website

Welcome to rogercom.com homepage info - get ready to check Rogercom best content for Brazil right away, or after learning these important things about rogercom.com

ZigBee, IEEE 802.15.4, IoT, M2M, RT4, Lpt, Internet of Things, Internet da Coisas, Robótica, Cursos C/C++, Domótica, automação residencial, etc

Visit rogercom.com

Key Findings

We analyzed Rogercom.com page load time and found that the first response time was 161 ms and then it took 897 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

rogercom.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

rogercom.com

161 ms

frame2.htm

52 ms

frame1.htm

162 ms

count.js

338 ms

LogoPreto1.gif

56 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 93% of them (37 requests) were addressed to the original Rogercom.com, 8% (3 requests) were made to Count.carrierzone.com. The less responsive or slowest element that took the longest time to load (338 ms) relates to the external source Count.carrierzone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.6 kB (29%)

Content Size

113.9 kB

After Optimization

81.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rogercom.com main page is 113.9 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. 20% of websites need less resources to load. Images take 75.9 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 1.0 kB

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 961 B

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 1.0 kB or 52% of the original size.

Image Optimization

-1%

Potential reduce by 964 B

  • Original 75.9 kB
  • After minification 74.9 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. Rogercom images are well optimized though.

JavaScript Optimization

-85%

Potential reduce by 30.6 kB

  • Original 36.0 kB
  • After minification 23.8 kB
  • After compression 5.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 30.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (15%)

Requests Now

39

After Optimization

33

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

rogercom.com

rogercom.com

161 ms

frame2.htm

frame2.htm

52 ms

frame1.htm

frame1.htm

162 ms

count.js

count.js

338 ms

LogoPreto1.gif

LogoPreto1.gif

56 ms

BarraSepara.gif

BarraSepara.gif

111 ms

Fundo.jpg

Fundo.jpg

68 ms

Botao1.jpg

Botao1.jpg

95 ms

IconZNet.gif

IconZNet.gif

93 ms

IconRcomMeshBee.gif

IconRcomMeshBee.gif

91 ms

banner_treinamento_xbee1.jpg

banner_treinamento_xbee1.jpg

93 ms

icon-control-water.jpg

icon-control-water.jpg

95 ms

facebook_icon.jpg

facebook_icon.jpg

96 ms

IconGravaPen.jpg

IconGravaPen.jpg

133 ms

LPT_Livre.jpg

LPT_Livre.jpg

133 ms

USB_Livre.jpg

USB_Livre.jpg

89 ms

icon_xplus.gif

icon_xplus.gif

92 ms

icon_xbeewifi.gif

icon_xbeewifi.gif

94 ms

Icon_QR_XBeeWiFi.gif

Icon_QR_XBeeWiFi.gif

181 ms

PendriverPIC.gif

PendriverPIC.gif

133 ms

livro_xbee_jadeilson.jpg

livro_xbee_jadeilson.jpg

133 ms

icone-proto-bee.jpg

icone-proto-bee.jpg

134 ms

IconeLpt-Wireless.gif

IconeLpt-Wireless.gif

138 ms

IconeLpt-ID.gif

IconeLpt-ID.gif

142 ms

IconLPT8M.gif

IconLPT8M.gif

177 ms

Icone32es.gif

Icone32es.gif

177 ms

IconeAngulo.gif

IconeAngulo.gif

177 ms

IconeMotor.gif

IconeMotor.gif

184 ms

Dspserver.gif

Dspserver.gif

187 ms

IconeAcesso.gif

IconeAcesso.gif

225 ms

Icone32Entradas.gif

Icone32Entradas.gif

223 ms

IconeLpt32.gif

IconeLpt32.gif

222 ms

IconeVolt.gif

IconeVolt.gif

226 ms

IconeLptwave.gif

IconeLptwave.gif

229 ms

IconeLptgraf.gif

IconeLptgraf.gif

235 ms

IconeDisplay.gif

IconeDisplay.gif

272 ms

IconeDspcom.gif

IconeDspcom.gif

265 ms

IconeLptCont.gif

IconeLptCont.gif

264 ms

ctin.php

ctin.php

151 ms

ctin.php

ctin.php

152 ms

Accessibility Review

rogercom.com accessibility score

85

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

rogercom.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

rogercom.com SEO score

67

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rogercom.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Rogercom.com 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

rogercom.com

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