Website review, no card needed
acmecups.eu website review
Visit site (opens in a new tab)Reviewed 27 October 202648 issues · 92 checks
This review found 48 issues worth fixing on acmecups.eu, 19 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
76C- #75,209 of 123,879 reviewed websitesbeats 35%
- #48,194 of 69,698 online storesbeats 26%
- #45,657 of 63,406 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 105 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 99 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 109 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 110 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 115 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
Speed
Reduce unused JavaScript
3.3 s · 723 KiBAbout 723 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,722 HTML elements
The page has 3,722 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, Klaviyo and Unpkg and others), adding 1.9 MB and 1.4 s of main-thread time.
Render-blocking requests
650 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Google Tag Manager adds 446 ms
446 msGoogle Tag Manager costs a phone 446 ms of main-thread work and 478 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.
Legacy JavaScript
400 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Klaviyo adds 274 ms
274 msKlaviyo costs a phone 274 ms of main-thread work and 516 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.
Improve image delivery
291 KiB12 images could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
Google CDN adds 160 ms
160 msGoogle CDN costs a phone 160 ms of main-thread work and 379 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.
Shopify adds 97 ms
97 msShopify costs a phone 97 ms of main-thread work and 304 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
250 ms · 29 KiB9 files are served with short cache lifetimes, so returning visitors download them again (29 KiB).
Reduce unused CSS
120 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 33.5 s
33.5 sYour largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE NOTICED YOU'RE BROWSING FROM UNITED STATES”.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 565 ms
565 msScripts block taps and scrolling for 565 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 105 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 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 INP: 134 ms
134 msReal visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 311 ms
311 msReal visitors wait 311 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 34.6 MB in 344 requests
34.6 MBYour homepage downloads 34.6 MB in 344 requests on a phone: media 26.0 MB (3), images 5.5 MB (79) and scripts 2.1 MB (137). Under 2 MB keeps phones on slow connections fast.
24 images far larger than shown
1.6 MB24 images are downloaded at several times the size a phone draws them, for example Our_Taster_cups_have_scored_a_prime_spot_to_call_home___Oasi at 600 px wide, shown at 96 px. Resized copies would save about 1.6 MB.
1 image over 500 KB
megamenu line 86): invalid url input weighs 676 KiB. On a phone connection a single image that size takes seconds.
22 images below the first screen load straight away
22 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 9.8 g of CO₂ per visit
9.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.79 g of CO₂e: 1175.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (2 elements)
Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
62 links without text
62 visible links have no text or label, so screen readers cannot say where they go.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h4 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
42 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: 42 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Acme Cups Europe”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (177 characters)
Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
269 internal links, 33 external
The homepage links to 269 pages on acmecups.eu and 33 external pages.
4 checks passed
One H1 headline
Your main headline reads: “We noticed you're browsing from {country}”.
Canonical URL set
The canonical URL is https://acmecups.eu/.
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://acmecups.eu/sitemap.xml.
AI search readiness
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.
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,497 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://acmecups.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://acmecups.eu/collections/roman-range and https://acmecups.eu/collections/bobby, which answer with an error. Visitors hit a dead end and search engines drop them.
5 pages without a meta description
https://acmecups.eu/blogs/news, https://acmecups.eu/pages/contact, https://acmecups.eu/pages/everything, https://acmecups.eu/collections/over-120 and https://acmecups.eu/collections/cups-and-saucers have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://acmecups.eu/collections, https://acmecups.eu/blogs/news, https://acmecups.eu/pages/about, https://acmecups.eu/pages/contact, https://acmecups.eu/collections/classic-range and https://acmecups.eu/collections/cutlery and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://acmecups.eu/collections, https://acmecups.eu/blogs/news, https://acmecups.eu/pages/about, https://acmecups.eu/pages/contact, https://acmecups.eu/collections/classic-range and https://acmecups.eu/collections/cutlery and 7 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 97 found) and read each the way a search engine does.
4 checks passed
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 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://acmecups.eu/Liquid%20error%20(snippets/megamenu%20line%2086):%20invalid%20url%20input.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
43 of 45 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 719 words of copy
The homepage carries about 719 words of visible text.
4 checks passed
47 calls to action
The homepage has 47 calls to action, for example “Shop”, “Contact” and “shop collection”.
62 short forms
62 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
13 cookies set on arrival
13Opening the homepage sets 13 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 acmecups.eu, 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
- Analytics
- Google 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 48 issues on acmecups.eu, including 18 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.