Website review, no card needed
americantall.com website review
Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 90 checks
This review found 44 issues worth fixing on americantall.com, 15 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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- #86,555 of 123,862 reviewed websitesbeats 26%
- #54,436 of 69,698 online storesbeats 18%
- #51,149 of 63,406 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 178 ms |
| May 9, 2026 | 179 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 214 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 228 ms |
| Jul 11, 2026 | 234 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 238 ms |
| Aug 1, 2026 | 244 ms |
| Aug 8, 2026 | 245 ms |
| Aug 15, 2026 | 250 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 262 ms |
| Sep 5, 2026 | 266 ms |
| Sep 12, 2026 | 262 ms |
| Sep 19, 2026 | 258 ms |
| Sep 26, 2026 | 250 ms |
| Oct 3, 2026 | 245 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 246 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.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Render-blocking requests
1.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 17.0 s
A phone's processor spends 17.0 s on main-thread work while loading, 9.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,510 HTML elements
The page has 7,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Google Tag Manager and Shopify and others), adding 2.2 MB and 2.7 s of main-thread time.
Reduce unused JavaScript
1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page.
ContentSquare adds 760 ms
760 msContentSquare costs a phone 760 ms of main-thread work and 164 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.
Reduce unused CSS
640 ms · 71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 640 ms faster on a phone.
Google Tag Manager adds 650 ms
650 msGoogle Tag Manager costs a phone 650 ms of main-thread work and 368 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.
Use efficient cache lifetimes
150 ms · 394 KiB30 files are served with short cache lifetimes, so returning visitors download them again (394 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 445 ms. During a long task the page ignores taps.
Improve image delivery
440 KiB11 images could be 440 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 380 ms
380 msShopify costs a phone 380 ms of main-thread work and 537 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.
Facebook adds 281 ms
281 msFacebook costs a phone 281 ms of main-thread work and 228 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.
Klaviyo adds 204 ms
204 msKlaviyo costs a phone 204 ms of main-thread work and 355 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.
Minify JavaScript
114 KiB114 KiB could be saved by minifying JavaScript.
Legacy JavaScript
68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need.
Minify CSS
40 ms · 13 KiB13 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 58 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 25 ms
25 msYour server sent the HTML in 25 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.
Speed Index: 21.4 s
21.4 sVisually, the page fills in at 21.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.1 s
38.1 sThe page becomes fully interactive after 38.1 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user INP: 415 ms
415 msReal visitors wait 415 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 178 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 703 ms
703 msReal visitors wait 703 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.068
0.068The layout barely moves while loading (CLS 0.068, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 489 requests
6.3 MBYour homepage downloads 6.3 MB in 489 requests on a phone: scripts 3.2 MB (199), images 1.5 MB (61) and other files 907 KiB (189). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (393 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.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
26 form fields without a label
26 form fields have no label, so screen readers announce an empty box and autofill guesses.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
403 internal links, 17 external
The homepage links to 403 pages on americantall.com and 17 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Explore our clothing for tall women (5'9" - 6'6") and tall men (6' - 7'1")! American Tall designs fitted, slim clothes.…”.
One H1 headline
Your main headline reads: “American Tall American Tall”.
Title: 61 characters
Your title is a healthy 61 characters: “Tall Men's & Tall Women's Clothing up to 7'1" | American Tall”.
Canonical URL set
The canonical URL is https://americantall.com/.
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://americantall.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (4,043 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://americantall.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://americantall.com/collections/tall-mens-best-sellers, https://americantall.com/pages/american-tall-referrals, https://americantall.com/collections/fall-styles-for-tall-men, https://americantall.com/pages/ski-guide-tall-men and https://americantall.com/pages/camping-guide have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://americantall.com/pages/american-tall-referrals, https://americantall.com/pages/ski-guide-tall-men and https://americantall.com/pages/camping-guide have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 116 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://americantall.com/.
8 small tap targets
8 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 176 words
The homepage has only about 176 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Women” and “Shop Men”.
19 calls to action
The homepage has 19 calls to action, for example “Contact Us”, “Track My Order” and “Suit Shop”.
28 short forms
28 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 39 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (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.
56 other companies contacted
Loading the homepage contacts 56 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 americantall.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics
Hiring
- Hiring
- 5 open roles
- Teams
- Information Technology (2), Marketing Operations (1), Merchandising (1), Product Development (1)
- Job board
- lever
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on americantall.com, including 23 speed issues, 2 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.