Website review, no card needed
kikiskitchen.de website review
Visit site (opens in a new tab)Reviewed 6 November 202648 issues · 91 checks
This review found 48 issues worth fixing on kikiskitchen.de, 20 of them high impact, across 91 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64D- #111,677 of 118,736 reviewed websitesbeats 5%
- #65,559 of 67,418 online storesbeats 2%
- #60,097 of 61,467 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 163 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 207 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 209 ms |
| Jul 18, 2026 | 214 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 216 ms |
| Aug 8, 2026 | 213 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 207 ms |
| Aug 29, 2026 | 214 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 237 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 236 ms |
| Oct 3, 2026 | 232 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 224 ms |
| Oct 24, 2026 | 225 ms |
| Oct 31, 2026 | 230 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
How it loaded on a phone
2.2 s
4.5 s
6.7 s
8.9 s
11.2 s
13.4 s
15.7 s
17.9 s
Speed
Improve image delivery
37.7 s · 29.3 MB30 images could be 29.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 37.7 s faster on a phone.
Main-thread work: 21.1 s
A phone's processor spends 21.1 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
hcaptcha.com adds 1.9 s
1.9 shcaptcha.com costs a phone 1.9 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.4 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 10
10/100Your mobile performance score is 10. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,532 HTML elements
The page has 6,532 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, Shopify and PayPal and others), adding 4.0 MB and 4.5 s of main-thread time.
Reduce unused JavaScript
1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page.
Shopify adds 873 ms
873 msShopify costs a phone 873 ms of main-thread work and 1.8 MB 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 adds 726 ms
726 msPayPal costs a phone 726 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.
Use efficient cache lifetimes
50 ms · 574 KiB64 files are served with short cache lifetimes, so returning visitors download them again (574 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 616 ms. During a long task the page ignores taps.
cloudfront.net adds 461 ms
461 mscloudfront.net costs a phone 461 ms of main-thread work and 59 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.
rebuyengine.com adds 251 ms
251 msrebuyengine.com costs a phone 251 ms of main-thread work and 298 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
131 KiBPolyfills for old browsers add 131 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
52 KiB52 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
30 KiBAbout 30 KiB of CSS is downloaded but never applied 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 52.3 s
52.3 sYour largest element takes 52.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.7 s
25.7 sVisually, the page fills in at 25.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 124.2 s
124.2 sThe page becomes fully interactive after 124.2 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.501
0.501The layout shifts by 0.501 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 300 ms
300 msReal visitors wait 300 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 525 ms
525 msReal visitors wait 525 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
8 images over 500 KB
8 images weigh 144.2 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
108.4 MB8 images are downloaded at several times the size a phone draws them, for example matcha_gif_5a182d18-a693-477b-b483-7fc138069635.gif at 720 px wide, shown at 76 px. Resized copies would save about 108.4 MB.
Page weight: 36.5 MB in 658 requests
36.5 MBYour homepage downloads 36.5 MB in 658 requests on a phone: images 30.8 MB (119), scripts 3.5 MB (302) and other files 1.2 MB (168). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (144.2 MB) are 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.
7 images below the first screen load straight away
7 images further down the page (192 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 10.3 g of CO₂ per visit
10.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.34 g of CO₂e: 1241.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 text elements with low contrast
30 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)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
58 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 58 passed and 4 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Kikis Kitchen”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “JETZT NEU ✨”). One clear main headline is easier for people and search engines.
186 internal links, 27 external
The homepage links to 186 pages on kikiskitchen.de and 27 external pages.
6 checks passed
Meta description: 107 characters
Your meta description is 107 characters: “Entdecke jetzt die besten Back- & Kochprodukte, Bio Lebensmittel, Brotaufstriche, Saucen und Trendprodukte.”.
Canonical URL set
The canonical URL is https://www.kikiskitchen.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://www.kikiskitchen.de/sitemap.xml.
AI search readiness
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,769 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.kikiskitchen.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.kikiskitchen.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.kikiskitchen.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://www.kikiskitchen.de/collections/all, https://www.kikiskitchen.de/customer_authentication/redirect, https://www.kikiskitchen.de/collections/kikis-cream, https://www.kikiskitchen.de/policies/shipping-policy, https://www.kikiskitchen.de/collections/kikis-tortenringe and https://www.kikiskitchen.de/collections/kikis-springformen and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.kikiskitchen.de/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.kikiskitchen.de/customer_authentication/redirect, https://www.kikiskitchen.de/collections/kikis-springformen, https://www.kikiskitchen.de/collections/kikis-topfe-pfannen, https://www.kikiskitchen.de/collections/kikis-saucen, https://www.kikiskitchen.de/collections/kikis-kaffee and https://www.kikiskitchen.de/collections/kikis-bio-lebensmittel took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 82 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
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) AbortError: The play() request was interrupted by a new load request. https://goo.gl/LdLk22”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
24 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,005 words of copy
The homepage carries about 1,005 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Zum Shop” and “◎ Start Picking Placement”.
35 short forms
35 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and 1 trust badge.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 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.
35 other companies contacted
Loading the homepage contacts 35 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 kikiskitchen.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 21 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Frequently Bought · C Hub Customer Accounts · Dr Stacked Discounts · Klaviyo Email Marketing Sms · Regios Discounts · Bloggo Blog Search Bar · Omega Auto Tagger · Judge Me Reviews · Page Speed Optimizer · Sternify · Section Factory · Dealeasy · Forms · Bestpush · Rubik Combined Listings · Madgic Checkout Validation · goaffpro.com · trustpilot.com · kaktusapp.com · rebuyengine.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on kikiskitchen.de, including 24 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.