kingofcotton.com website review

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

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

25 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Shopify, Klaviyo and 506.io and others), adding 4.0 MB and 798 ms of main-thread time.

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

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

Shopify costs a phone 335 ms of main-thread work and 3.0 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).

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

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

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

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

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

12 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “White bed linen and a beige fringed throw in a sunlit bedro…”.

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

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

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

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

Your homepage downloads 5.9 MB in 476 requests on a phone: images 2.9 MB (76), scripts 1.5 MB (167) and other files 1.1 MB (178). Under 2 MB keeps phones on slow connections fast.

1 image (68 KiB) is 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.

3 images further down the page (145 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.68 g of CO₂e: 202.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your <h1> is empty.

The homepage links to 149 pages on kingofcotton.com and 7 external pages.

There is no https://www.kingofcotton.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

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

https://www.kingofcotton.com/collections/all, https://www.kingofcotton.com/customer_authentication/redirect and https://www.kingofcotton.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kingofcotton.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://www.kingofcotton.com/cdn/shop/t/26/assets/no.svg?v=9044.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 124 trust badges. 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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 439 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 14 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.