Website review, no card needed
kenro.ie website review
Visit site (opens in a new tab)Reviewed 16 November 202647 issues · 96 checks
This review found 47 issues worth fixing on kenro.ie, 15 of them high impact, across 96 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
74C- #85,531 of 122,251 reviewed websitesbeats 26%
- #53,965 of 69,055 online storesbeats 18%
- #50,754 of 62,911 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 31, 2026 | 1.5 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 12, 2026 | 190 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 224 ms |
| Oct 3, 2026 | 246 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
Speed
Improve image delivery
1.6 s · 2.8 MB15 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
4,901 HTML elements
The page has 4,901 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.1 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, Klaviyo and Clarity and others), adding 13.2 MB and 812 ms of main-thread time.
Shopify adds 256 ms
256 msShopify costs a phone 256 ms of main-thread work and 12.3 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.
Reduce unused JavaScript
900 ms · 286 KiBAbout 286 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 177 KiB20 files are served with short cache lifetimes, so returning visitors download them again (177 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 132 ms
132 msKlaviyo costs a phone 132 ms of main-thread work and 319 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
200 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
200 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.
Minify JavaScript
44 KiB44 KiB could be saved by minifying JavaScript.
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: 22 ms
22 msYour server sent the HTML in 22 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: 20.6 s
20.6 sYour largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.0 s
22.0 sThe page becomes fully interactive after 22.0 s. Good is under 3.8 s.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 190 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 55 ms
55 msScripts block the page for only 55 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.7 MB in 473 requests
15.7 MBYour homepage downloads 15.7 MB in 473 requests on a phone: images 12.2 MB (63), scripts 1.5 MB (190) and other files 1.3 MB (172). Under 2 MB keeps phones on slow connections fast.
24 images far larger than shown
10.9 MB24 images are downloaded at several times the size a phone draws them, for example Kenro_Chedworth_June24__308_web.jpg at 2,400 px wide, shown at 131 px. Resized copies would save about 10.9 MB.
8 images over 500 KB
8 images weigh 7.9 MB together. On a phone connection a single image that size takes seconds.
26 images below the first screen load straight away
26 images further down the page (11.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (3.7 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.
About 4.5 g of CO₂ per visit
4.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.46 g of CO₂e: 535.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (4 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (2 elements)
Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 186 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 14 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://www.kenro.co.uk )”.
575 internal links, 16 external
The homepage links to 575 pages on kenro.ie and 16 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “A UK-based, family-run company specialising in photography & videography equipment and home decor. Take your photo and …”.
Title: 44 characters
Your title is a healthy 44 characters: “Photo & Video Equipment & Home Decor | Kenro”.
Canonical URL set
The canonical URL is https://www.kenro.ie/.
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.kenro.ie/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.kenro.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.
Text is in the HTML
Your server sends the page's text in the HTML (2,844 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without an H1
https://www.kenro.ie/a/wishlist, https://www.kenro.ie/collections/photo-frames, https://www.kenro.ie/collections/strut-mounts-photo-folders and https://www.kenro.ie/products/strut-mounts 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 197 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 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.
Every page has a meta description
All 5 pages that loaded have a meta description.
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 5 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136019957&tm=shpfy_ui&Ver=2&mid=bdbbcf4b-59b5-49fe-982e-e8cef8b576d6&bo=1&sid=e7617b40e20811f1bad74b563032e1aa&vid=e7616580e20811f1a350a3d15e8d4fb5&vids=1&msclkid=N&pi.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
375 of 382 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 3,441 words of copy
The homepage carries about 3,441 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All Photo Frames” and “Shop All Photo Mounts & Folders”.
105 calls to action
The homepage has 105 calls to action, for example “Shop All Photo Frames”, “Shop All Photo Mounts & Folders” and “Strut Mounts Shop product”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 86 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 4 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (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.
48 other companies contacted
Loading the homepage contacts 48 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 kenro.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Judge Me Reviews · Klaviyo Email Marketing Sms · Inbox · Gdpr Backpack · Boo Eu Withdrawal Button · webmarked.net · trafficmanager.net · nice-team.net · kenro.co.uk · amazonaws.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
- Tailwind CSS
- 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 47 issues on kenro.ie, including 18 speed issues, 2 SEO issues and 2 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.