123.live website review

About 789 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

About 253 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 11 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

9 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

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

Google Tag Manager costs a phone 287 ms of main-thread work and 203 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.

1-2-3.tv costs a phone 0 ms of main-thread work and 548 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.

5 third-party services load with your homepage (Google Tag Manager, adsdefender.com and cookiefirst.com and others), adding 904 KiB and 347 ms of main-thread time.

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

Desktop scores 40 but mobile only 11. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

For real visitors the layout shifts by 0.86 (75th percentile). Good is under 0.1.

The first text or image appears after 7.7 s on a phone. Good is under 1.8 s.

Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir setzen auf unserer Webseite Cookies ein, um die Nutzung…”.

The layout shifts by 0.899 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Scripts block taps and scrolling for 961 ms in total while the page loads. Good is under 200 ms.

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

Real visitors wait 354 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors wait 973 ms for your server to start answering (75th percentile). Good is under 800 ms.

7 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 2.6 MB in 93 requests on a phone: scripts 1.3 MB (21), images 784 KiB (55) and stylesheets 273 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example show_1166_pv24.webp at 514 px wide, shown at 85 px. Resized copies would save about 144 KiB.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

5 visible links have no text or label, so screen readers cannot say where they go.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (5 elements).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 417 pages on 123.live and 19 external pages.

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.

There is no /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.

/show/luca-lorenzo, /show/diamant-d-or, /show/jepara, /Mode/Damenmode and /Mode/Damenmode/Shirts have no <title>, so Google invents the link text in results.

/neu-hier is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/sale and /neu-hier all use the title “123.live”. Search engines can't tell which page to show for a search, so each competes with the others.

/sale, /neu-hier, /show/luca-lorenzo, /show/diamant-d-or, /show/jepara and /Mode/Damenmode and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /sale, whose canonical is /shop. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/shop, /sale, /wochenuebersicht, /Mode, /show/luca-lorenzo and /show/diamant-d-or and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/show/luca-lorenzo, /show/diamant-d-or, /show/jepara, /Mode/Damenmode and /Mode/Damenmode/Shirts 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 196 found) and read each the way a search engine does.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

3 links go through two or more redirects, for example https://www.123.live/neu-hier/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

123.live is registered until Oct 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

123.live has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

123.live's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,846 words of visible text.

123.live has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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 5 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.