Website review, no card needed
ninjakitchen.ie website review
Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 72 checks
This review found 26 issues worth fixing on ninjakitchen.ie, 11 of them high impact, across 72 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
77C- #68,815 of 123,924 reviewed websitesbeats 39%
- #44,541 of 69,719 online storesbeats 31%
- #42,361 of 63,424 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 831 ms |
| May 23, 2026 | 826 ms |
| May 30, 2026 | 816 ms |
| Jun 6, 2026 | 818 ms |
| Jun 13, 2026 | 836 ms |
| Jun 20, 2026 | 848 ms |
| Jun 27, 2026 | 873 ms |
| Jul 4, 2026 | 891 ms |
| Jul 11, 2026 | 897 ms |
| Jul 18, 2026 | 900 ms |
| Jul 25, 2026 | 889 ms |
| Aug 1, 2026 | 867 ms |
| Aug 8, 2026 | 858 ms |
| Aug 15, 2026 | 857 ms |
| Aug 22, 2026 | 871 ms |
| Aug 29, 2026 | 884 ms |
| Sep 5, 2026 | 894 ms |
| Sep 12, 2026 | 893 ms |
| Sep 19, 2026 | 870 ms |
| Sep 26, 2026 | 852 ms |
| Oct 3, 2026 | 830 ms |
| Oct 10, 2026 | 806 ms |
| Oct 17, 2026 | 803 ms |
| Oct 24, 2026 | 795 ms |
| Oct 31, 2026 | 782 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 119 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 119 ms |
| Oct 31, 2026 | 118 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
4.2 s · 676 KiB12 images could be 676 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Render-blocking requests
750 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Shopify adds 166 ms
166 msShopify costs a phone 166 ms of main-thread work and 552 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 895 KiB and 354 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 160 KiB12 files are served with short cache lifetimes, so returning visitors download them again (160 KiB).
Reduce unused JavaScript
173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
38 KiB38 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 603 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 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.
Real-user CLS: 0.62
0.62For real visitors the layout shifts by 0.62 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.723
0.723The layout shifts by 0.723 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
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 119 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 94 ms
94 msReal visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 339 ms
339 msReal visitors wait 339 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 12 ms
12 msScripts block the page for only 12 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.9 MB in 230 requests
9.9 MBYour homepage downloads 9.9 MB in 230 requests on a phone: media 6.8 MB (4), images 1.4 MB (31) and other files 769 KiB (98). Under 2 MB keeps phones on slow connections fast.
About 2.8 g of CO₂ per visit
2.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.81 g of CO₂e: 336.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (8 elements).
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Black Friday Starts Now”). One clear main headline is easier for people and search engines.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
116 internal links, 11 external
The homepage links to 116 pages on ninjakitchen.ie and 11 external pages.
7 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Shop Ninja’s full range of Air Fryers, Blenders, Food Processors, Grills and Multi-Cookers. Fast delivery across Irelan…”.
Title: 57 characters
Your title is a healthy 57 characters: “Ninja Ireland - Kitchen Appliances, Air Fryers & Blenders”.
Canonical URL set
The canonical URL is https://www.ninjakitchen.ie/.
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.ninjakitchen.ie/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.ninjakitchen.ie/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.
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.
Other pages
1 page without a meta description
https://www.ninjakitchen.ie/pages/microwaves has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.ninjakitchen.ie/collections/offers, https://www.ninjakitchen.ie/pages/microwaves and https://www.ninjakitchen.ie/products/ninja-belgian-waffle-maker-bw1000uk 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 52 found) and read each the way a search engine does.
5 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
4 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Shop all offers”, “Shop now” and “Shop Now”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: 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
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
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 ninjakitchen.ie, 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
Pandectes Gdpr · Klaviyo Email Marketing Sms · Powerful Form Builder · Instafeed · Gdpr Cookie Consent · Deco Labels Badges · Free Gift · bazaarvoice.com · nfcube.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
- E-commerce
- Shopify
- Hosting
- Shopify Hosted
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on ninjakitchen.ie, including 10 speed issues, 2 SEO issues and 4 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.