Programmable

Website review, no card needed

intotheam.eu logo

intotheam.eu website review

Visit site (opens in a new tab)Reviewed 12 November 202632 issues · 68 checks

This review found 32 issues worth fixing on intotheam.eu, 15 of them high impact, across 68 checks. The most urgent: avoid multiple page redirects. 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

Site score

64D

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

www.intotheam.eu (opens in a new tab)
Full-page screenshot of intotheam.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. intotheam.eu at 0.7 s0.7 s
  2. intotheam.eu at 1.4 s1.4 s
  3. intotheam.eu at 2.2 s2.2 s
  4. intotheam.eu at 2.9 s2.9 s
  5. intotheam.eu at 3.6 s3.6 s
  6. intotheam.eu at 4.3 s4.3 s
  7. intotheam.eu at 5.1 s5.1 s
  8. intotheam.eu at 5.8 s5.8 s

Speed

9 to fix35

  • Avoid multiple page redirects

    4.5 s

    The page goes through 1 redirect before it starts loading, costing about 4.5 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    3.8 s · 501 KiB

    About 501 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Signyfyd adds 1.2 s

    1.2 s

    Signyfyd costs a phone 1.2 s of main-thread work and 283 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.5 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 (Signyfyd, Google Tag Manager and helpdocs.io and others), adding 1.4 MB and 1.8 s of main-thread time.

  • 17 long tasks on the main thread

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

  • Google Tag Manager adds 369 ms

    369 ms

    Google Tag Manager costs a phone 369 ms of main-thread work and 572 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.

  • Font display

    300 ms

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

  • Use efficient cache lifetimes

    200 ms · 90 KiB

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

  • Legacy JavaScript

    82 KiB

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

  • Reduce unused CSS

    18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    6 KiB

    6 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: 6 ms

    6 ms

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

Core Web Vitals

6 to fix43

  • First Contentful Paint: 8.0 s

    8.0 s

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

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

  • Time to Interactive: 19.6 s

    19.6 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Total Blocking Time: 847 ms

    847 ms

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

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed

  • Cumulative Layout Shift: 0.079

    0.079

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

Images and page weight

1 to fix67

  • Page weight: 2.7 MB in 204 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 204 requests on a phone: scripts 1.8 MB (120), other files 572 KiB (54) and HTML 164 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.77 g

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

Accessibility

4 to fixGoogle 8488

  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

3 to fixGoogle 8584

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 31 internal links, 1 external

    The homepage links to 31 pages on intotheam.eu and 1 external page.

6 checks passed

  • Meta description: 152 characters

    Your meta description is 152 characters: “Stay inspired in one-of-a-kind All Over Print Shirts, Tees, Tank Tops, & Hoodies from INTO THE AM. Apparel handcrafted …”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “All Over Print - Shirts, Hoodies, Tank Tops, Tees - INTO THE AM”.

  • Canonical URL set

    The canonical URL is https://www.intotheam.eu/.

  • 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://www.intotheam.eu/sitemap.xml.

AI search readiness

1 to fix83

  • 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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.intotheam.eu/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix71

  • 15 pages without a title

    https://www.intotheam.eu/collections/mens-tees, https://www.intotheam.eu/collections/mens-tank-tops, https://www.intotheam.eu/collections/hoodie-collection, https://www.intotheam.eu/collections/mens-joggers, https://www.intotheam.eu/collections/mens-graphic-t-shirts and https://www.intotheam.eu/collections/mens-all-over-print-shirts and 9 others have no <title>, so Google invents the link text in results.

  • 15 pages without a meta description

    https://www.intotheam.eu/collections/mens-tees, https://www.intotheam.eu/collections/mens-tank-tops, https://www.intotheam.eu/collections/hoodie-collection, https://www.intotheam.eu/collections/mens-joggers, https://www.intotheam.eu/collections/mens-graphic-t-shirts and https://www.intotheam.eu/collections/mens-all-over-print-shirts and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.intotheam.eu/collections/mens-tees, https://www.intotheam.eu/collections/mens-tank-tops, https://www.intotheam.eu/collections/hoodie-collection, https://www.intotheam.eu/collections/mens-joggers, https://www.intotheam.eu/collections/mens-graphic-t-shirts and https://www.intotheam.eu/collections/mens-all-over-print-shirts and 9 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 25 found) and read each the way a search engine does.

3 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9692

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64

  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 10 words

    The homepage has only about 10 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.

3 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “SHOP” and “Track My Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 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.

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 intotheam.eu, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

signifyd.com · amazonaws.com · stamped.io · refersion.com · klaviyo.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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on intotheam.eu, 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

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