Tools & Wizards About Us
moby.co screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

moby.co

Try Moby

Page Load Speed

2 sec in total

First Response

111 ms

Resources Loaded

1.2 sec

Page Rendered

627 ms

moby.co screenshot

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 111 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

moby.co performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value10,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.188

65/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

moby.co

111 ms

www.moby.co

225 ms

styles.css

119 ms

css

112 ms

core-4d08d258547af8a29fc4738e545ca8e26d95e11b829a9db5a0b36d047fb91843.css

111 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Moby.co, 48% (16 requests) were made to Kajabi-storefronts-production.kajabi-cdn.com and 6% (2 requests) were made to Kajabi-app-assets.kajabi-cdn.com. The less responsive or slowest element that took the longest time to load (790 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.1 kB (25%)

Content Size

718.4 kB

After Optimization

535.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Moby.co main page is 718.4 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. 70% of websites need less resources to load. Images take 367.8 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 162.7 kB

  • Original 179.7 kB
  • After minification 172.4 kB
  • After compression 17.0 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 162.7 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 4.5 kB

  • Original 367.8 kB
  • After minification 363.3 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. Moby images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 15.5 kB

  • Original 144.1 kB
  • After minification 144.1 kB
  • After compression 128.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 15.5 kB or 11% of the original size.

CSS Optimization

-2%

Potential reduce by 493 B

  • Original 26.7 kB
  • After minification 26.7 kB
  • After compression 26.2 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 12 (43%)

Requests Now

28

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 28 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 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

moby.co

moby.co

111 ms

www.moby.co

www.moby.co

225 ms

styles.css

styles.css

119 ms

css

css

112 ms

core-4d08d258547af8a29fc4738e545ca8e26d95e11b829a9db5a0b36d047fb91843.css

core-4d08d258547af8a29fc4738e545ca8e26d95e11b829a9db5a0b36d047fb91843.css

111 ms

all.css

all.css

313 ms

js

js

360 ms

dotlottie-player.mjs

dotlottie-player.mjs

110 ms

commonninja.js

commonninja.js

99 ms

platform.js

platform.js

104 ms

encore_core-f4735cadef603151d28ba781c6a9b7e0fbd3e895347360bf76166481afeacf15.js

encore_core-f4735cadef603151d28ba781c6a9b7e0fbd3e895347360bf76166481afeacf15.js

354 ms

scripts.js

scripts.js

354 ms

gtm.js

gtm.js

472 ms

polyfill.min.js

polyfill.min.js

790 ms

fbevents.js

fbevents.js

583 ms

18apDziHN6JdlwyIjqHdSjgVDOdzCcezL

18apDziHN6JdlwyIjqHdSjgVDOdzCcezL

686 ms

aa12a78-73c-0822-715-41f777417ef5_Moby_Black.png

aa12a78-73c-0822-715-41f777417ef5_Moby_Black.png

329 ms

43f8464-e1c8-7e51-00db-33df2c1c86a5_Untitled_design_5_.png

43f8464-e1c8-7e51-00db-33df2c1c86a5_Untitled_design_5_.png

329 ms

e22878c-3bae-4740-bc13-66bc7ed53c6_e041812-61-b4d6-671-0a8eb4f5e756_APP_STORE.webp

e22878c-3bae-4740-bc13-66bc7ed53c6_e041812-61-b4d6-671-0a8eb4f5e756_APP_STORE.webp

361 ms

32544ed-0a80-ccf1-b08f-8a1b2e8817a_07fa2bec-ebe5-40a4-a20a-c0446fbdd95b.webp

32544ed-0a80-ccf1-b08f-8a1b2e8817a_07fa2bec-ebe5-40a4-a20a-c0446fbdd95b.webp

361 ms

background.jpg

background.jpg

483 ms

ce0ba1d-12-3cb-f42d-337f66db6a0_Untitled_design_6_.png

ce0ba1d-12-3cb-f42d-337f66db6a0_Untitled_design_6_.png

361 ms

be4ef-3138-28c5-488b-c0c36efe543_Untitled_design_3_.png

be4ef-3138-28c5-488b-c0c36efe543_Untitled_design_3_.png

480 ms

7b57478-e62b-c77-af1-f020c1e85546_Moby_Blue.png

7b57478-e62b-c77-af1-f020c1e85546_Moby_Blue.png

361 ms

placeholder.png

placeholder.png

479 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

483 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

484 ms

0b0c6d2-d0dc-27d-53e7-d16d204c5dc8_Untitled_design_7_.png

0b0c6d2-d0dc-27d-53e7-d16d204c5dc8_Untitled_design_7_.png

392 ms

16847d8-18a4-eb8e-0f5c-dc45604341cc_f8d289e4-1174-49ad-b12f-73d9c8be1474.png

16847d8-18a4-eb8e-0f5c-dc45604341cc_f8d289e4-1174-49ad-b12f-73d9c8be1474.png

352 ms

b31bef3-578-3c1c-10e5-a20c2f5d54a2_Untitled_design_8_.png

b31bef3-578-3c1c-10e5-a20c2f5d54a2_Untitled_design_8_.png

314 ms

5623ed-8762-4b3f-c6f1-3fb7dca6a2d_Untitled_design_8_.png

5623ed-8762-4b3f-c6f1-3fb7dca6a2d_Untitled_design_8_.png

356 ms

fa-brands-400.woff

fa-brands-400.woff

122 ms

overrides.css

overrides.css

25 ms

Accessibility Review

moby.co accessibility score

96

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

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

100

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

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

moby.co

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: