Tools & Wizards About Us
captainrjshelly.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

captainrjshelly.com

Page Load Speed

1.4 sec in total

First Response

59 ms

Resources Loaded

1.2 sec

Page Rendered

105 ms

captainrjshelly.com screenshot

About Website

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

Port O'Connor fishing guides, Capt RJ Shelly is known for his high octane fishing trips. If huge redfish, trout & flounder are your style, come fish POC!

Visit captainrjshelly.com

Key Findings

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

Performance Metrics

captainrjshelly.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

captainrjshelly.com

59 ms

site

22 ms

615 ms

wp-emoji-release.min.js

25 ms

dashicons.min.css

59 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Captainrjshelly.com, 3% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (615 ms) belongs to the original domain Captainrjshelly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.7 kB (40%)

Content Size

712.3 kB

After Optimization

429.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Captainrjshelly.com main page is 712.3 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. 45% of websites need less resources to load. Javascripts take 513.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 23.9 kB

  • Original 30.0 kB
  • After minification 28.3 kB
  • After compression 6.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 23.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 28 B

  • Original 57.6 kB
  • After minification 57.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. Captainrjshelly images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 232.4 kB

  • Original 513.6 kB
  • After minification 513.6 kB
  • After compression 281.2 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 232.4 kB or 45% of the original size.

CSS Optimization

-24%

Potential reduce by 26.4 kB

  • Original 111.0 kB
  • After minification 111.0 kB
  • After compression 84.7 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. Captainrjshelly.com needs all CSS files to be minified and compressed as it can save up to 26.4 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (87%)

Requests Now

55

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

captainrjshelly.com

captainrjshelly.com

59 ms

site

site

22 ms

615 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

25 ms

dashicons.min.css

dashicons.min.css

59 ms

wunderground.css

wunderground.css

45 ms

style.min.css

style.min.css

47 ms

styles.css

styles.css

259 ms

frontend.min.css

frontend.min.css

50 ms

css

css

36 ms

owl.carousel.css

owl.carousel.css

43 ms

lightgallery.css

lightgallery.css

63 ms

fontello.css

fontello.css

62 ms

style.css

style.css

79 ms

supersized.css

supersized.css

66 ms

jplayer.css

jplayer.css

77 ms

lg-transitions.min.css

lg-transitions.min.css

85 ms

light-style.css

light-style.css

89 ms

jquery.min.js

jquery.min.js

116 ms

jquery-migrate.min.js

jquery-migrate.min.js

96 ms

core.min.js

core.min.js

98 ms

menu.min.js

menu.min.js

100 ms

wp-polyfill.min.js

wp-polyfill.min.js

124 ms

dom-ready.min.js

dom-ready.min.js

114 ms

i18n.min.js

i18n.min.js

116 ms

a11y.min.js

a11y.min.js

118 ms

autocomplete.min.js

autocomplete.min.js

133 ms

widget.min.js

widget.min.js

135 ms

js

js

86 ms

lodash.min.js

lodash.min.js

137 ms

url.min.js

url.min.js

154 ms

hooks.min.js

hooks.min.js

142 ms

api-fetch.min.js

api-fetch.min.js

155 ms

index.js

index.js

308 ms

tabs.min.js

tabs.min.js

155 ms

modernizr-custom.js

modernizr-custom.js

160 ms

jquery.transit.min.js

jquery.transit.min.js

173 ms

hammer.min.js

hammer.min.js

174 ms

jquery.tipsy.js

jquery.tipsy.js

175 ms

lightgallery-all.min.js

lightgallery-all.min.js

182 ms

jquery.mtree.js

jquery.mtree.js

192 ms

velocity.min.js

velocity.min.js

176 ms

comment-reply.min.js

comment-reply.min.js

159 ms

jquery.supersized.js

jquery.supersized.js

166 ms

jquery.supersized.shutter.min.js

jquery.supersized.shutter.min.js

168 ms

jquery.custom.js

jquery.custom.js

170 ms

lazysizes.min.js

lazysizes.min.js

160 ms

wp-embed.min.js

wp-embed.min.js

165 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

23 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

20 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

26 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

24 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

20 ms

bg_pattern_1.png

bg_pattern_1.png

52 ms

CaptRJShelly-PortOConnor.jpg

CaptRJShelly-PortOConnor.jpg

50 ms

full_scrt_l.gif

full_scrt_l.gif

51 ms

port-oconnor-fishing-guides-captain-rj-shelly.jpg

port-oconnor-fishing-guides-captain-rj-shelly.jpg

51 ms

bg_preloader.gif

bg_preloader.gif

20 ms

font

font

19 ms

font

font

104 ms

Accessibility Review

captainrjshelly.com accessibility score

74

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

Image elements do not have [alt] attributes

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

captainrjshelly.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

captainrjshelly.com SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

captainrjshelly.com

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