Tools & Wizards About Us
r-o.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

r-o.com

Texas’ Premier Builder and General Contractor for Commercial Construction

Page Load Speed

3.2 sec in total

First Response

235 ms

Resources Loaded

1.6 sec

Page Rendered

1.4 sec

r-o.com screenshot

About Website

Welcome to r-o.com homepage info - get ready to check R O best content right away, or after learning these important things about r-o.com

Since 1969, Rogers-O’Brien has firmly established itself in the commercial construction industry as Texas’ Premier Builder and General Contractor by providing a wide range of preconstruction and const...

Visit r-o.com

Key Findings

We analyzed R-o.com page load time and found that the first response time was 235 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

r-o.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

r-o.com

235 ms

jquery-3.5.0.js

155 ms

vjt8vez.js

104 ms

icon

55 ms

picturefill.min.js

71 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 57% of them (43 requests) were addressed to the original R-o.com, 21% (16 requests) were made to Player.vimeo.com and 7% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (539 ms) relates to the external source Player.vimeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.2 kB (9%)

Content Size

1.1 MB

After Optimization

954.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of R-o.com main page is 1.1 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 794.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 86.3 kB

  • Original 100.6 kB
  • After minification 88.9 kB
  • After compression 14.3 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. This page needs HTML code to be minified as it can gain 11.7 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 86.3 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 4.3 kB

  • Original 794.9 kB
  • After minification 790.6 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. R O images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 4.1 kB

  • Original 112.1 kB
  • After minification 112.1 kB
  • After compression 108.0 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

-6%

Potential reduce by 2.5 kB

  • Original 44.4 kB
  • After minification 44.4 kB
  • After compression 42.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. R-o.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (57%)

Requests Now

44

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

r-o.com

r-o.com

235 ms

jquery-3.5.0.js

jquery-3.5.0.js

155 ms

vjt8vez.js

vjt8vez.js

104 ms

icon

icon

55 ms

picturefill.min.js

picturefill.min.js

71 ms

slick.css

slick.css

73 ms

slick-theme.css

slick-theme.css

74 ms

slick.js

slick.js

117 ms

player.js

player.js

56 ms

common.v-3.3.js

common.v-3.3.js

84 ms

home.js

home.js

98 ms

insight.min.js

insight.min.js

243 ms

homevideo_view.jpg

homevideo_view.jpg

127 ms

923373414

923373414

21 ms

923370653

923370653

22 ms

410239577

410239577

22 ms

410237437

410237437

21 ms

923372230

923372230

20 ms

rogers-obrien.v2.svg

rogers-obrien.v2.svg

195 ms

thumb.jpg

thumb.jpg

302 ms

ro-tag.v5.png

ro-tag.v5.png

342 ms

play.v1.png

play.v1.png

342 ms

banner-triangles.v1.png

banner-triangles.v1.png

341 ms

banner-triangles-reverse.v1.png

banner-triangles-reverse.v1.png

373 ms

safety-ph.v1.png

safety-ph.v1.png

372 ms

ph.v1.png

ph.v1.png

373 ms

better-way-ph.v1.png

better-way-ph.v1.png

406 ms

923373414

923373414

5 ms

923370653

923370653

4 ms

410239577

410239577

3 ms

410237437

410237437

3 ms

923372230

923372230

2 ms

923373414

923373414

442 ms

923370653

923370653

482 ms

410239577

410239577

434 ms

410237437

410237437

539 ms

923372230

923372230

478 ms

ajax-loader.gif

ajax-loader.gif

144 ms

placeholder.v1.png

placeholder.v1.png

346 ms

placeholder.v1.png

placeholder.v1.png

348 ms

citadel-group.v4.svg

citadel-group.v4.svg

134 ms

slant.svg

slant.svg

135 ms

ph.v1.png

ph.v1.png

136 ms

bliss-medium-webfont.woff

bliss-medium-webfont.woff

209 ms

scrap-social-feed

scrap-social-feed

414 ms

2fcrYFNaTjcS6g4U3t-Y5StnKWgpfO2iSkLzTz-AABg.ttf

2fcrYFNaTjcS6g4U3t-Y5StnKWgpfO2iSkLzTz-AABg.ttf

184 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNa.woff

flUhRq6tzZclQEJ-Vdg-IuiaDsNa.woff

206 ms

citadel-group-white.svg

citadel-group-white.svg

89 ms

slant-white.svg

slant-white.svg

95 ms

d

d

39 ms

d

d

42 ms

d

d

132 ms

d

d

136 ms

building-texas-xwide.v1.jpg

building-texas-xwide.v1.jpg

477 ms

insight_tag_errors.gif

insight_tag_errors.gif

101 ms

p.gif

p.gif

25 ms

1815577036-851f0db922990f6c84f96ccd4051d885908e0bfc29f026e3080c6f880cf9fd5b-d

1815577036-851f0db922990f6c84f96ccd4051d885908e0bfc29f026e3080c6f880cf9fd5b-d

64 ms

1815373590-0c7cf725d3c0332c444522b928c0aedbce7643b65e05f73c861419a0d8f4f9e0-d

1815373590-0c7cf725d3c0332c444522b928c0aedbce7643b65e05f73c861419a0d8f4f9e0-d

44 ms

api.js

api.js

15 ms

1815376212-93846a1e1859355adebaf8ebd68f3e03c9975ae7e8a49cfdbd37b77343129fa6-d

1815376212-93846a1e1859355adebaf8ebd68f3e03c9975ae7e8a49cfdbd37b77343129fa6-d

44 ms

style-list.css

style-list.css

45 ms

border-vertical-tight.v1.png

border-vertical-tight.v1.png

44 ms

cursor.v1.png

cursor.v1.png

43 ms

border-vertical.png

border-vertical.png

44 ms

border-horizontal.png

border-horizontal.png

43 ms

bg.v1.jpg

bg.v1.jpg

165 ms

border-white-horizontal.v1.png

border-white-horizontal.v1.png

74 ms

bliss-medium-webfont.woff

bliss-medium-webfont.woff

37 ms

TrumpSoftPro.woff

TrumpSoftPro.woff

255 ms

daniel-bold-webfont.woff

daniel-bold-webfont.woff

75 ms

MyriadPro-Regular.woff

MyriadPro-Regular.woff

127 ms

slick.woff

slick.woff

106 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

127 ms

slick.ttf

slick.ttf

64 ms

slick.svg

slick.svg

69 ms

Accessibility Review

r-o.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

r-o.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

r-o.com SEO score

90

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R-o.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that R-o.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

r-o.com

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