Website review, no card needed

1019.store logo

1019.store website review

Visit site (opens in a new tab)Reviewed 28 October 202620 issues · 70 checks

This review found 20 issues worth fixing on 1019.store, 5 of them high impact, across 70 checks. The most urgent: 8 text elements with low contrast. 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.4 s565 msMay 16Oct 24664 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Aug 29, 2026919 ms
Sep 5, 2026795 ms
Sep 12, 2026784 ms
Sep 19, 2026782 ms
Sep 26, 2026751 ms
Oct 3, 2026730 ms
Oct 10, 2026722 ms
Oct 17, 2026704 ms
Oct 24, 2026664 ms
Real-visitor tap response (INP)75th percentile, phones
144 ms67 msMay 16Oct 1076 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026127 ms
May 30, 2026127 ms
Jun 6, 2026133 ms
Jun 13, 2026135 ms
Jun 20, 2026129 ms
Aug 29, 202694 ms
Sep 5, 202680 ms
Sep 12, 202678 ms
Sep 19, 202680 ms
Sep 26, 202678 ms
Oct 3, 202676 ms
Oct 10, 202676 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 1019.store (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1019.store at 0.4 s0.4 s
  2. 1019.store at 0.8 s0.8 s
  3. 1019.store at 1.1 s1.1 s
  4. 1019.store at 1.5 s1.5 s
  5. 1019.store at 1.9 s1.9 s
  6. 1019.store at 2.3 s2.3 s
  7. 1019.store at 2.6 s2.6 s
  8. 1019.store at 3.0 s3.0 s

Speed

2 to fix89
  • Mobile performance score: 89

    89/100

    Your mobile performance score is 89 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Improve image delivery

    73 KiB

    5 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 67 KiB and 10 ms of main-thread time.

  • Use efficient cache lifetimes

    5 KiB

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

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

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 240 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1019 Hoodie in Schwarz – Vorderansicht”.

  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.9 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.

10 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: 0.9 s

    0.9 s

    Real visitors wait 0.9 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 FCP: 0.6 s

    0.6 s

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

  • Tap response (INP) got 38% faster for real visitors

    -38%

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

  • Largest content (LCP) got 47% faster for real visitors

    -47%

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

  • Time to Interactive: 3.6 s

    3.6 s

    The page is fully interactive after 3.6 s.

  • Cumulative Layout Shift: 0

    0

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

  • Speed Index: 1.9 s

    1.9 s

    Visually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 7 ms

    7 ms

    Scripts block the page for only 7 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.40 g

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

4 checks passed
  • Page weight: 1.4 MB in 168 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 168 requests on a phone: other files 877 KiB (116), images 320 KiB (18) and scripts 204 KiB (30). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

4 to fixGoogle 9193
  • 8 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.1019records.de/cdn/shop/files/1019_Logo_CMYK_4ab9…”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 27 internal links, 0 external

    The homepage links to 27 pages on 1019.store and 0 external pages.

5 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Offizieller 1019 Records Merch Shop: Hoodies, T-Shirts, Track Pants, Accessoires & Tickets. Einsnulleinsneun – der Onli…”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “1019 OFFICIAL MERCH SHOP – 1019 | Merch Shop”.

  • Canonical URL set

    The canonical URL is https://www.1019records.de/.

  • 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.1019records.de/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), 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.1019records.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.1019records.de/collections/1019-clothing has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.1019records.de/collections/1019-clothing, https://www.1019records.de/products/1019-hoodie-black, https://www.1019records.de/products/1019-hoodie-olive, https://www.1019records.de/products/1019-zip-hoodie-grey, https://www.1019records.de/products/1019-zip-up-hoodie-black and https://www.1019records.de/products/1019-track-pants-black and 9 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 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 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 12 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 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.

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

    The homepage has only about 96 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
  • 1 call to action

    The homepage has 1 call to action, for example “Contact information”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 1019.store, 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
10 Shopify Products;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 20 issues on 1019.store, including 5 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

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