Website review, no card needed
jadekiwinz.com website review
Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 82 checks
This review found 39 issues worth fixing on jadekiwinz.com, 13 of them high impact, across 82 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
73C- #92,318 of 125,123 reviewed websitesbeats 23%
- #57,322 of 70,108 online storesbeats 15%
- #53,592 of 63,712 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
1.6 s · 1.3 MB31 images could be 1.3 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.
Reduce unused JavaScript
1.5 s · 293 KiBAbout 293 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 151 KiB6 files are served with short cache lifetimes, so returning visitors download them again (151 KiB).
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Reduce unused CSS
150 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (squarecdn.com, Shopify and Google CDN and others), adding 575 KiB and 131 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 328 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.0 s
16.0 sYour largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.105
0.105The layout shifts by 0.105 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.4 MB in 183 requests
4.4 MBYour homepage downloads 4.4 MB in 183 requests on a phone: images 2.8 MB (52), other files 729 KiB (77) and scripts 666 KiB (40). Under 2 MB keeps phones on slow connections fast.
24 images below the first screen load straight away
24 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
9 images far larger than shown
289 KiB9 images are downloaded at several times the size a phone draws them, for example 51A060FD-A069-450A-AB63-4F133994246C_grande.jpg at 600 px wide, shown at 150 px. Resized copies would save about 289 KiB.
3 images in older formats
3 images (276 KiB) 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 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
57 text elements with low contrast
57 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
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.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 11 failed. 1 more 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.
Canonical points to another host
Your canonical URL points to jadekiwi.nz, not jadekiwinz.com, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (292 characters)
Your meta description is 292 characters; Google truncates after about 160, so the end of your pitch is cut.
126 internal links, 6 external
The homepage links to 126 pages on jadekiwinz.com and 6 external pages.
4 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Jade Kiwi Gift, Souvenir and New Zealand Gift Shop”.
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://jadekiwinz.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 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 (338 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://jadekiwinz.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://jadekiwinz.com/collections/novelty, https://jadekiwinz.com/collections/books-stationery, https://jadekiwinz.com/collections/bath-body, https://jadekiwinz.com/collections/accessories, https://jadekiwinz.com/collections/bags and https://jadekiwinz.com/collections/beauty-accessories and 3 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 59 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 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 404 ()”.
2 checks passed
Tap targets are thumb-sized
49 of 55 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 333 words of copy
The homepage carries about 333 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Shop” and “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
20 other companies contacted
Loading the homepage contacts 20 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 jadekiwinz.com, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Forms
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on jadekiwinz.com, including 12 speed issues, 4 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.