Tools & Wizards About Us
royaltyseo.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

royaltyseo.com

Best SEO Company | Internet Marketing | Fort Lauderdale | Miami | Florida

Page Load Speed

6.7 sec in total

First Response

753 ms

Resources Loaded

5.7 sec

Page Rendered

298 ms

royaltyseo.com screenshot

About Website

Click here to check amazing Royalty SEO content. Otherwise, check out these important facts you probably never knew about royaltyseo.com

Royalty SEO is the best SEO company in Fort Lauderdale. We are a full service internet marketing, SEO and web design company.

Visit royaltyseo.com

Key Findings

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

Performance Metrics

royaltyseo.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value21.3 s

0/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

www.royaltyseo.com

753 ms

jquery-latest.min.js

8 ms

style.min.css

230 ms

styles.css

453 ms

foobox.free.min.css

461 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 89% of them (50 requests) were addressed to the original Royaltyseo.com, 7% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Royaltyseo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.8 kB (30%)

Content Size

1.3 MB

After Optimization

883.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaltyseo.com main page is 1.3 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 923.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 60.7 kB

  • Original 76.8 kB
  • After minification 75.7 kB
  • After compression 16.1 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 60.7 kB or 79% of the original size.

Image Optimization

-32%

Potential reduce by 292.8 kB

  • Original 923.4 kB
  • After minification 630.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. Obviously, Royalty SEO needs image optimization as it can save up to 292.8 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 2.8 kB

  • Original 177.9 kB
  • After minification 177.9 kB
  • After compression 175.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

-18%

Potential reduce by 13.4 kB

  • Original 74.9 kB
  • After minification 74.9 kB
  • After compression 61.5 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. Royaltyseo.com needs all CSS files to be minified and compressed as it can save up to 13.4 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (68%)

Requests Now

50

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.royaltyseo.com

www.royaltyseo.com

753 ms

jquery-latest.min.js

jquery-latest.min.js

8 ms

style.min.css

style.min.css

230 ms

styles.css

styles.css

453 ms

foobox.free.min.css

foobox.free.min.css

461 ms

prettyPhoto.css

prettyPhoto.css

464 ms

settings.css

settings.css

473 ms

wp-core.css

wp-core.css

467 ms

foundation-scss.css

foundation-scss.css

474 ms

foundation-ie8.css

foundation-ie8.css

678 ms

icomoon.css

icomoon.css

687 ms

font-awesome.min.css

font-awesome.min.css

695 ms

buttons.css

buttons.css

700 ms

style.css

style.css

706 ms

menu-ltr.css

menu-ltr.css

710 ms

media-queries.css

media-queries.css

905 ms

animate.css

animate.css

914 ms

anything-popup.js

anything-popup.js

926 ms

jquery.min.js

jquery.min.js

940 ms

jquery-migrate.min.js

jquery-migrate.min.js

937 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

955 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1137 ms

modernizr.js

modernizr.js

1141 ms

jquery-parallax-set.min.js

jquery-parallax-set.min.js

1159 ms

rockthemes-parallax.min.js

rockthemes-parallax.min.js

1170 ms

quasar.jquery.min.js

quasar.jquery.min.js

1174 ms

jquery.navgoco.min.js

jquery.navgoco.min.js

1191 ms

foobox.free.min.js

foobox.free.min.js

1370 ms

css

css

57 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1416 ms

wp-polyfill.min.js

wp-polyfill.min.js

1416 ms

index.js

index.js

1416 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1417 ms

jquery.color.min.js

jquery.color.min.js

1460 ms

effect.min.js

effect.min.js

1595 ms

wp-embed.min.js

wp-embed.min.js

1599 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1641 ms

LOGO3_V2.png

LOGO3_V2.png

482 ms

new_banners_3-1.jpg

new_banners_3-1.jpg

735 ms

new_banners_1-1.jpg

new_banners_1-1.jpg

752 ms

new_banners_2-1.jpg

new_banners_2-1.jpg

1116 ms

tes_1.png

tes_1.png

450 ms

tes_2.png

tes_2.png

477 ms

tes_3.png

tes_3.png

678 ms

tes_4.png

tes_4.png

707 ms

shadow-divider-up.png

shadow-divider-up.png

716 ms

wordpress_icon.png

wordpress_icon.png

905 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e2fwniDhzA.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e2fwniDhzA.ttf

77 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e2fwniDhzA.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e2fwniDhzA.ttf

110 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxlqHrzJYAA.ttf

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxlqHrzJYAA.ttf

139 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG089z4eqVxlqHrzJYAA.ttf

7Aujp_0qiz-afTfcIyoiGtm2P0wG089z4eqVxlqHrzJYAA.ttf

132 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

857 ms

select_arrow_down.png

select_arrow_down.png

655 ms

loader.gif

loader.gif

673 ms

small_left.png

small_left.png

689 ms

small_right.png

small_right.png

832 ms

Accessibility Review

royaltyseo.com accessibility score

85

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

royaltyseo.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

royaltyseo.com SEO score

83

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royaltyseo.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 Royaltyseo.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

royaltyseo.com

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