Website review, no card needed
yummygums.com website review
Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 88 checks
This review found 38 issues worth fixing on yummygums.com, 17 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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- #73,020 of 119,682 reviewed websitesbeats 34%
- #47,042 of 67,864 online storesbeats 26%
- #44,621 of 61,860 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 158 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 160 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 169 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 178 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 179 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.9 s
1.8 s
2.7 s
3.5 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Use efficient cache lifetimes
1.1 s · 648 KiB37 files are served with short cache lifetimes, so returning visitors download them again (648 KiB).
10,408 HTML elements
The page has 10,408 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
1.9 MB17 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Reviews.io and Klaviyo and others), adding 2.0 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
590 ms · 858 KiBAbout 858 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 590 ms faster on a phone.
Render-blocking requests
650 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Google Tag Manager adds 330 ms
330 msGoogle Tag Manager costs a phone 330 ms of main-thread work and 283 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.
Reviews.io adds 222 ms
222 msReviews.io costs a phone 222 ms of main-thread work and 393 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 195 ms
195 msKlaviyo costs a phone 195 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.
Reduce unused CSS
140 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
Minify CSS
9 KiB9 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: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 12.5 s
12.5 sYour largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Supplementen die je wél volhoudt. Hoogwaardige supplementen…”.
Time to Interactive: 31.3 s
31.3 sThe page becomes fully interactive after 31.3 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 703 ms
703 msScripts block taps and scrolling for 703 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 218 ms
218 msReal visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 158 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
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: 346 ms
346 msReal visitors wait 346 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 9.0 MB in 444 requests
9.0 MBYour homepage downloads 9.0 MB in 444 requests on a phone: images 2.7 MB (85), scripts 2.4 MB (130) and media 2.2 MB (1). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
17f1ea81c2e1ac10012daa9aae0adbaf6fdcf3c7.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.4 MB2 images are downloaded at several times the size a phone draws them, for example 17f1ea81c2e1ac10012daa9aae0adbaf6fdcf3c7.png at 3,500 px wide, shown at 119 px. Resized copies would save about 1.4 MB.
4 images below the first screen load straight away
4 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (52 KiB) is 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 2.5 g of CO₂ per visit
2.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.54 g of CO₂e: 304.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (83 elements)
All page content should be contained by landmarks: 83 elements on the page fail 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 → h5), 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. (4 elements).
1 checks passed
49 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: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “Yummygums | Hoogwaardige supplementen | vitamine gummies en meer – YummygumsNL”.
One H1 headline
Your <h1> is empty.
317 internal links, 5 external
The homepage links to 317 pages on yummygums.com and 5 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Met Yummygums wordt gezond leven iets om naar uit te kijken. Probeer onze vitamine gummies, shots of capsules. ✓Suikerv…”.
Canonical URL set
The canonical URL is https://www.yummygums.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.yummygums.com/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,758 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.yummygums.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.yummygums.com/pages/bundle-builder has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.yummygums.com/pages/bundle-builder 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 105 found) and read each the way a search engine does.
5 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.
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
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187211921&Ver=2&mid=3431db90-e242-4a99-ad5b-e75d7cf48c87&bo=1&sid=305bbc00db7211f1b9e107c73a9c01b7&vid=305bc300db7211f1ae3b8b77d4572b98&vids=1&msclkid=N&pi=918639831&l.
64 small tap targets
64 of 212 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.yummygums.com' has been blocke…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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,984 words of copy
The homepage carries about 1,984 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Yummygums”.
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Shop Yummygums” and “Shop nu”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
32 cookies set on arrival
32Opening the homepage sets 32 cookies, 2 of them by other companies (measured from a US location before any click).
52 other companies contacted
Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 yummygums.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gsc Instagram Feed · Triplewhale · Instant Ai Page Builder · Wisepops Popup Builder Cro · Microsoft Clarity · Announcement Bar Maker By Apphero · Reviews Co Uk Product And Merchant Review Collection · gorgias.chat · klaviyo.com · revenuehunt.com · 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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Amsterdam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on yummygums.com, including 19 speed issues, 2 SEO issues 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.