Website review, no card needed
takedownshop.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 77 checks
This review found 34 issues worth fixing on takedownshop.com, 11 of them high impact, across 77 checks. The most urgent: 10,203 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #74,113 of 105,222 reviewed websitesbeats 26%
- #46,277 of 59,089 online storesbeats 18%
- #43,535 of 53,842 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 147 ms |
| May 30, 2026 | 151 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 181 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 172 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 225 ms |
| Sep 19, 2026 | 229 ms |
| Sep 26, 2026 | 235 ms |
| Oct 3, 2026 | 237 ms |
| Oct 10, 2026 | 230 ms |
| Oct 17, 2026 | 236 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 229 ms |
| Nov 7, 2026 | 220 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
10,203 HTML elements
The page has 10,203 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.6 MB and 1.3 s of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
250 ms · 392 KiB22 files are served with short cache lifetimes, so returning visitors download them again (392 KiB).
Reduce unused JavaScript
100 ms · 532 KiBAbout 532 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 100 ms faster on a phone.
Google Tag Manager adds 425 ms
425 msGoogle Tag Manager costs a phone 425 ms of main-thread work and 628 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.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 344 ms. During a long task the page ignores taps.
Klaviyo adds 148 ms
148 msKlaviyo costs a phone 148 ms of main-thread work and 365 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.
Legacy JavaScript
64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need.
Improve image delivery
21 KiB1 image could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 871 ms
871 msScripts block taps and scrolling for 871 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.4 s
4.4 sYour 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 element shown below.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 304 ms
304 msReal visitors wait 304 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 147 ms to 220 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 523 ms
523 msReal visitors wait 523 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 578 requests
7.6 MBYour homepage downloads 7.6 MB in 578 requests on a phone: images 3.2 MB (91), other files 2.5 MB (363) and scripts 1.8 MB (101). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.17 g of CO₂e: 260.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
51 form fields without a label
51 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 112 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Fully Customizable Sportswear & Premium Training Gear – Takedown Sportswear”.
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
225 internal links, 4 external
The homepage links to 225 pages on takedownshop.com and 4 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://takedownshop.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://takedownshop.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,670 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://takedownshop.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://takedownshop.com/products/mystery-item-free-w-purchase-of-75 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://takedownshop.com/products/mystery-item-free-w-purchase-of-75 all use the title “Fully Customizable Sportswear & Premium Training Gear – Takedown Spor…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://takedownshop.com/products/mystery-item-free-w-purchase-of-75, https://takedownshop.com/collections/mj-all-singlet, https://takedownshop.com/collections/mj-all-mens-shorts-sorted-by-bestseller, https://takedownshop.com/collections/mj-rashguards, https://takedownshop.com/collections/ml-shirts-tees and https://takedownshop.com/collections/ml-hoodies-pullover and 9 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://takedownshop.com/products/mystery-item-free-w-purchase-of-75 has no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://takedownshop.com/collections/mj-all-mens-products-sorted-by-bestseller, https://takedownshop.com/collections/mj-all-womens-shorts-sorted-by-bestseller, https://takedownshop.com/collections/mj-leggings, https://takedownshop.com/collections/sports-bra and https://takedownshop.com/collections/womens-singlets took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://takedownshop.com/cdn/shop/t/56/assets/template-index.min.css?v=52115' because its …”.
2 checks passed
Tap targets are thumb-sized
52 of 53 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 18-field form
Your longest form asks for 18 fields (0 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,711 words of copy
The homepage carries about 1,711 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Free Shipping on Order $100+”.
16 calls to action
The homepage has 16 calls to action, for example “Free Shipping on Order $100+”, “Shop All 360° Custom Apparel” and “Shop All 360° Custom Builder”.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
45 other companies contacted
Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at takedownshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Okendo · Klaviyo Email Marketing Sms · custom-gateway.net · govx.com · hubapi.com · getredo.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 85
- Founded
- 2006
- Headquarters
- Lawrenceville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on takedownshop.com, including 19 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.