Website review, no card needed
professornutz.com website review
Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 73 checks
This review found 30 issues worth fixing on professornutz.com, 9 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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
75C- #75,964 of 114,810 reviewed websitesbeats 29%
- #49,226 of 66,305 online storesbeats 22%
- #46,636 of 60,658 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 8, 2026 | 70 ms |
| Aug 15, 2026 | 72 ms |
| Aug 22, 2026 | 72 ms |
| Aug 29, 2026 | 72 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.7 s
1.4 s
2.1 s
2.8 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Reduce unused JavaScript
1.3 s · 141 KiBAbout 141 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Improve image delivery
500 ms · 906 KiB13 images could be 906 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 903 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 207 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 20 KiB7 files are served with short cache lifetimes, so returning visitors download them again (20 KiB).
7 third-party services on the page
7 third-party services load with your homepage (Shopify, Stamped.io and cloudfront.net and others), adding 329 KiB and 129 ms of main-thread time.
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Professor Nutz presenting a giant spoonful of peanut butter”.
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: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
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.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 70 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 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
Total Blocking Time: 192 ms
192 msScripts block the page for only 192 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
7 images over 500 KB
7 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
2.6 MB9 images are downloaded at several times the size a phone draws them, for example pn-original-jar.webp at 567 px wide, shown at 139 px. Resized copies would save about 2.6 MB.
10 images in older formats
10 images (5.3 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.
Page weight: 2.5 MB in 162 requests
2.5 MBYour homepage downloads 2.5 MB in 162 requests on a phone: images 1.1 MB (14), other files 648 KiB (73) and scripts 365 KiB (39). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
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 35 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Professor Nutz”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 short (14 characters)
Your meta description is only 14 characters: “Professor Nutz”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“Professor Nutz” and “Peanut butter, corrected.”). One clear main headline is easier for people and search engines.
61 internal links, 4 external
The homepage links to 61 pages on professornutz.com and 4 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.professornutz.com/.
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.professornutz.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 (1,594 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.professornutz.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.professornutz.com/pages/what-inside, which answers with an error. Visitors hit a dead end and search engines drop it.
10 pages share a meta description
https://www.professornutz.com/collections/all, https://www.professornutz.com/pages/the-study, https://www.professornutz.com/pages/our-story, https://www.professornutz.com/pages/contact and https://www.professornutz.com/pages/how-it-works use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.professornutz.com/.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
32 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 10-field form
Your longest form asks for 10 fields (8 required). Every extra field lowers completion.
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 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 1,105 words of copy
The homepage carries about 1,105 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Contact” and “Shop the flavors”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
17 other companies contacted
Loading the homepage contacts 17 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 professornutz.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Uppromote Affiliate · Affliate By Secomapp · stamped.io · nice-team.net · carthike.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
Company
- Headquarters
- Knoxville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on professornutz.com, including 9 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.