Website review, no card needed
aeris.de website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 93 checks
This review found 40 issues worth fixing on aeris.de, 14 of them high impact, across 93 checks. The most urgent: page weight: 14.9 MB in 298 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
83B- #27,005 of 117,615 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #17,312 of 61,018 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 188 ms |
| May 23, 2026 | 180 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 183 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 214 ms |
| Jul 18, 2026 | 208 ms |
| Jul 25, 2026 | 208 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 201 ms |
| Aug 29, 2026 | 204 ms |
| Sep 5, 2026 | 200 ms |
| Sep 12, 2026 | 201 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 237 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 261 ms |
| Oct 31, 2026 | 262 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
4,634 HTML elements
The page has 4,634 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.4 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 (zapier.com, Google Tag Manager and Shopify and others), adding 3.3 MB and 1.4 s of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
974 KiBAbout 974 KiB of JavaScript is downloaded but never used on this page.
zapier.com adds 502 ms
502 mszapier.com costs a phone 502 ms of main-thread work and 1.4 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.
Google Tag Manager adds 484 ms
484 msGoogle Tag Manager costs a phone 484 ms of main-thread work and 538 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.
Render-blocking requests
450 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 119 ms
119 msShopify costs a phone 119 ms of main-thread work and 1.0 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.
Improve image delivery
247 KiB14 images could be 247 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
200 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.
Reduce unused CSS
137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
66 KiB10 files are served with short cache lifetimes, so returning visitors download them again (66 KiB).
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
Minify CSS
8 KiB8 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: 21 ms
21 msYour server sent the HTML in 21 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: 27.5 s
27.5 sThe page becomes fully interactive after 27.5 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden auf unserer Website Cookies oder andere Funkt…”. Most of its time is element render delay (2.6 s).
Real-user INP: 319 ms
319 msReal visitors wait 319 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 188 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 293 ms
293 msScripts block taps and scrolling for 293 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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.02
0.02For real visitors the layout shifts by 0.02 (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.
Real-user TTFB: 558 ms
558 msReal visitors wait 558 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 14.9 MB in 298 requests
14.9 MBYour homepage downloads 14.9 MB in 298 requests on a phone: media 9.3 MB (1), scripts 2.9 MB (94) and images 1.2 MB (49). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example AGR_Logo_black.webp at 390 px wide, shown at 86 px. Resized copies would save about 62 KiB.
3 images in older formats
3 images (190 KiB) 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.
About 4.2 g of CO₂ per visit
4.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.21 g of CO₂e: 505.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail 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.
21 form fields without a label
21 form fields have no label, so screen readers announce an empty box and autofill guesses.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (12 elements)
Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
36 links crawlers can't follow
36 links have no real href, so search engines can't follow them.
144 internal links, 4 external
The homepage links to 144 pages on aeris.de and 4 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Erlebe, wie die ergonomischen Aeris Bürostühle dich bei der Arbeit in Bewegung halten. Entdecke jetzt den Aeris Swopper…”.
One H1 headline
Your main headline reads: “Aeris”.
Title: 33 characters
Your title is a healthy 33 characters: “Ergonomische Bürostühle von Aeris”.
Canonical URL set
The canonical URL is https://www.aeris.de/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://www.aeris.de/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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,744 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.aeris.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.aeris.de/pages/jubilaeum-swopper and https://www.aeris.de/collections/aeris-muvman-industry are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://www.aeris.de/collections/all and https://www.aeris.de/products/aeris-numo-kufengestell-sitzschalenfarbe-schwarz have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.aeris.de/products/aeris-numo-task-gestellfarbe-schwarz-sitzbezug-hellgrau-meliert-copy, whose canonical is https://www.aeris.de/products/aeris-numo-task-gestellfarbe-schwarz-sitzbezug-schwarz. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.aeris.de/collections/all and https://www.aeris.de/products/aeris-swopper-wollmischung-capture-gruen have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.aeris.de/collections/all, https://www.aeris.de/products/aeris-swopper-wollmischung-capture-gruen and https://www.aeris.de/products/aeris-numo-task-gestellfarbe-schwarz-sitzbezug-hellgrau-meliert-copy 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.
2 pages slow to respond
https://www.aeris.de/products/aeris-linu-kufengestell-sitzschalenfarbe-schwarz and https://www.aeris.de/collections/buerostuehle took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 57 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=134618422&Ver=2&mid=68495ba3-eef0-416c-acba-d262e7b66a19&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Ergonomische%20B%C3%BCrost%C3%BChle%20von%20Aeris&p=ht.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
32 of 33 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 1,134 words of copy
The homepage carries about 1,134 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
1 call to action
The homepage has 1 call to action, for example “Shop now”.
24 short forms
24 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 4 of them by other companies (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.
38 other companies contacted
Loading the homepage contacts 38 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 aeris.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Multifeeds · Powerful Form Builder · Gdpr Cookie Consent · Orbe Geolocation · Forms · Eu Tax Exemption Easy · Agentic Ai Search Discovery · hextom.com · cloudfront.net
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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Haar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on aeris.de, including 17 speed issues and 1 SEO issue. 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.