Website review, no card needed
aandfstore.com website review
Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 83 checks
This review found 40 issues worth fixing on aandfstore.com, 18 of them high impact, across 83 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
62D- #112,908 of 117,615 reviewed websitesbeats 3%
- #65,817 of 66,923 online storesbeats 1%
- #60,226 of 61,018 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 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.8 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.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 103 ms |
| May 16, 2026 | 103 ms |
| May 23, 2026 | 102 ms |
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 108 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
Speed
Render-blocking requests
3.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Main-thread work: 10.5 s
A phone's processor spends 10.5 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,941 HTML elements
The page has 4,941 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 3.7 MB32 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Improve image delivery
2.3 MB76 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 4.4 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
900 ms · 667 KiBAbout 667 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 493 ms
493 msGoogle Tag Manager costs a phone 493 ms of main-thread work and 762 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.
Shopify adds 228 ms
228 msShopify costs a phone 228 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.
Reduce unused CSS
150 ms · 85 KiBAbout 85 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.
Legacy JavaScript
150 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 6 KiB6 KiB could be saved by minifying CSS.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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: 20 ms
20 msYour server sent the HTML in 20 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.
Real-user CLS: 0.40
0.40For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 24.5 s
24.5 sYour largest element takes 24.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SABBATICAL|COMPLETE SETUP”.
Time to Interactive: 61.3 s
61.3 sThe page becomes fully interactive after 61.3 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.391
0.391The layout shifts by 0.391 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 309 ms
309 msScripts block taps and scrolling for 309 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 103 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 516 ms
516 msReal visitors wait 516 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 15.3 MB in 481 requests
15.3 MBYour homepage downloads 15.3 MB in 481 requests on a phone: images 11.5 MB (242), scripts 2.1 MB (83) and other files 820 KiB (95). Under 2 MB keeps phones on slow connections fast.
12 images far larger than shown
677 KiB12 images are downloaded at several times the size a phone draws them, for example feature-bn840-sabbatical-how-to-pitch-the-tent-kamikouchi.jp at 840 px wide, shown at 164 px. Resized copies would save about 677 KiB.
25 images below the first screen load straight away
25 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (230 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 4.3 g of CO₂ per visit
4.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.33 g of CO₂e: 520.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
410 internal links, 30 external
The homepage links to 410 pages on aandfstore.com and 30 external pages.
6 checks passed
Meta description: 100 characters
Your meta description is 100 characters: “1977年創業以来、日本のアウトドア業界を牽引してきたエイアンドエフ(A&F)の公式通販サイトです。MYSTERYRANCH(ミステリーランチ)など多くのアウトドアブランドを取り扱っています。”.
Title: 48 characters
Your title is a healthy 48 characters: “A&F エイアンドエフ オンラインストア【公式通販サイト】 – aandfonlinestore”.
Canonical URL set
The canonical URL is https://aandfstore.com/.
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://aandfstore.com/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.
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 (270 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aandfstore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://aandfstore.com/pages/ranking, https://aandfstore.com/pages/contact and https://aandfstore.com/collections/price_1000 have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://aandfstore.com/pages/brandlist, https://aandfstore.com/pages/ranking, https://aandfstore.com/collections/sale, https://aandfstore.com/collections/000005, https://aandfstore.com/collections/100162 and https://aandfstore.com/collections/100155 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 pages with very little text
https://aandfstore.com/pages/ranking, https://aandfstore.com/collections/sale, https://aandfstore.com/pages/contact, https://aandfstore.com/collections/000004, https://aandfstore.com/collections/bag_mountaineeringpack and https://aandfstore.com/collections/000005 and 8 others 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.
1 page slow to respond
https://aandfstore.com/pages/ranking took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 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
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'includes')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
122 of 137 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 233 words
The homepage has only about 233 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.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 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.
48 other companies contacted
Loading the homepage contacts 48 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 aandfstore.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on aandfstore.com, including 19 speed issues, 2 SEO issues and 5 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.