Website review, no card needed
abercrombie.id website review
Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 81 checks
This review found 38 issues worth fixing on abercrombie.id, 6 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
84B- #22,083 of 123,879 reviewed websitesbeats 77%
- #14,230 of 69,702 online storesbeats 74%
- #13,801 of 63,406 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 162 ms |
| May 16, 2026 | 170 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 176 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 173 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 219 ms |
| Aug 22, 2026 | 233 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 263 ms |
| Sep 19, 2026 | 254 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 236 ms |
| Oct 24, 2026 | 237 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.9 s · 1.3 MB10 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 317 KiBAbout 317 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.
Render-blocking requests
550 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Use efficient cache lifetimes
450 ms · 91 KiB8 files are served with short cache lifetimes, so returning visitors download them again (91 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and haptikapi.com and others), adding 1.4 MB and 357 ms of main-thread time.
2,424 HTML elements
The page has 2,424 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 116 ms
116 msShopify costs a phone 116 ms of main-thread work and 691 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
150 ms · 74 KiBAbout 74 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 702 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile Banner”.
Time to Interactive: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 162 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 107% slower for real visitors
+107%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 505 ms
505 msReal visitors wait 505 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 20 ms
20 msScripts block the page for only 20 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.3 MB in 261 requests
4.3 MBYour homepage downloads 4.3 MB in 261 requests on a phone: images 1.8 MB (16), scripts 1.0 MB (66) and other files 974 KiB (137). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ANF_FALL_UPDATE_Homepage_768x1000_WOMEN_b9128552-efcc-4847-9 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images in older formats
6 images (575 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.
About 1.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner 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)
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.
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.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (92 characters)
Your title is 92 characters, so Google will cut it off around 60: “Abercrombie & Fitch | Authentic American clothing since 1892 – Abercrombie & Fitch Indone…”.
4 H1 headlines
There are 4 <h1> headlines (“”, “Sign In” and “Join”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
207 internal links, 15 external
The homepage links to 207 pages on abercrombie.id and 15 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Explore a world of online shopping with the latest fashion. Shop now for exclusive deals and fast shipping. Elevate you…”.
Canonical URL set
The canonical URL is https://www.abercrombie.id/.
Structured data in place
Structured data found: Organization and WebSite.
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://www.abercrombie.id/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
2 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.
llms.txt published
The site publishes https://www.abercrombie.id/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without an H1
https://www.abercrombie.id/collections/mens-new-arrivals, https://www.abercrombie.id/collections/mens-tops-new-arrivals, https://www.abercrombie.id/collections/mens-bottom-new-arrivals, https://www.abercrombie.id/collections/womens-new-arrival, https://www.abercrombie.id/collections/womens-dresses-and-rompers-new-arrivals and https://www.abercrombie.id/collections/womens-tops-new-arrivals and 8 others 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 67 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 55 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 “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus/css/okendo-reviews-styles.c5b9c195.css' f…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
Only about 140 words
The homepage has only about 140 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MULTIBUY” and “SHOP NOW”.
36 calls to action
The homepage has 36 calls to action, for example “Order Help”, “Track My Order” and “Join”.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
13 other companies contacted
Loading the homepage contacts 13 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 abercrombie.id, 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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on abercrombie.id, including 15 speed issues, 3 SEO issues and 4 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.