Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

moby.co

Try Moby

Page Load Speed

4 sec in total

First Response

153 ms

Resources Loaded

3.3 sec

Page Rendered

516 ms

About Website

Welcome to moby.co homepage info - get ready to check Moby best content for United States right away, or after learning these important things about moby.co

Join over 5 million people making better investments. For investors of every level. Our research is loved by beginners, billionaires, and everyone in between.

Visit moby.co

Key Findings

We analyzed Moby.co page load time and found that the first response time was 153 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

moby.co performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.356

31/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

www.moby.co

153 ms

css

70 ms

core-39d7ec8c864adbae305102afb66be7486f2dfa14daf2042501bc27b46117fc72.css

74 ms

all.css

156 ms

styles.css

89 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Moby.co, 39% (16 requests) were made to Kajabi-storefronts-production.kajabi-cdn.com and 10% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source S6.gifyu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.7 kB (8%)

Content Size

3.0 MB

After Optimization

2.8 MB

In fact, the total size of Moby.co main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 232.9 kB

  • Original 258.7 kB
  • After minification 248.7 kB
  • After compression 25.8 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 232.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.4 MB
  • After minification 2.4 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. Moby images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 300 B

  • Original 343.0 kB
  • After minification 343.0 kB
  • After compression 342.7 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

-2%

Potential reduce by 466 B

  • Original 26.2 kB
  • After minification 26.1 kB
  • After compression 25.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. Moby.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (52%)

Requests Now

33

After Optimization

16

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

Accessibility Review

moby.co accessibility score

92

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

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

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

Best Practices

moby.co best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

moby.co SEO score

99

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 Moby.co 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 Moby.co 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 data is detected on the main page of Moby. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: