tenthousand.cc website review

moonshot-ai.com costs a phone 1.5 s of main-thread work and 39 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (moonshot-ai.com, Shopify and Klaviyo and others), adding 1.2 MB and 2.6 s of main-thread time.

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

About 474 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.

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

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

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

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

Klaviyo costs a phone 216 ms of main-thread work and 316 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 2,097 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

16 KiB could be saved by minifying JavaScript.

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BUILT HERE”.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 12.7 MB in 383 requests on a phone: media 8.5 MB (2), scripts 2.1 MB (158) and other files 1.0 MB (191). Under 2 MB keeps phones on slow connections fast.

1 image (80 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.

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

[role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 80 pages on tenthousand.cc and 5 external pages.

There is no https://www.tenthousand.cc/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.tenthousand.cc/collections/shop-all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.tenthousand.cc/collections/shop-all, https://www.tenthousand.cc/collections/training, https://www.tenthousand.cc/collections/lifting and https://www.tenthousand.cc/collections/outdoor have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tenthousand.cc/collections/new-arrivals, https://www.tenthousand.cc/collections/shorts, https://www.tenthousand.cc/collections/shop-all and https://www.tenthousand.cc/collections/training have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tenthousand.cc/collections/new-arrivals, https://www.tenthousand.cc/collections/shorts and https://www.tenthousand.cc/collections/training 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.

https://www.tenthousand.cc/pages/find-your-perfect-shorts, https://www.tenthousand.cc/collections/best-sellers, https://www.tenthousand.cc/collections/new-arrivals, https://www.tenthousand.cc/collections/shorts, https://www.tenthousand.cc/collections/shop-all and https://www.tenthousand.cc/collections/rep and 2 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.ojrq.net/p/?return=&cid=18764&tpsync=no&auth=.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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 carries about 326 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 3 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 65 cookies, 2 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 68 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.