Website review, no card needed
goodgoodbrand.com website review
Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 89 checks
This review found 40 issues worth fixing on goodgoodbrand.com, 10 of them high impact, across 89 checks. The most urgent: main-thread work: 9.4 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
78C- #61,535 of 122,489 reviewed websitesbeats 44%
- #40,276 of 69,172 online storesbeats 36%
- #38,485 of 63,011 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 109 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 149 ms |
| Oct 31, 2026 | 149 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
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.5 s
7.6 s
8.7 s
Speed
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 5.4 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 (Google Tag Manager, Yotpo and Klaviyo and others), adding 2.4 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 837 KiB6 images could be 837 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
546 KiB35 files are served with short cache lifetimes, so returning visitors download them again (546 KiB).
Google Tag Manager adds 488 ms
488 msGoogle Tag Manager costs a phone 488 ms of main-thread work and 516 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.
Yotpo adds 444 ms
444 msYotpo costs a phone 444 ms of main-thread work and 417 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.
Klaviyo adds 378 ms
378 msKlaviyo costs a phone 378 ms of main-thread work and 613 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 414 ms. During a long task the page ignores taps.
Render-blocking requests
400 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
1,953 HTML elements
The page has 1,953 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
smile.io adds 115 ms
115 mssmile.io costs a phone 115 ms of main-thread work and 364 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.
Shopify adds 70 ms
70 msShopify costs a phone 70 ms of main-thread work and 410 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
83 KiBPolyfills for old browsers add 83 KiB JavaScript that modern phones do not need.
Reduce unused CSS
73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
22 KiB22 KiB could be saved by minifying JavaScript.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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: 20 ms
20 msYour server sent the HTML in 20 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.
Time to Interactive: 31.2 s
31.2 sThe page becomes fully interactive after 31.2 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 905 ms
905 msScripts block taps and scrolling for 905 ms in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.13
0.13For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 109 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
7 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 INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 536 ms
536 msReal visitors wait 536 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 406 requests
5.5 MBYour homepage downloads 5.5 MB in 406 requests on a phone: scripts 2.7 MB (143), images 1.2 MB (66) and other files 893 KiB (161). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
53 KiB1 image is downloaded at several times the size a phone draws it, for example Buy_More_Save_More_70.png at 1,693 px wide, shown at 390 px. Resized copies would save about 53 KiB.
About 1.6 g of CO₂ per visit
1.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.57 g of CO₂e: 188.1 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
50 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: 50 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
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
40 internal links, 22 external
The homepage links to 40 pages on goodgoodbrand.com and 22 external pages.
7 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “No added sugar jams, peanut butter & chocolate spreads. Keto-friendly, vegan & non-GMO. Born in Iceland. Shop GOOD GOOD…”.
One H1 headline
Your main headline reads: “No Added Sugar Jams, Peanut Butter & Chocolate Spreads”.
Title: 57 characters
Your title is a healthy 57 characters: “No Added Sugar Jams, Spreads & Peanut Butter | GOOD GOOD®”.
Canonical URL set
The canonical URL is https://goodgoodbrand.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://goodgoodbrand.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.
Some text only appears after JavaScript runs
34%The HTML your server sends has 254 of the 753 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://goodgoodbrand.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://goodgoodbrand.com/products/fruit-spread-bundle, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
https://goodgoodbrand.com/products/jam-bundle-1 and https://goodgoodbrand.com/pages/bundle all use the title “Custom Bundle | US GOOD GOOD®”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://goodgoodbrand.com/collections/spring-zest, https://goodgoodbrand.com/collections/strawberry-jam, https://goodgoodbrand.com/collections/all-choco-hazel, https://goodgoodbrand.com/collections/creamy-peanut-butter and https://goodgoodbrand.com/collections/crunchy-peanut-butter have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://goodgoodbrand.com/products/jam-bundle-1 and https://goodgoodbrand.com/pages/bundle use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://goodgoodbrand.com/pages/bundle, whose canonical is https://goodgoodbrand.com/products/jam-bundle-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://goodgoodbrand.com/collections/sugar-free-jelly-and-jams, https://goodgoodbrand.com/collections/all, https://goodgoodbrand.com/products/jam-bundle-1 and https://goodgoodbrand.com/pages/bundle have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://goodgoodbrand.com/collections/sugar-free-jelly-and-jams, https://goodgoodbrand.com/collections/all, https://goodgoodbrand.com/products/jam-bundle-1 and https://goodgoodbrand.com/pages/bundle have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
2 checks passed
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
18 small tap targets
18 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'closest')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 753 words of copy
The homepage carries about 753 words of visible text.
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop All Jams”, “Shop All Choco Spreads” and “Shop All Peanut Butters”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
37 cookies set on arrival
37Opening the homepage sets 37 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.
61 other companies contacted
Loading the homepage contacts 61 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 goodgoodbrand.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Attentive · Triplewhale · Forms · adroll.com · gorgias.chat · dollardonationclub.com · cloudfront.net · attn.tv · 9gtb.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
- jQuery
- E-commerce
- Shopify
- 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 40 issues on goodgoodbrand.com, including 22 speed issues, 1 SEO issue 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.