rocketsofawesome.com website review

A phone's processor spends 5.4 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Clarity, Shopify and Klaviyo and others), adding 875 KiB and 825 ms of main-thread time.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Clarity costs a phone 292 ms of main-thread work and 30 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

9 images could be 288 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Shopify costs a phone 215 ms of main-thread work and 418 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,761 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 220 ms faster on a phone.

8 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.

18 files are served with short cache lifetimes, so returning visitors download them again (108 KiB).

About 66 KiB of JavaScript is downloaded but never used on this page.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

12 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

The page becomes fully interactive after 11.2 s. Good is under 3.8 s.

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.

Your homepage downloads 2.9 MB in 374 requests on a phone: scripts 991 KiB (175), other files 918 KiB (159) and images 720 KiB (16). Under 2 MB keeps phones on slow connections fast.

dotty-cardigan.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example ROA-SET-B10-2.jpg at 1,000 px wide, shown at 325 px. Resized copies would save about 6 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (2 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 246 pages on rocketsofawesome.com and 3 external pages.

https://www.mightly.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.mightly.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.mightly.com/customer_authentication/redirect, https://www.mightly.com/collections/shop-all-1/division:GIRLS+size-group:KIDS, https://www.mightly.com/collections/dresses-jumpsuits, https://www.mightly.com/collections/kids-shorts-skorts-skirts/division:GIRLS, https://www.mightly.com/collections/all-tees-and-tops/division:GIRLS+type:TOPS and https://www.mightly.com/collections/kids-bottoms/division:GIRLS+size-group:KIDS+collection:pants and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.mightly.com/collections/shop-all-1/division:GIRLS+size-group:KIDS, whose canonical is https://www.mightly.com/collections/shop-all-1/division:girls+size-group:kids. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mightly.com/customer_authentication/redirect, https://www.mightly.com/collections/shop-all-1/division:GIRLS+size-group:KIDS, https://www.mightly.com/collections/dresses-jumpsuits, https://www.mightly.com/collections/kids-shorts-skorts-skirts/division:GIRLS, https://www.mightly.com/collections/all-tees-and-tops/division:GIRLS+type:TOPS and https://www.mightly.com/collections/kids-leggings-toddlers-girls and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/, https://www.mightly.com/collections/shop-all-1/division:GIRLS+size-group:KIDS, https://www.mightly.com/collections/all-tees-and-tops/division:GIRLS+type:TOPS, https://www.mightly.com/collections/kids-skin-care-natural and https://www.mightly.com/collections/all-tees-and-tops/division:GIRLS+size-group:KIDS have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 112 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 114 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 22 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.