Website review, no card needed
mrralph.co.nz website review
Visit site (opens in a new tab)Reviewed 9 November 202642 issues · 91 checks
This review found 42 issues worth fixing on mrralph.co.nz, 14 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
76C- #76,537 of 126,417 reviewed websitesbeats 35%
- #48,635 of 70,458 online storesbeats 26%
- #46,015 of 63,958 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 102 ms |
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 131 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 134 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
Render-blocking requests
1.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 6.9 MB and 1.0 s of main-thread time.
Reduce unused JavaScript
880 ms · 551 KiBAbout 551 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 880 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Shopify adds 168 ms
168 msShopify costs a phone 168 ms of main-thread work and 5.7 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 CSS
580 ms · 127 KiBAbout 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.
Google Tag Manager adds 430 ms
430 msGoogle Tag Manager costs a phone 430 ms of main-thread work and 521 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.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,499 HTML elements
The page has 2,499 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 113 ms
113 msKlaviyo costs a phone 113 ms of main-thread work and 341 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
200 ms · 238 KiB16 files are served with short cache lifetimes, so returning visitors download them again (238 KiB).
Improve image delivery
250 ms · 63 KiB3 images could be 63 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Minify CSS
130 ms · 11 KiB11 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 6 ms
6 msYour server sent the HTML in 6 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 TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 102 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 378 ms
378 msScripts block taps and scrolling for 378 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.9 MB in 321 requests
8.9 MBYour homepage downloads 8.9 MB in 321 requests on a phone: media 5.3 MB (1), scripts 2.0 MB (156) and other files 805 KiB (119). Under 2 MB keeps phones on slow connections fast.
About 2.5 g of CO₂ per visit
2.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.51 g of CO₂e: 301.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
Links must have discernible text (4 elements)
Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail 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.
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 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
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 51 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 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.
Meta description is long (317 characters)
Your meta description is 317 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://mrralph.co.nz/search?q={search_term_string}")”.
151 internal links, 10 external
The homepage links to 151 pages on mrralph.co.nz and 10 external pages.
5 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Mr Ralph Lighting NZ - Beautiful Lighting Products across NZ”.
Canonical URL set
The canonical URL is https://mrralph.co.nz/.
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://mrralph.co.nz/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (661 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mrralph.co.nz/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://mrralph.co.nz/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://mrralph.co.nz/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://mrralph.co.nz/policies/refund-policy, https://mrralph.co.nz/policies/shipping-policy, https://mrralph.co.nz/customer_authentication/redirect, https://mrralph.co.nz/collections/low-stud-solutions and https://mrralph.co.nz/collections/new-product have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://mrralph.co.nz/customer_authentication/redirect, https://mrralph.co.nz/collections/end-of-line, https://mrralph.co.nz/pages/lookbook and https://mrralph.co.nz/pages/ask-ralph have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://mrralph.co.nz/pages/lookbook, https://mrralph.co.nz/blogs/news, https://mrralph.co.nz/pages/ask-ralph and https://mrralph.co.nz/pages/contact took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211043117&Ver=2&mid=c3a53f70-2cd8-4be3-bdaf-e8ae5a3d03e4&bo=1&sid=1431dd70dc6b11f1801317ced41c422e&vid=1431e980dc6b11f193de33bd52b3339f&vids=1&msclkid=N&pi=918639831&l.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'find')”.
2 checks passed
Tap targets are thumb-sized
14 of 16 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.
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 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 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 425 words of copy
The homepage carries about 425 words of visible text.
6 checks passed
25 calls to action
The homepage has 25 calls to action, for example “Shop”, “Shop By Product Type” and “Shop by Style”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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, 2 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.
43 other companies contacted
Loading the homepage contacts 43 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 mrralph.co.nz, 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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Instafeed · Klaviyo Email Marketing Sms · Inbox · Fabrikator Inventory Assistant · Sticky Cart By Qikify · redirectify.app
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 Analytics | Google Tag Manager | 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 42 issues on mrralph.co.nz, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.