comebackkid-us.com website review

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

About 743 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

About 286 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

8 third-party services load with your homepage (YouTube, Shopify and Klaviyo and others), adding 9.3 MB and 892 ms of main-thread time.

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

Shopify costs a phone 170 ms of main-thread work and 7.4 MB 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.

105 KiB could be saved by minifying CSS.

YouTube costs a phone 440 ms of main-thread work and 1,016 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.

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

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

Klaviyo costs a phone 127 ms of main-thread work and 328 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.

avada.io costs a phone 96 ms of main-thread work and 362 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.

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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 66.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our 1037 partners process data that concerns you. We…”.

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

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

Scripts block taps and scrolling for 269 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 120 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.6 MB in 361 requests on a phone: images 9.0 MB (25), scripts 1.9 MB (89) and other files 1.3 MB (230). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 53c57774-230b-49e8-8aaa-68a9089689ed.jpeg at 1,482 px wide, shown at 239 px. Resized copies would save about 53 KiB.

3 images (229 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 48 pages on comebackkid-us.com and 10 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://comebackkid-us.com/collections/all-products, https://comebackkid-us.com/collections/apparel-1, https://comebackkid-us.com/collections/accessories, https://comebackkid-us.com/collections/music, https://comebackkid-us.com/collections/sale and https://comebackkid-us.com/pages/contact-us and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://comebackkid-us.com/products/chosen-hell-12-vinyl-glow-in-the-dark-black-split and https://comebackkid-us.com/products/chosen-hell-12-vinyl-red-transparent-blue-split use the same meta description. A description written for each page earns more clicks.

https://comebackkid-us.com/collections/all-products, https://comebackkid-us.com/collections/apparel-1, https://comebackkid-us.com/collections/accessories, https://comebackkid-us.com/collections/music and https://comebackkid-us.com/collections/sale have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://comebackkid-us.com/.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 234 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 (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 18 cookies, 1 of them by other companies (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.