Website review, no card needed

gloriaskincare.de logo

gloriaskincare.de website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 87 checks

This review found 39 issues worth fixing on gloriaskincare.de, 13 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.3 sAug 22Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
225 ms208 msAug 22Oct 31214 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026223 ms
Aug 29, 2026210 ms
Sep 5, 2026210 ms
Sep 12, 2026212 ms
Sep 19, 2026212 ms
Sep 26, 2026216 ms
Oct 3, 2026220 ms
Oct 10, 2026221 ms
Oct 17, 2026220 ms
Oct 24, 2026220 ms
Oct 31, 2026214 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

Full-page screenshot of gloriaskincare.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gloriaskincare.de at 2.1 s2.1 s
  2. gloriaskincare.de at 4.3 s4.3 s
  3. gloriaskincare.de at 6.4 s6.4 s
  4. gloriaskincare.de at 8.5 s8.5 s
  5. gloriaskincare.de at 10.7 s10.7 s
  6. gloriaskincare.de at 12.8 s12.8 s
  7. gloriaskincare.de at 14.9 s14.9 s
  8. gloriaskincare.de at 17.1 s17.1 s

Speed

11 to fix56
  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 11.8 s

    A phone's processor spends 11.8 s on main-thread work while loading, 4.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 (Shopify, Clarity and Other Google APIs/SDKs and others), adding 1.8 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 749 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    710 ms · 136 KiB

    About 136 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 710 ms faster on a phone.

  • Use efficient cache lifetimes

    350 ms · 398 KiB

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

  • Shopify adds 545 ms

    545 ms

    Shopify costs a phone 545 ms of main-thread work and 1,002 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.

  • Clarity adds 416 ms

    416 ms

    Clarity costs a phone 416 ms of main-thread work and 29 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.

  • Klaviyo adds 229 ms

    229 ms

    Klaviyo costs a phone 229 ms of main-thread work and 334 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.

  • 2,060 HTML elements

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

  • Improve image delivery

    217 KiB

    5 images could be 217 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 14 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    47 KiB

    Polyfills for old browsers add 47 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.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 70 ms

    70 ms

    Your server sent the HTML in 70 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • 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.

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “91B25312-9324-429F-80DE-3191C1D9A5B5.png”.

  • Real-user TTFB: 849 ms

    849 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 349 ms

    349 ms

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 184 ms

    184 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 475 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 475 requests on a phone: scripts 1.8 MB (111), other files 1.6 MB (302) and images 567 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8490
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 16 tap targets too small

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

  • 8 text elements with low contrast

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

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • 4 links without text

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

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (4 elements)

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • 4 H1 headlines

    There are 4 <h1> headlines (“”, “Needless Shots Set – Bio-Microneedling für Zuhause” and “Milky Toner”). One clear main headline is easier for people and search engines.

  • Meta description is long (230 characters)

    Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 150 internal links, 4 external

    The homepage links to 150 pages on gloriaskincare.de and 4 external pages.

6 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “Gloria Skincare - BB-Cream, 2% BHA Maske & Anti-Pickel Set”.

  • Canonical URL set

    The canonical URL is https://gloriaskincare.de/.

  • Structured data in place

    Structured data found: 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://gloriaskincare.de/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,604 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://gloriaskincare.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://gloriaskincare.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://gloriaskincare.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://gloriaskincare.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages share a meta description

    https://gloriaskincare.de/collections/needless-shots, https://gloriaskincare.de/pages/meine-geschichte, https://gloriaskincare.de/collections/morgenroutine, https://gloriaskincare.de/collections/abendroutine, https://gloriaskincare.de/pages/erstelle-dein-set and https://gloriaskincare.de/collections/alle-produkte and 7 others use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://gloriaskincare.de/products/needless-shots, https://gloriaskincare.de/collections/morgenroutine, https://gloriaskincare.de/collections/alle-produkte, https://gloriaskincare.de/customer_authentication/redirect, https://gloriaskincare.de/collections/all and https://gloriaskincare.de/collections/bestseller and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://gloriaskincare.de/products/needless-shots, https://gloriaskincare.de/collections/needless-shots, https://gloriaskincare.de/collections/morgenroutine, https://gloriaskincare.de/collections/abendroutine, https://gloriaskincare.de/collections/bestseller and https://gloriaskincare.de/collections/gbc and 3 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 34 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.

  • 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.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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.

  • 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 912 words of copy

    The homepage carries about 912 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • 24 short forms

    24 short forms (5 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 68 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 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.

  • 51 other companies contacted

    Loading the homepage contacts 51 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 gloriaskincare.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 25 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews · Gempages Builder · Seal Subscriptions · Gsc Countdown Timer · Uppromote Affiliate · Fbp Fast Bundle · Triplewhale · Venon · Fly Bundles Upsells · Eg Auto Add To Cart · Echo All In One Fixed Bundles · Opus Cart Drawer Cart Upsell · Stape Remix · Checkout Regeln Grosse Warenkoerbe 2026 · Affliate By Secomapp · Chatarmin · Gift Box Builder · Referral And Affiliates · Free Gift · stationmade.com · shopclimb.com · nfcube.com · cloudfront.net · kaktusapp.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
Bootstrap
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on gloriaskincare.de, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25