carbonphone.de website review

15 files are served with short cache lifetimes, so returning visitors download them again (216 KiB).

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

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

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

8 third-party services load with your homepage (PayPal, Shopify and staq-cdn.com and others), adding 782 KiB and 521 ms of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

A phone's processor spends 3.5 s on main-thread work while loading, 958 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Shopify costs a phone 231 ms of main-thread work and 466 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.

PayPal costs a phone 252 ms of main-thread work and 232 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.

8 images could be 204 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 33 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CarbonPhone – Smartphones neu und geprüft gebraucht kaufen”.

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your homepage downloads 3.2 MB in 318 requests on a phone: other files 1.0 MB (151), scripts 994 KiB (106) and images 938 KiB (47). Under 2 MB keeps phones on slow connections fast.

1 image (44 KiB) is 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.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 11 characters: “CarbonPhone”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

The homepage links to 255 pages on carbonphone.de and 4 external pages.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://carbonphone.de/collections/xiaomi/Smartphones, whose canonical is https://carbonphone.de/collections/xiaomi/smartphones. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://carbonphone.de/collections/top-deals, https://carbonphone.de/collections/handys-smartphones, https://carbonphone.de/collections/xiaomi/Smartphones and https://carbonphone.de/collections/huawei/Smartphones have no <h1> headline, so visitors and search engines get no clear main topic.

https://carbonphone.de/collections/top-deals and https://carbonphone.de/collections/handys-smartphones 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.

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

35 of 151 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Unexpected token ')'”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 728 words of visible text.

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.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.