Website review, no card needed
allcandy.shop website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 77 checks
This review found 31 issues worth fixing on allcandy.shop, 13 of them high impact, across 77 checks. The most urgent: page weight: 20.1 MB in 396 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
84B- #21,596 of 120,386 reviewed websitesbeats 77%
- #14,000 of 68,161 online storesbeats 73%
- #13,583 of 62,115 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 166 ms |
| May 23, 2026 | 170 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 159 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 169 ms |
| Sep 12, 2026 | 165 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 149 ms |
| Oct 31, 2026 | 146 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
How it loaded on a phone
0.9 s
1.8 s
2.8 s
3.7 s
4.6 s
5.5 s
6.4 s
7.4 s
Speed
10,225 HTML elements
The page has 10,225 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
4.4 MB26 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
3.0 MB29 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, vitals.app and Google Tag Manager and others), adding 1.8 MB and 786 ms of main-thread time.
Render-blocking requests
900 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Shopify adds 424 ms
424 msShopify costs a phone 424 ms of main-thread work and 1.1 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 JavaScript
313 KiBAbout 313 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 150 ms
150 msGoogle Tag Manager costs a phone 150 ms of main-thread work and 296 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 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: 24 ms
24 msYour server sent the HTML in 24 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.
Time to Interactive: 30.0 s
30.0 sThe page becomes fully interactive after 30.0 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Real-user INP: 339 ms
339 msReal visitors wait 339 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
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.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 166 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 194 ms
194 msScripts block the page for only 194 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Weihnachten kann kommen.”.
Images and page weight
Page weight: 20.1 MB in 396 requests
20.1 MBYour homepage downloads 20.1 MB in 396 requests on a phone: media 10.2 MB (1), images 7.3 MB (112) and scripts 1.4 MB (166). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.
12 images far larger than shown
4.0 MB12 images are downloaded at several times the size a phone draws them, for example Fotos-Polaroid_vinyedo.png at 2,000 px wide, shown at 525 px. Resized copies would save about 4.0 MB.
36 images in older formats
36 images (11.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.
4 images below the first screen load straight away
4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.7 g of CO₂ per visit
5.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.70 g of CO₂e: 684.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
32 elements hidden from screen readers can still receive keyboard focus.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 220 images in the HTML carry an alt attribute.
51 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: 51 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
395 internal links, 0 external
The homepage links to 395 pages on allcandy.shop and 0 external pages.
8 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “AllSpirits ist Dein Onlinehandel für Bier & Cider, Softdrinks & Energy-Drinks, Spirituosen, Weine & Schaumweine, Süßigk…”.
One H1 headline
Your main headline reads: “AllSpirits”.
Title: 43 characters
Your title is a healthy 43 characters: “AllSpirits – Getränke, Süßigkeiten und mehr”.
Canonical URL set
The canonical URL is https://allspirits.shop/.
Structured data in place
Structured data found: Organization.
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://allspirits.shop/sitemap.xml.
AI search readiness
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.
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 (2,367 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://allspirits.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without an H1
https://allspirits.shop/collections/alle-produkte, https://allspirits.shop/collections/top-angebote, https://allspirits.shop/collections/spirituosen, https://allspirits.shop/collections/whisky, https://allspirits.shop/collections/vodka and https://allspirits.shop/collections/rum and 8 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 116 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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
66 of 75 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 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.
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 458 words of copy
The homepage carries about 458 words of visible text.
1 checks passed
133 short forms
133 short forms (0 fields at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
29 other companies contacted
Loading the homepage contacts 29 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 allcandy.shop, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wishlist By Square · Hoppy Trust Badges · Product Labels And Badges · Feebee · Essential Cart Drawer · Bestpush
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
- CMS
- WordPress
- 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 31 issues on allcandy.shop, including 14 speed 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.