Website review, no card needed
nutjar.ca website review
Visit site (opens in a new tab)Reviewed 12 November 202632 issues · 76 checks
This review found 32 issues worth fixing on nutjar.ca, 8 of them high impact, across 76 checks. The most urgent: main-thread work: 4.3 s. 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
80B- #42,116 of 106,224 reviewed websitesbeats 55%
- #27,827 of 59,843 online storesbeats 47%
- #26,769 of 54,557 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 934 ms |
| May 30, 2026 | 853 ms |
| Jun 6, 2026 | 827 ms |
| Jun 13, 2026 | 840 ms |
| Jun 20, 2026 | 864 ms |
| Jun 27, 2026 | 947 ms |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 999 ms |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 990 ms |
| Aug 1, 2026 | 972 ms |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.2 s |
| Oct 3, 2026 | 927 ms |
| Oct 10, 2026 | 962 ms |
| Oct 17, 2026 | 949 ms |
| Oct 24, 2026 | 954 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 136 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 121 ms |
| Aug 22, 2026 | 144 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 145 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
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.7 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, Hotjar and Google Tag Manager and others), adding 1.3 MB and 951 ms of main-thread time.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
900 KiB19 images could be 900 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
881 KiBAbout 881 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Shopify adds 279 ms
279 msShopify costs a phone 279 ms of main-thread work and 645 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.
Hotjar adds 266 ms
266 msHotjar costs a phone 266 ms of main-thread work and 65 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.
2,372 HTML elements
The page has 2,372 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 48 KiBAbout 48 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
60 KiB12 files are served with short cache lifetimes, so returning visitors download them again (60 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
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: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.6 s
18.6 sThe page becomes fully interactive after 18.6 s. Good is under 3.8 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 218 ms
218 msScripts block taps and scrolling for 218 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 136 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 327 requests
3.8 MBYour homepage downloads 3.8 MB in 327 requests on a phone: scripts 1.3 MB (148), images 1.3 MB (31) and other files 810 KiB (114). Under 2 MB keeps phones on slow connections fast.
18 images below the first screen load straight away
18 images further down the page (779 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 130.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (168 characters)
Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 27 external
The homepage links to 100 pages on nutjar.ca and 27 external pages.
6 checks passed
One H1 headline
Your main headline reads: “NutJar”.
Title: 36 characters
Your title is a healthy 36 characters: “Nuts | Canadian Nut Butters | NutJar”.
Canonical URL set
The canonical URL is https://www.nutjar.ca/.
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.nutjar.ca/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 (1,056 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.nutjar.ca/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.nutjar.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.nutjar.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://www.nutjar.ca/customer_authentication/redirect, https://www.nutjar.ca/collections/nut-butters-spreads, https://www.nutjar.ca/collections/gifting, https://www.nutjar.ca/collections/protein-packs, https://www.nutjar.ca/collections/spreads and https://www.nutjar.ca/collections/pure-nut-butters and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.nutjar.ca/customer_authentication/redirect has 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 44 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 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 13 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.
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 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 661 words of copy
The homepage carries about 661 words of visible text.
4 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Order note”, “Apply” and “Shop”.
19 short forms
19 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
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
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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
39 other companies contacted
Loading the homepage contacts 39 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 nutjar.ca, 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
Elevar Conversion Tracking · Judge Me Reviews · Klaviyo Email Marketing Sms · Instant Ai Page Builder · Inbox · Simprosys Google Shopping Feed · Forms · Applovin Shop Integration · snapchat.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
- Hosting
- Shopify
Company
- Headquarters
- Delta
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on nutjar.ca, including 13 speed issues, 3 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.