Tools & Wizards About Us
roix.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

roix.com

GDB | SafeMedia

Page Load Speed

3.9 sec in total

First Response

19 ms

Resources Loaded

2.9 sec

Page Rendered

949 ms

roix.com screenshot

About Website

Visit roix.com now to see the best up-to-date Roix content and also check out these interesting facts you probably never knew about roix.com

Visit roix.com

Key Findings

We analyzed Roix.com page load time and found that the first response time was 19 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

roix.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.42

23/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

roix.com

19 ms

gdb.net

911 ms

custom.css

105 ms

styles.css

157 ms

ivory-search.min.css

158 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Roix.com, 69% (45 requests) were made to Gdb.net and 18% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cmpcdn.gdb.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 507.1 kB (11%)

Content Size

4.8 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Roix.com main page is 4.8 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. 55% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 126.7 kB

  • Original 154.1 kB
  • After minification 151.4 kB
  • After compression 27.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 126.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 23.1 kB

  • Original 3.9 MB
  • After minification 3.9 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. Roix images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 356.4 kB

  • Original 698.3 kB
  • After minification 698.3 kB
  • After compression 341.9 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 356.4 kB or 51% of the original size.

CSS Optimization

-9%

Potential reduce by 867 B

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 9.0 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. Roix.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

roix.com

roix.com

19 ms

gdb.net

gdb.net

911 ms

custom.css

custom.css

105 ms

styles.css

styles.css

157 ms

ivory-search.min.css

ivory-search.min.css

158 ms

css

css

32 ms

css

css

20 ms

ivory-ajax-search.min.css

ivory-ajax-search.min.css

108 ms

jquery.min.js

jquery.min.js

168 ms

jquery-migrate.min.js

jquery-migrate.min.js

160 ms

jquery.mask.js

jquery.mask.js

159 ms

master.js

master.js

161 ms

hooks.min.js

hooks.min.js

166 ms

i18n.min.js

i18n.min.js

167 ms

index.js

index.js

216 ms

index.js

index.js

216 ms

scripts.min.js

scripts.min.js

327 ms

jquery.fitvids.js

jquery.fitvids.js

219 ms

jquery.mobile.js

jquery.mobile.js

220 ms

common.js

common.js

227 ms

ivory-search.min.js

ivory-search.min.js

267 ms

ivory-ajax-search.min.js

ivory-ajax-search.min.js

320 ms

motion-effects.js

motion-effects.js

359 ms

sticky-elements.js

sticky-elements.js

359 ms

cmp.php

cmp.php

444 ms

cmp_en.min.js

cmp_en.min.js

1496 ms

et-divi-dynamic-tb-13-tb-20-48-late.css

et-divi-dynamic-tb-13-tb-20-48-late.css

157 ms

logo-gdb.svg

logo-gdb.svg

348 ms

spinner.gif

spinner.gif

349 ms

search.svg

search.svg

344 ms

social-linkedin.svg

social-linkedin.svg

345 ms

social-instagram.svg

social-instagram.svg

346 ms

iStock-1338846836-scaled.jpg

iStock-1338846836-scaled.jpg

410 ms

grafismo2.svg

grafismo2.svg

349 ms

grafismo1.svg

grafismo1.svg

350 ms

img-ctv.png

img-ctv.png

472 ms

img-carbon-free.png

img-carbon-free.png

630 ms

img-video.png

img-video.png

571 ms

img-audio.png

img-audio.png

580 ms

img-display.png

img-display.png

619 ms

img-native.png

img-native.png

517 ms

grafismo3.svg

grafismo3.svg

521 ms

triangle.svg

triangle.svg

573 ms

triangle-pink.svg

triangle-pink.svg

579 ms

triangle-left.svg

triangle-left.svg

627 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nmjpw.ttf

22 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nmjpw.ttf

29 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8fvx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8fvx1nmjpw.ttf

36 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nmjpw.ttf

41 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8aXx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8aXx1nmjpw.ttf

40 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nmjpw.ttf

45 ms

object2.svg

object2.svg

624 ms

logo-gdb-white.svg

logo-gdb-white.svg

604 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

9 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

12 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

5 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

9 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

9 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

13 ms

arrow-left.svg

arrow-left.svg

294 ms

arrow-right.svg

arrow-right.svg

339 ms

modules.woff

modules.woff

333 ms

cmp.php

cmp.php

415 ms

cmp.php

cmp.php

132 ms

bV8xLndfNjE0ODMucl9HRFBSLmxfZW4uZF8yMjcyNy54XzEyLnYucC50XzIyNzI3Lnh0XzU.js

bV8xLndfNjE0ODMucl9HRFBSLmxfZW4uZF8yMjcyNy54XzEyLnYucC50XzIyNzI3Lnh0XzU.js

873 ms

Accessibility Review

roix.com accessibility score

89

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

roix.com best practices score

75

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

Low

Detected JavaScript libraries

SEO Factors

roix.com SEO score

90

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Roix.com 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 Roix.com 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

roix.com

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