Website review, no card needed

juced.co logo

juced.co website review

Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 87 checks

This review found 41 issues worth fixing on juced.co, 13 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.6 sMay 30Nov 143.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.0 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.8 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.5 s
Oct 24, 20262.7 s
Oct 31, 20262.9 s
Nov 7, 20263.0 s
Nov 14, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
193 ms112 msMay 30Nov 14133 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026163 ms
Jun 6, 2026170 ms
Jun 13, 2026175 ms
Jun 20, 2026180 ms
Jun 27, 2026180 ms
Jul 4, 2026137 ms
Jul 11, 2026173 ms
Jul 18, 2026184 ms
Jul 25, 2026171 ms
Aug 1, 2026155 ms
Aug 8, 2026139 ms
Aug 15, 2026131 ms
Aug 22, 2026128 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026127 ms
Sep 26, 2026121 ms
Oct 3, 2026121 ms
Oct 10, 2026121 ms
Oct 17, 2026126 ms
Oct 24, 2026134 ms
Oct 31, 2026130 ms
Nov 7, 2026135 ms
Nov 14, 2026133 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

Full-page screenshot of juced.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. juced.co at 1.1 s1.1 s
  2. juced.co at 2.3 s2.3 s
  3. juced.co at 3.4 s3.4 s
  4. juced.co at 4.5 s4.5 s
  5. juced.co at 5.7 s5.7 s
  6. juced.co at 6.8 s6.8 s
  7. juced.co at 7.9 s7.9 s
  8. juced.co at 9.1 s9.1 s

Speed

13 to fix44
  • Render-blocking requests

    1.0 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.7 s

    A phone's processor spends 9.7 s on main-thread work while loading, 5.3 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 (alia-prod.com, Google Tag Manager and Vimeo and others), adding 3.9 MB and 2.3 s of main-thread time.

  • Reduce unused JavaScript

    1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    696 KiB

    35 files are served with short cache lifetimes, so returning visitors download them again (696 KiB).

  • Improve image delivery

    300 ms · 356 KiB

    6 images could be 356 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Vimeo adds 387 ms

    387 ms

    Vimeo costs a phone 387 ms of main-thread work and 1.9 MB 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.

  • alia-prod.com adds 463 ms

    463 ms

    alia-prod.com costs a phone 463 ms of main-thread work and 564 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.

  • Google Tag Manager adds 443 ms

    443 ms

    Google Tag Manager costs a phone 443 ms of main-thread work and 553 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.

  • Facebook adds 277 ms

    277 ms

    Facebook costs a phone 277 ms of main-thread work and 220 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.

  • heatmap.com adds 285 ms

    285 ms

    heatmap.com costs a phone 285 ms of main-thread work and 93 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 267 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    52 KiB

    Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    22 KiB

    About 22 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 32 ms

    32 ms

    Your server sent the HTML in 32 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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: 37.4 s

    37.4 s

    The page becomes fully interactive after 37.4 s. Good is under 3.8 s.

  • Speed Index: 14.6 s

    14.6 s

    Visually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 5.5 s

    5.5 s

    Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest content (LCP) got 62% slower for real visitors

    +62%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

6 checks passed
  • Real-user INP: 127 ms

    127 ms

    Real visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 546 ms

    546 ms

    Real visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 20% faster for real visitors

    -20%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 163 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 6.4 MB in 400 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 400 requests on a phone: scripts 3.9 MB (113), images 1.0 MB (36) and other files 1,010 KiB (226). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.4 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.

  • 1 image below the first screen load straight away

    1 image further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9194
  • Elements must only use permitted ARIA attributes (5 elements)

    Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (16 elements)

    All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 57 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 57 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • 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 (230 characters)

    Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 35 internal links, 21 external

    The homepage links to 35 pages on juced.co and 21 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Pre-Anything Energy Gummies”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Jüced | Peachy, Portable Energy Gummies”.

  • Canonical URL set

    The canonical URL is https://juced.co/.

  • 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://juced.co/sitemap.xml.

AI search readiness

1 to fix88
  • 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,762 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://juced.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://juced.co/products/juced all use the title “Jüced | Peachy, Portable Energy Gummies”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://juced.co/products/juced has no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    3 pages of 13 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 3 broken images

    3 images failed to load on a phone, for example https://files.alia-prod.com/11652/d4fc97f78974f4d6.webp.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    15 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • About 1,813 words of copy

    The homepage carries about 1,813 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try Jüced Now” and “Shop Now”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Try Jüced Now”, “Contact” and “Start Now”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 23 testimonial or review blocks, a star rating and “1M+ members”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 3 email links.

  • 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

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.

  • 35 cookies set on arrival

    35

    Opening the homepage sets 35 cookies, 4 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.

  • 55 other companies contacted

    Loading the homepage contacts 55 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 juced.co, 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

Intelligems A B Testing · Visually A B Testing Cro · Elevar Conversion Tracking · Keepcart Coupon Protect · Postscript Sms Marketing · Klaviyo Email Marketing Sms · Aftersell · Test Sms · Upcart · socialsnowball.io · nofraud.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

Hiring

Hiring
26 open roles
Teams
International (6), Ecommerce (3), Operations - Facilities (3), People (3)
Job board
greenhouse

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on juced.co, including 22 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25