Website review, no card needed
atletica.de website review
Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 82 checks
This review found 37 issues worth fixing on atletica.de, 10 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81B- #41,449 of 124,145 reviewed websitesbeats 61%
- #27,457 of 69,798 online storesbeats 54%
- #26,454 of 63,482 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 123 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 171 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
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.9 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 (zohocdn.com, Shopify and Klaviyo and others), adding 2.4 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
zohocdn.com adds 731 ms
731 mszohocdn.com costs a phone 731 ms of main-thread work and 1.8 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.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 421 ms. During a long task the page ignores taps.
2,712 HTML elements
The page has 2,712 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 208 KiBAbout 208 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
140 KiB8 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Use efficient cache lifetimes
59 KiB10 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
1 checks passed
Server response: 42 ms
42 msYour server sent the HTML in 42 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: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 908 ms
908 msReal visitors wait 908 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 545 ms
545 msScripts block taps and scrolling for 545 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 186 requests
4.7 MBYour homepage downloads 4.7 MB in 186 requests on a phone: scripts 2.2 MB (80), media 820 KiB (1) and images 684 KiB (47). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
App-banner-mobile.webp 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 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 244 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“ATLETICA”, “ATLETICA” and “ATLETICA”). One clear main headline is easier for people and search engines.
Meta description is long (213 characters)
Your meta description is 213 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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
520 internal links, 11 external
The homepage links to 520 pages on atletica.de and 11 external pages.
5 checks passed
Title: 58 characters
Your title is a healthy 58 characters: “ATLETICA Fitness Equipment für zu Hause | Entwickelt in DE”.
Canonical URL set
The canonical URL is https://atletica.de/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://atletica.de/sitemap.xml.
AI search readiness
No llms.txt
There is no https://atletica.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,208 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://atletica.de/collections/limited-edition-sets, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages without an H1
https://atletica.de/pages/bestellablauf-zahlung-versand and https://atletica.de/collections/power-racks-all 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 127 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 2 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 2 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 406 words of copy
The homepage carries about 406 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 5 mores (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
42 other companies contacted
Loading the homepage contacts 42 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 atletica.de, 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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gorgias Live Chat Helpdesk · Speedsize Ai Image Optimizer · Klaviyo Email Marketing Sms · Loyalty Rewards And Referrals · Dropinblog · Specification And Compare · Gdpr Backpack · Delivery Timer · Iwish · Bestpush · loox.io · goaffpro.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on atletica.de, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.