soluckyfish.com website review

19 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

About 104 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

6 third-party services load with your homepage (Privy, Google CDN and Shopify and others), adding 459 KiB and 208 ms of main-thread time.

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

About 23 KiB of CSS is downloaded but never applied on this page.

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

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

Your largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Leaping Tigers Charcoal Muscle Tank”.

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

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

The layout shifts by 0.214 while loading, so content jumps under the reader's thumb. Good is under 0.1.

41 images have no width and height attributes, so the layout jumps as each one loads.

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.5 MB in 212 requests on a phone: images 3.0 MB (59), other files 796 KiB (103) and scripts 512 KiB (40). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

8 tap targets are too small or too close together to hit reliably with a finger.

5 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

6 visible links have no text or label, so screen readers cannot say where they go.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

3 elements have a tabindex above 0, which scrambles the keyboard order.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

Your title is only 10 characters: “Lucky Fish”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 8 <h1> headlines (“Women”, “Men / Unisex” and “Baby”). One clear main headline is easier for people and search engines.

The homepage links to 126 pages on soluckyfish.com and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://soluckyfish.com/collections/womens, https://soluckyfish.com/collections/mens, https://soluckyfish.com/collections/tween, https://soluckyfish.com/collections/boys, https://soluckyfish.com/collections/babys and https://soluckyfish.com/collections/products/Clothing and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://soluckyfish.com/collections/products/Clothing, whose canonical is https://soluckyfish.com/collections/products/clothing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://soluckyfish.com/collections/bags has 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 68 found) and read each the way a search engine does.

33 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 128 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 Analytics, Google Tag Manager and Pinterest Tag (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 10 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.