Tools & Wizards About Us
royalplus.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

royalplus.com

Disaster Cleanup Company | Royal Plus

Page Load Speed

2.5 sec in total

First Response

15 ms

Resources Loaded

1.5 sec

Page Rendered

1.1 sec

royalplus.com screenshot

About Website

Welcome to royalplus.com homepage info - get ready to check Royal Plus best content right away, or after learning these important things about royalplus.com

Royal Plus is here to help with all major emergency natural disaster clean ups and restorations. Contact our disaster cleanup company now for more information.

Visit royalplus.com

Key Findings

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

Performance Metrics

royalplus.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.981

2/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

royalplus.com

15 ms

royalplus.com

939 ms

autoptimize_286b9d01333133a72801b0a39e397929.css

134 ms

jquery.min.js

145 ms

all.css

35 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Royalplus.com, 53% (41 requests) were made to Rzpb7c.a2cdn1.secureserver.net and 39% (30 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (939 ms) belongs to the original domain Royalplus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.1 kB (1%)

Content Size

10.0 MB

After Optimization

9.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalplus.com main page is 10.0 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. Only a small number of websites need less resources to load. Images take 9.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 105.9 kB

  • Original 127.9 kB
  • After minification 127.8 kB
  • After compression 21.9 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 105.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.7 MB
  • After minification 9.7 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. Royal Plus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 24 B

  • Original 127.5 kB
  • After minification 127.5 kB
  • After compression 127.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 92 B

  • Original 49.2 kB
  • After minification 49.2 kB
  • After compression 49.1 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. Royalplus.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (7%)

Requests Now

42

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalplus.com

royalplus.com

15 ms

royalplus.com

royalplus.com

939 ms

autoptimize_286b9d01333133a72801b0a39e397929.css

autoptimize_286b9d01333133a72801b0a39e397929.css

134 ms

jquery.min.js

jquery.min.js

145 ms

all.css

all.css

35 ms

hooks.min.js

hooks.min.js

143 ms

autoptimize_c5a50e2eff97959229c3e98a0a040316.js

autoptimize_c5a50e2eff97959229c3e98a0a040316.js

142 ms

gtm.js

gtm.js

152 ms

new-logo-e1594653723634.png

new-logo-e1594653723634.png

144 ms

RPCATRestorationLogo-01-20221012183317.png

RPCATRestorationLogo-01-20221012183317.png

144 ms

rp-logo_88x68.jpg

rp-logo_88x68.jpg

131 ms

RPCAT-Logo-options_400.png

RPCAT-Logo-options_400.png

130 ms

Royal-Plus_47.jpg

Royal-Plus_47.jpg

170 ms

Royal-Plus_Damage__MG_6850-1-scaled.jpg

Royal-Plus_Damage__MG_6850-1-scaled.jpg

168 ms

Royal-Plusstorm-wind-damage.jpg

Royal-Plusstorm-wind-damage.jpg

151 ms

Royal-Plus_Mold-service.jpg

Royal-Plus_Mold-service.jpg

167 ms

ochmra-copy.png

ochmra-copy.png

168 ms

Salisbury-Chamber-of-Commer-copy.png

Salisbury-Chamber-of-Commer-copy.png

169 ms

Ocean-City-Chamber.png

Ocean-City-Chamber.png

186 ms

NARI-national.png

NARI-national.png

199 ms

NADCABlueLogoAI.png

NADCABlueLogoAI.png

200 ms

mhla-logo.png

mhla-logo.png

185 ms

IICRC_CMYK.png

IICRC_CMYK.png

198 ms

IAQA-Logo.png

IAQA-Logo.png

199 ms

volusia-county-copy.png

volusia-county-copy.png

258 ms

DCMA.png

DCMA.png

262 ms

daytona-regional.png

daytona-regional.png

267 ms

CFHLA.png

CFHLA.png

268 ms

casselberry_chamber_logo-2.png

casselberry_chamber_logo-2.png

263 ms

bomao-orlando-500x173-1.png

bomao-orlando-500x173-1.png

264 ms

bbb-logo.png

bbb-logo.png

269 ms

aia-logo-1443x984-1.png

aia-logo-1443x984-1.png

269 ms

ContractHolder_Number.png

ContractHolder_Number.png

310 ms

Royal-Plus_Circle.png

Royal-Plus_Circle.png

276 ms

RPRPCATUpdatedLogoFOOTER-01-20221012183322.png

RPRPCATUpdatedLogoFOOTER-01-20221012183322.png

270 ms

7.jpg

7.jpg

271 ms

Royal-Plus_Mercy1.jpg

Royal-Plus_Mercy1.jpg

272 ms

Royal-Plus_Safety-Meeting_IMG_6652.jpg

Royal-Plus_Safety-Meeting_IMG_6652.jpg

279 ms

Royal-Plus_Damage_5-scaled.jpg

Royal-Plus_Damage_5-scaled.jpg

280 ms

Royal-Plus_Img23031-1.jpg

Royal-Plus_Img23031-1.jpg

309 ms

RoyalPlus_Arts-Center-picture-32337659-1.jpg

RoyalPlus_Arts-Center-picture-32337659-1.jpg

280 ms

YUN00013.jpg

YUN00013.jpg

312 ms

Royal-Plus_Mast-School5.jpg

Royal-Plus_Mast-School5.jpg

310 ms

Royal-Plus_IMG_6359.jpg

Royal-Plus_IMG_6359.jpg

216 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

64 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

96 ms

S6u9w4BMUTPHh6UVSwaPHw.woff

S6u9w4BMUTPHh6UVSwaPHw.woff

96 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

97 ms

S6u9w4BMUTPHh50XSwaPHw.woff

S6u9w4BMUTPHh50XSwaPHw.woff

96 ms

S6u9w4BMUTPHh50XSwaPHA.ttf

S6u9w4BMUTPHh50XSwaPHA.ttf

148 ms

S6uyw4BMUTPHjxAwWA.woff

S6uyw4BMUTPHjxAwWA.woff

148 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

150 ms

S6u9w4BMUTPHh7USSwaPHw.woff

S6u9w4BMUTPHh7USSwaPHw.woff

149 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

150 ms

S6u8w4BMUTPHh30AUi-s.woff

S6u8w4BMUTPHh30AUi-s.woff

152 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

152 ms

fa-solid-900.woff

fa-solid-900.woff

39 ms

fa-regular-400.woff

fa-regular-400.woff

74 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7ilwQ.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7ilwQ.woff

152 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7ilwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7ilwg.ttf

154 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwQ.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwQ.woff

153 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwg.ttf

155 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwQ.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwQ.woff

155 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwg.ttf

155 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7ilwQ.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7ilwQ.woff

153 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7ilwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7ilwg.ttf

157 ms

modules.woff

modules.woff

185 ms

Accessibility Review

royalplus.com accessibility score

64

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

royalplus.com SEO score

97

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalplus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Royalplus.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

royalplus.com

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