Website review, no card needed

jungleworks.com logo

jungleworks.com website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 88 checks

This review found 40 issues worth fixing on jungleworks.com, 17 of them high impact, across 88 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
4.5 s4.1 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.2 s
May 23, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.1 s
Jun 27, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.5 s
Oct 10, 20264.5 s
Oct 17, 20264.4 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
236 ms159 msMay 9Oct 24223 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026172 ms
May 16, 2026174 ms
May 23, 2026168 ms
Jun 13, 2026172 ms
Jun 20, 2026177 ms
Jun 27, 2026177 ms
Jul 18, 2026196 ms
Jul 25, 2026199 ms
Aug 1, 2026202 ms
Aug 22, 2026207 ms
Aug 29, 2026197 ms
Sep 5, 2026194 ms
Sep 12, 2026204 ms
Sep 19, 2026207 ms
Sep 26, 2026214 ms
Oct 3, 2026222 ms
Oct 10, 2026227 ms
Oct 17, 2026226 ms
Oct 24, 2026223 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 jungleworks.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jungleworks.com at 0.5 s0.5 s
  2. jungleworks.com at 1.0 s1.0 s
  3. jungleworks.com at 1.5 s1.5 s
  4. jungleworks.com at 2.0 s2.0 s
  5. jungleworks.com at 2.5 s2.5 s
  6. jungleworks.com at 3.0 s3.0 s
  7. jungleworks.com at 3.5 s3.5 s
  8. jungleworks.com at 4.0 s4.0 s

Speed

10 to fix44
  • Reduce unused JavaScript

    1.6 s · 770 KiB

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

  • Use efficient cache lifetimes

    2.0 s · 403 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    460 ms · 75 KiB

    About 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Google Tag Manager adds 431 ms

    431 ms

    Google Tag Manager costs a phone 431 ms of main-thread work and 387 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 332 ms

    332 ms

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

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • ec2dashboard.com adds 48 ms

    48 ms

    ec2dashboard.com costs a phone 48 ms of main-thread work and 611 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.

  • 19 long tasks on the main thread

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

  • Improve image delivery

    30 KiB

    1 image could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    10 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    12 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 79 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

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

12 to fix33
  • 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.

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 0.26

    0.26

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 10.4 s

    10.4 s

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

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Total Blocking Time: 875 ms

    875 ms

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 7 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

2 checks passed
  • Real-user INP: 194 ms

    194 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 95 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 95 requests on a phone: scripts 1.5 MB (29), images 1,015 KiB (37) and stylesheets 98 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (827 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

2 checks passed
  • 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

5 to fixGoogle 9292
  • 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.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 99 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

Google 100100
  • 52 internal links, 32 external

    The homepage links to 52 pages on jungleworks.com and 32 external pages.

8 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “We are the market leaders in delivering mobility solutions to entrepreneurs and enterprises.”.

  • One H1 headline

    Your main headline reads: “We're powering Local Commerce.”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Jungleworks | Powering Local Commerce”.

  • Canonical URL set

    The canonical URL is https://jungleworks.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://jungleworks.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://jungleworks.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (753 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix58
  • 1 page without a title

    https://jungleworks.com/panther/fitness has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://jungleworks.com/hippo/conversational-support declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://jungleworks.com/hippo/conversational-support all use the title “Jungleworks | Powering Local Commerce”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://jungleworks.com/panther/fitness has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://jungleworks.com/panther/fitness 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 39 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://jungleworks.com/wp-content/uploads/2024/08/pci-dss.svg.

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

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

    The homepage carries about 419 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a Demo”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Request a Demo”, “Looking for something else? Contact Us.” and “Get In Touch”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 34 customer or partner logos and “5M+ Users”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Umami.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 jungleworks.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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 jungleworks.com, including 22 speed 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