Website review, no card needed

junglejunglejungle.com logo

junglejunglejungle.com website review

Visit site (opens in a new tab)Reviewed 17 November 202637 issues · 86 checks

This review found 37 issues worth fixing on junglejunglejungle.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
1.5 s967 msMay 30Nov 141.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Nov 14, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
196 ms159 msMay 30Nov 14177 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026163 ms
Jun 6, 2026168 ms
Jun 13, 2026169 ms
Jun 20, 2026169 ms
Jun 27, 2026171 ms
Jul 4, 2026176 ms
Jul 11, 2026178 ms
Jul 18, 2026178 ms
Jul 25, 2026175 ms
Aug 1, 2026173 ms
Aug 8, 2026179 ms
Aug 15, 2026185 ms
Aug 22, 2026188 ms
Aug 29, 2026191 ms
Sep 5, 2026191 ms
Sep 12, 2026188 ms
Sep 19, 2026190 ms
Sep 26, 2026189 ms
Oct 3, 2026188 ms
Oct 10, 2026190 ms
Oct 17, 2026191 ms
Oct 24, 2026192 ms
Oct 31, 2026187 ms
Nov 7, 2026182 ms
Nov 14, 2026177 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 junglejunglejungle.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. junglejunglejungle.com at 0.8 s0.8 s
  2. junglejunglejungle.com at 1.6 s1.6 s
  3. junglejunglejungle.com at 2.4 s2.4 s
  4. junglejunglejungle.com at 3.2 s3.2 s
  5. junglejunglejungle.com at 3.9 s3.9 s
  6. junglejunglejungle.com at 4.7 s4.7 s
  7. junglejunglejungle.com at 5.5 s5.5 s
  8. junglejunglejungle.com at 6.3 s6.3 s

Speed

10 to fix27
  • Reduce unused JavaScript

    2.9 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Google Tag Manager adds 2.6 s

    2.6 s

    Google Tag Manager costs a phone 2.6 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 8.4 s

    A phone's processor spends 8.4 s on main-thread work while loading, 4.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 (Google Tag Manager, YouTube and Facebook and others), adding 3.9 MB and 4.4 s of main-thread time.

  • YouTube adds 916 ms

    916 ms

    YouTube costs a phone 916 ms of main-thread work and 992 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.

  • Use efficient cache lifetimes

    150 ms · 419 KiB

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

  • Render-blocking requests

    450 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 432 ms. During a long task the page ignores taps.

  • Facebook adds 347 ms

    347 ms

    Facebook costs a phone 347 ms of main-thread work and 261 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

    150 ms · 112 KiB

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

  • Improve image delivery

    50 ms · 13 KiB

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

  • Legacy JavaScript

    46 KiB

    Polyfills for old browsers add 46 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.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 12.6 s

    12.6 s

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

  • Time to Interactive: 34.8 s

    34.8 s

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

  • Total Blocking Time: 3.3 s

    3.3 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 199 ms

    199 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 480 ms

    480 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.6 MB in 405 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 405 requests on a phone: scripts 4.1 MB (116), other files 974 KiB (210) and images 180 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.59 g

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

3 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.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 8 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 8 images without alt text

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “UPCOMING TOUR DATES”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 42 internal links, 28 external

    The homepage links to 42 pages on junglejunglejungle.com and 28 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Jungle Official Website. Listen to Jungle and subscribe to the mailing list to be the first to hear new music. Shop our…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Jungle Official Website and Store – Jungle UK Store”.

  • Canonical URL set

    The canonical URL is https://www.junglejunglejungle.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.junglejunglejungle.com/sitemap.xml.

AI search readiness

100
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 (280 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.junglejunglejungle.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.junglejunglejungle.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.junglejunglejungle.com/collections/sunshine, https://www.junglejunglejungle.com/collections/music, https://www.junglejunglejungle.com/collections/clothing, https://www.junglejunglejungle.com/collections/accessories, https://www.junglejunglejungle.com/customer_authentication/redirect and https://www.junglejunglejungle.com/collections/frontpage have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.junglejunglejungle.com/collections/sunshine and https://www.junglejunglejungle.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.junglejunglejungle.com/pages/tour-dates has 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 16 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

3 to fixGoogle 6976
  • 1 broken image

    1 image failed to load on a phone, for example https://track.mailerlite.com/webforms/o/3564256/v1p7f3?v1679052082.

  • 6 third-party cookies

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 436 words of copy

    The homepage carries about 436 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More” and “CLICK HERE TO JOIN THE JUNGLE FAN CLUB”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “CLICK HERE TO JOIN THE JUNGLE FAN CLUB”, “Subscribe” and “CHRISTMAS ORDER DATES”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager 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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 cookies, 2 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.

  • 51 other companies contacted

    Loading the homepage contacts 51 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 junglejunglejungle.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Eu Cookie Bar · mailerlite.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 Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on junglejunglejungle.com, including 16 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

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