Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

secure.stansberryresearch.com

Stansberry Research

Page Load Speed

1.2 sec in total

First Response

354 ms

Resources Loaded

757 ms

Page Rendered

102 ms

secure.stansberryresearch.com screenshot

About Website

Click here to check amazing Secure Stansberry Research content for United States. Otherwise, check out these important facts you probably never knew about secure.stansberryresearch.com

Everything you need to successfully invest including real time data from the NYSE, Nasdaq and BATS exchanges, streaming articles from 20+ publications, highlighted Stansberry Research recommendations,...

Visit secure.stansberryresearch.com

Key Findings

We analyzed Secure.stansberryresearch.com page load time and found that the first response time was 354 ms and then it took 859 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

secure.stansberryresearch.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

354 ms

cloudflare.min.js

8 ms

css

81 ms

dashicons.min.css

33 ms

wp-admin.min.css

43 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Secure.stansberryresearch.com, 9% (1 request) were made to Ajax.cloudflare.com and 9% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (354 ms) relates to the external source Stansberryresearch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.6 kB (69%)

Content Size

329.2 kB

After Optimization

103.6 kB

In fact, the total size of Secure.stansberryresearch.com main page is 329.2 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. 30% of websites need less resources to load. CSS take 299.9 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.3 kB

  • Original 5.5 kB
  • After minification 5.1 kB
  • After compression 2.2 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 3.3 kB or 61% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.1 kB
  • After minification 5.1 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. Secure Stansberry Research images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 128 B

  • Original 18.7 kB
  • After minification 18.7 kB
  • After compression 18.6 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

-74%

Potential reduce by 222.1 kB

  • Original 299.9 kB
  • After minification 298.6 kB
  • After compression 77.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. Secure.stansberryresearch.com needs all CSS files to be minified and compressed as it can save up to 222.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

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

Accessibility Review

secure.stansberryresearch.com accessibility score

60

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.

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 IDs 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

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

secure.stansberryresearch.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

secure.stansberryresearch.com SEO score

79

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

High

Page is blocked from indexing

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

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 Secure.stansberryresearch.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 Secure.stansberryresearch.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

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