Tools & Wizards About Us
rpluce.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

rpluce.com

Custom Equipment Cases | Pelican Cases | Carrying Cases

Page Load Speed

2.2 sec in total

First Response

59 ms

Resources Loaded

1.4 sec

Page Rendered

739 ms

rpluce.com screenshot

About Website

Click here to check amazing Rpluce content. Otherwise, check out these important facts you probably never knew about rpluce.com

Serving our customers exclusive needs for over 50 years, R.P. Luce provides the industry's most rugged and customized Pelican and Zarges case products.

Visit rpluce.com

Key Findings

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

Performance Metrics

rpluce.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

rpluce.com

59 ms

www.rpluce.com

355 ms

js

118 ms

loading.gif

24 ms

plusone.js

25 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 43% of them (10 requests) were addressed to the original Rpluce.com, 26% (6 requests) were made to Apis.google.com and 9% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (863 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 692.5 kB (46%)

Content Size

1.5 MB

After Optimization

829.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rpluce.com main page is 1.5 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. 30% of websites need less resources to load. HTML takes 925.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 691.9 kB

  • Original 925.2 kB
  • After minification 919.0 kB
  • After compression 233.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. 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 691.9 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 155 B

  • Original 423.1 kB
  • After minification 423.0 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. Rpluce images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 459 B

  • Original 173.5 kB
  • After minification 173.5 kB
  • After compression 173.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.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • AJAX
  • Images
  • JavaScript

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rpluce. 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 as a result speed up the page load time.

Network Requests Diagram

rpluce.com

rpluce.com

59 ms

www.rpluce.com

www.rpluce.com

355 ms

js

js

118 ms

loading.gif

loading.gif

24 ms

plusone.js

plusone.js

25 ms

pixel_trans.gif

pixel_trans.gif

18 ms

account_icon.png

account_icon.png

55 ms

search_icon.png

search_icon.png

92 ms

8fb6d8e7d246bf3115ba7e0035b0f707.thumb.webp

8fb6d8e7d246bf3115ba7e0035b0f707.thumb.webp

236 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

30 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

fastbutton

fastbutton

40 ms

homepage_tanks.jpg

homepage_tanks.jpg

270 ms

industries_served.jpg

industries_served.jpg

222 ms

postmessageRelay

postmessageRelay

176 ms

developers.google.com

developers.google.com

863 ms

js

js

77 ms

analytics.js

analytics.js

29 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

38 ms

collect

collect

22 ms

1380534674-postmessagerelay.js

1380534674-postmessagerelay.js

135 ms

rpc:shindig_random.js

rpc:shindig_random.js

123 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

Accessibility Review

rpluce.com accessibility score

93

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

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

High

Links do not have a discernible name

Best Practices

rpluce.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

rpluce.com SEO score

91

Search Engine Optimization Advices

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

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

rpluce.com

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