Programmable

Website review, no card needed

allinonetrade.de logo

allinonetrade.de website review

Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 77 checks

This review found 24 issues worth fixing on allinonetrade.de, 5 of them high impact, across 77 checks. The most urgent: 6 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

Site score

90A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.4 s947 msJul 4Nov 7999 ms
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 26, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 31, 20261.0 s
Nov 7, 2026999 ms
Real-visitor tap response (INP)75th percentile, phones
142 ms91 msJul 4Oct 17135 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 2026127 ms
Jul 18, 2026112 ms
Aug 22, 202697 ms
Aug 29, 2026109 ms
Sep 5, 2026129 ms
Sep 12, 2026130 ms
Sep 26, 2026136 ms
Oct 10, 2026132 ms
Oct 17, 2026135 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

allinonetrade.de (opens in a new tab)
Full-page screenshot of allinonetrade.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allinonetrade.de at 0.4 s0.4 s
  2. allinonetrade.de at 0.8 s0.8 s
  3. allinonetrade.de at 1.3 s1.3 s
  4. allinonetrade.de at 1.7 s1.7 s
  5. allinonetrade.de at 2.1 s2.1 s
  6. allinonetrade.de at 2.5 s2.5 s
  7. allinonetrade.de at 2.9 s2.9 s
  8. allinonetrade.de at 3.4 s3.4 s

Speed

5 to fix88

  • Mobile performance score: 88

    88/100

    Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    220 ms · 286 KiB

    About 286 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 220 ms faster on a phone.

  • Font display

    300 ms

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

  • Google Tag Manager adds 233 ms

    233 ms

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

  • 2,052 HTML elements

    The page has 2,052 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics), adding 443 KiB and 233 ms of main-thread time.

  • Render-blocking requests

    200 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.

  • 3 long tasks on the main thread

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

  • Improve image delivery

    110 KiB

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

  • Reduce unused CSS

    88 KiB

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

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 1.2 s

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

  • Server response: 228 ms

    228 ms

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

Core Web Vitals

3 to fix100

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

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

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

    +12%

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

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

    0.7 s

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

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

    -18%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 110 ms

    110 ms

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

  • Cumulative Layout Shift: 0.027

    0.027

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

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    redbull-big-slider-bilder-redbull-iced-vanilla-berry-smartph 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 0.4 g of CO₂ per visit

    0.42 g

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

3 checks passed

  • Page weight: 1.5 MB in 79 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 79 requests on a phone: scripts 708 KiB (30), images 428 KiB (32) and fonts 236 KiB (10). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

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

  • 6 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

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

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090

  • 2 H1 headlines

    There are 2 <h1> headlines (“Internationale Süßwaren, Snacks und Getränke für …” and “Ihr Großhandel für internationale Süßwaren und Ge…”). One clear main headline is easier for people and search engines.

  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 133 internal links, 11 external

    The homepage links to 133 pages on allinonetrade.de and 11 external pages.

6 checks passed

  • Title: 47 characters

    Your title is a healthy 47 characters: “Süßwaren & Getränke Großhandel | Allinone Trade”.

  • Canonical URL set

    The canonical URL is https://allinonetrade.de/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://allinonetrade.de/sitemap_index.xml.

AI search readiness

1 to fix88

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

  • No llms.txt

    There is no https://allinonetrade.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,554 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79

  • 1 linked page hidden from search

    https://allinonetrade.de/Kontakt is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://allinonetrade.de/Hersteller all use the title “Süßwaren & Getränke Großhandel | Allinone Trade”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://allinonetrade.de/News, https://allinonetrade.de/Kontakt and https://allinonetrade.de/Hersteller use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://allinonetrade.de/News, https://allinonetrade.de/Kontakt, https://allinonetrade.de/Alle-Produkte, https://allinonetrade.de/Suesswaren, https://allinonetrade.de/Chips-Salzige-Snacks and https://allinonetrade.de/Getraenke and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://allinonetrade.de/Chips-Salzige-Snacks, https://allinonetrade.de/Getraenke, https://allinonetrade.de/Nudeln-Fertiggerichte, https://allinonetrade.de/Fruehstueck-und-Aufstriche, https://allinonetrade.de/Spielzeuge and https://allinonetrade.de/Kaugummi-und-Kaubonbons and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 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 404 ()”.

2 checks passed

  • Tap targets are thumb-sized

    35 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67

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

    The homepage carries about 745 words of visible text.

4 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “JTL-Shop” and “TECHNIK JTL-Shop Template”.

  • 33 short forms

    33 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 allinonetrade.de, 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;Shopify Plus
Analytics
Google Analytics
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on allinonetrade.de, including 8 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