Website review, no card needed

josephinen.com logo

josephinen.com website review

Visit site (opens in a new tab)Reviewed 11 November 202642 issues · 85 checks

This review found 42 issues worth fixing on josephinen.com, 13 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
2.6 s1.8 sMay 23Nov 72.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
226 ms177 msMay 23Nov 7199 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026183 ms
May 30, 2026185 ms
Jun 6, 2026190 ms
Jun 13, 2026196 ms
Jun 20, 2026195 ms
Jun 27, 2026197 ms
Jul 4, 2026196 ms
Jul 11, 2026200 ms
Jul 18, 2026204 ms
Jul 25, 2026203 ms
Aug 1, 2026197 ms
Aug 8, 2026206 ms
Aug 15, 2026207 ms
Aug 22, 2026212 ms
Aug 29, 2026220 ms
Sep 5, 2026212 ms
Sep 12, 2026211 ms
Sep 19, 2026210 ms
Sep 26, 2026209 ms
Oct 3, 2026208 ms
Oct 10, 2026208 ms
Oct 17, 2026204 ms
Oct 24, 2026203 ms
Oct 31, 2026202 ms
Nov 7, 2026199 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 josephinen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. josephinen.com at 1.9 s1.9 s
  2. josephinen.com at 3.8 s3.8 s
  3. josephinen.com at 5.7 s5.7 s
  4. josephinen.com at 7.6 s7.6 s
  5. josephinen.com at 9.5 s9.5 s
  6. josephinen.com at 11.4 s11.4 s
  7. josephinen.com at 13.3 s13.3 s
  8. josephinen.com at 15.2 s15.2 s

Speed

13 to fix49
  • Reduce unused JavaScript

    1.9 s · 495 KiB

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

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 6.3 s

    A phone's processor spends 6.3 s on main-thread work while loading, 2.8 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 (Google Tag Manager, Clarity and Klaviyo and others), adding 1.6 MB and 1.3 s of main-thread time.

  • Render-blocking requests

    950 ms

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

  • Use efficient cache lifetimes

    750 ms · 139 KiB

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

  • Google Tag Manager adds 461 ms

    461 ms

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

  • Legacy JavaScript

    350 ms · 47 KiB

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

  • Clarity adds 368 ms

    368 ms

    Clarity costs a phone 368 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.

  • Improve image delivery

    289 KiB

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

  • 2,809 HTML elements

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

  • Klaviyo adds 232 ms

    232 ms

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

  • Shopify adds 45 ms

    45 ms

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

  • Reduce unused CSS

    150 ms · 84 KiB

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

  • 9 long tasks on the main thread

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

  • Minify CSS

    29 KiB

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 16.5 s

    16.5 s

    Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Shape of Taste – Josephinenhütte”.

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 421 ms

    421 ms

    Scripts block taps and scrolling for 421 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.

  • Tap response (INP) held steady for real visitors

    +9%

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

6 checks passed
  • Real-user INP: 179 ms

    179 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 582 ms

    582 ms

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

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

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 16.3 MB in 406 requests

    16.3 MB

    Your homepage downloads 16.3 MB in 406 requests on a phone: media 12.3 MB (2), scripts 1.6 MB (102) and other files 1.4 MB (257). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    116 KiB

    3 images are downloaded at several times the size a phone draws them, for example josephinenhutte-mystik-josephine-no2-universal-wine-glass-re at 1,750 px wide, shown at 312 px. Resized copies would save about 116 KiB.

  • 1 image below the first screen load straight away

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

  • About 4.6 g of CO₂ per visit

    4.61 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9696
  • 4 tap targets too small

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

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

    All page content should be contained by landmarks: 8 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.

2 checks passed
  • Every image has alt text

    All 81 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9290
  • 32 links with vague text

    32 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Josephinenhütte” and “Josephinenhütte”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 173 internal links, 7 external

    The homepage links to 173 pages on josephinen.com and 7 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Visionary design & finest craftsmanship: Each glass from Josephinenhütte is a mouth-blown unique piece. Made in Europe.”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Josephinenhütte – World's Finest Glasses”.

  • Canonical URL set

    The canonical URL is https://josephinen.com/.

  • 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://josephinen.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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 (1,432 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix60
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 2 pages share a title

    https://josephinen.com/collections/josephine and https://josephinen.com/collections/all all use the title “Josephine Collection · Josephinenhütte”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://josephinen.com/pages/newsletter, https://josephinen.com/pages/taste, https://josephinen.com/pages/kurt-josef-zalto, https://josephinen.com/pages/heritage, https://josephinen.com/blogs/stories and https://josephinen.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://josephinen.com/collections/josephine and https://josephinen.com/collections/all use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://josephinen.com/pages/taste, https://josephinen.com/pages/manufacture, https://josephinen.com/pages/kurt-josef-zalto, https://josephinen.com/pages/heritage, https://josephinen.com/blogs/stories and https://josephinen.com/customer_authentication/redirect and 1 other 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 58 found) and read each the way a search engine does.

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=148005045&tm=gtm002&Ver=2&mid=3c17eb53-d29e-4a0b-a16a-03ef8d5a8d3f&bo=1&sid=5efa5d00dd6711f1a174258f55b825a2&vid=5efa8dd0dd6711f1b01411c774b21d8c&vids=1&msclkid=N&pi=9.

  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    51 of 59 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 863 words of copy

    The homepage carries about 863 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Start shopping” and “Request cancellation”.

  • 20 short forms

    20 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 4 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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 josephinen.com, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Langify · Klaviyo Email Marketing Sms · Cozy Country Redirect · Gorgias Live Chat Helpdesk · Microsoft Clarity · Reviews Co Uk Product And Merchant Review Collection · Access Pro · digitaloceanspaces.com · 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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Munich

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on josephinen.com, including 21 speed issues, 3 SEO issues and 3 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

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