Website review, no card needed

and1eu.com logo

and1eu.com website review

Visit site (opens in a new tab)Reviewed 5 November 202643 issues · 88 checks

This review found 43 issues worth fixing on and1eu.com, 17 of them high impact, across 88 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.4 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
333 ms75 msMay 16Oct 31303 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026106 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 2026109 ms
Jun 20, 2026108 ms
Jun 27, 2026109 ms
Jul 4, 2026109 ms
Jul 11, 2026108 ms
Jul 18, 2026108 ms
Jul 25, 2026131 ms
Aug 1, 2026160 ms
Aug 8, 2026183 ms
Aug 15, 2026204 ms
Aug 22, 2026212 ms
Aug 29, 2026222 ms
Sep 5, 2026234 ms
Sep 12, 2026246 ms
Sep 19, 2026260 ms
Sep 26, 2026272 ms
Oct 3, 2026276 ms
Oct 10, 2026280 ms
Oct 17, 2026290 ms
Oct 24, 2026295 ms
Oct 31, 2026303 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

Full-page screenshot of and1eu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. and1eu.com at 1.8 s1.8 s
  2. and1eu.com at 3.6 s3.6 s
  3. and1eu.com at 5.4 s5.4 s
  4. and1eu.com at 7.2 s7.2 s
  5. and1eu.com at 9.1 s9.1 s
  6. and1eu.com at 10.9 s10.9 s
  7. and1eu.com at 12.7 s12.7 s
  8. and1eu.com at 14.5 s14.5 s

Speed

13 to fix32
  • Improve image delivery

    2.6 s · 6.9 MB

    24 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Main-thread work: 17.3 s

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

  • Render-blocking requests

    1.5 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Mobile performance score: 32

    32/100

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

  • 4,888 HTML elements

    The page has 4,888 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 (Google Tag Manager, Shopify and Facebook and others), adding 1.9 MB and 2.4 s of main-thread time.

  • Google Tag Manager adds 987 ms

    987 ms

    Google Tag Manager costs a phone 987 ms of main-thread work and 693 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 JavaScript

    682 KiB

    About 682 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 384 ms

    384 ms

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

  • 20 long tasks on the main thread

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

  • Facebook adds 299 ms

    299 ms

    Facebook costs a phone 299 ms of main-thread work and 229 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 269 ms

    269 ms

    Klaviyo costs a phone 269 ms of main-thread work and 364 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.

  • TikTok adds 270 ms

    270 ms

    TikTok costs a phone 270 ms of main-thread work and 157 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 · 248 KiB

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

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Legacy JavaScript

    40 KiB

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

  • 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: 34 ms

    34 ms

    Your server sent the HTML in 34 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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: 45.7 s

    45.7 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 9.8 s

    9.8 s

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

  • Real-user INP: 295 ms

    295 ms

    Real visitors wait 295 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 183% slower for real visitors

    +183%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 106 ms to 303 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 1.9 s

    1.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 654 ms

    654 ms

    Real visitors wait 654 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.068

    0.068

    The layout barely moves while loading (CLS 0.068, good is under 0.1).

Images and page weight

5 to fix14
  • Page weight: 11.4 MB in 310 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 310 requests on a phone: images 8.0 MB (32), scripts 2.0 MB (96) and other files 930 KiB (161). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    823 KiB

    1 image is downloaded at several times the size a phone draws it, for example T-AD0815-B-AD0814_1385.jpg at 1,935 px wide, shown at 390 px. Resized copies would save about 823 KiB.

  • 2 images in older formats

    2 images (2.5 MB) 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.

  • An image on the first screen is lazy-loaded

    ezgif.com-video-to-gif-converter-22.gif 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).

  • About 3.2 g of CO₂ per visit

    3.23 g

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

Accessibility

6 to fixGoogle 9093
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail 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.

  • 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 (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 128 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • 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.

  • 140 internal links, 4 external

    The homepage links to 140 pages on and1eu.com and 4 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Shop AND1 for basketball shoes and street-ready apparel. Discover performance footwear and iconic styles built for on a…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “AND1 | Shop Basketball Trainers, Apparel & More – And1”.

  • Canonical URL set

    The canonical URL is https://and1.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://and1.com/sitemap.xml.

AI search readiness

100
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 (831 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://and1.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://and1.com/collections/mk-x-london-hoops and https://and1.com/collections/mens-footwear have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://and1.com/collections/all-new-releases, https://and1.com/collections/trainers and https://and1.com/collections/mens-footwear have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://and1.com/collections/all-new-releases, https://and1.com/collections/mk-x-london-hoops, https://and1.com/collections/trainers and https://and1.com/collections/mens-footwear 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.

  • 2 pages slow to respond

    https://and1.com/collections/all-new-releases and https://and1.com/collections/trainers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97219450&tm=gtm002&Ver=2&mid=6b055f1a-beec-464b-bae3-ea00ee44407d&bo=3&sid=68f0cd30d95811f1942ef95101d57423&vid=68f0ede0d95811f19874d9aec3ed52f7&vids=0&msclkid=N&pi=91.

  • 21 small tap targets

    21 of 76 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “analytics is not defined”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • 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 303 words of copy

    The homepage carries about 303 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: “Learn more” and “SHOP ATTACK 4.0”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “shop ATTACK 4.0”, “SHOP MAD GAME PRO” and “SHOP PERFORMANCE”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 and1eu.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on and1eu.com, including 22 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25