Programmable

Website review, no card needed

cupcakehexerl.at logo

cupcakehexerl.at website review

Visit site (opens in a new tab)Reviewed 12 November 202627 issues · 73 checks

This review found 27 issues worth fixing on cupcakehexerl.at, 12 of them high impact, across 73 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

Site score

72C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.0 s814 msMay 23Nov 73.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.6 s
Sep 5, 20262.5 s
Sep 12, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.4 s
Oct 31, 20263.6 s
Nov 7, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
82 ms74 msMay 23Nov 781 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202676 ms
Jun 6, 202675 ms
Jun 13, 202675 ms
Aug 29, 202679 ms
Sep 5, 202676 ms
Sep 12, 202678 ms
Oct 24, 202681 ms
Oct 31, 202679 ms
Nov 7, 202681 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

www.cupcakehexerl.at (opens in a new tab)
Full-page screenshot of cupcakehexerl.at (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cupcakehexerl.at at 0.4 s0.4 s
  2. cupcakehexerl.at at 0.8 s0.8 s
  3. cupcakehexerl.at at 1.1 s1.1 s
  4. cupcakehexerl.at at 1.5 s1.5 s
  5. cupcakehexerl.at at 1.9 s1.9 s
  6. cupcakehexerl.at at 2.3 s2.3 s
  7. cupcakehexerl.at at 2.6 s2.6 s
  8. cupcakehexerl.at at 3.0 s3.0 s

Speed

2 to fix78

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 78

    78/100

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

  • Improve image delivery

    250 ms · 74 KiB

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

  • Legacy JavaScript

    250 ms · 35 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (cdn-cookieyes.com, WordPress Site Stats and Google Fonts and others), adding 251 KiB and 59 ms of main-thread time.

  • Reduce unused JavaScript

    21 KiB

    About 21 KiB of JavaScript is downloaded but never used on this page.

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

2 checks passed

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 119 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 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.

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CupcakeHexerl Auf der Suche nach dem perfekten Candy table”.

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Largest content (LCP) got 202% slower for real visitors

    +202%

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

  • Time to Interactive: 5.2 s

    5.2 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

5 checks passed

  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 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.

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.077

    0.077

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.24 g

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

4 checks passed

  • Page weight: 872 KiB in 51 requests

    872 KiB

    Your homepage downloads 872 KiB in 51 requests on a phone: images 585 KiB (19), scripts 126 KiB (11) and fonts 97 KiB (7). That is a lean page.

  • 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

2 to fixGoogle 9497

  • 4 text elements with low contrast

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

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

7 to fixGoogle 5041

  • Page is set to noindex

    The robots meta tag says “noindex, follow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (27 characters)

    Your title is only 27 characters: “Hauptseite - Cupcake Hexerl”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 35 internal links, 2 external

    The homepage links to 35 pages on cupcakehexerl.at and 2 external pages.

4 checks passed

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Person and WebPage.

  • 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.cupcakehexerl.at/sitemap.xml.

AI search readiness

1 to fix88

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, 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.

  • No llms.txt

    There is no https://www.cupcakehexerl.at/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.

2 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 (305 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95

  • 15 pages without a meta description

    https://www.cupcakehexerl.at/category/bewusstes-backen, https://www.cupcakehexerl.at/category/cake-pops-cookie-pops, https://www.cupcakehexerl.at/category/cookies-keks, https://www.cupcakehexerl.at/category/cremen-eis, https://www.cupcakehexerl.at/category/cupcakes-muffins and https://www.cupcakehexerl.at/category/suesse-getraenke and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 2 small tap targets

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

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42

  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

    The homepage carries about 286 words of visible text.

1 checks passed

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 6 other companies contacted

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

2 checks passed

  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 cupcakehexerl.at, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Nessus GmbH

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on cupcakehexerl.at, including 10 speed issues, 7 SEO issues and 5 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