Website review, no card needed

javashroom.com logo

javashroom.com website review

Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 73 checks

This review found 35 issues worth fixing on javashroom.com, 10 of them high impact, across 73 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

Full-page screenshot of javashroom.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. javashroom.com at 0.4 s0.4 s
  2. javashroom.com at 0.8 s0.8 s
  3. javashroom.com at 1.1 s1.1 s
  4. javashroom.com at 1.5 s1.5 s
  5. javashroom.com at 1.9 s1.9 s
  6. javashroom.com at 2.3 s2.3 s
  7. javashroom.com at 2.6 s2.6 s
  8. javashroom.com at 3.0 s3.0 s

Speed

12 to fix49
  • Reduce unused JavaScript

    4.8 s · 1.1 MB

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. 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, rebuyengine.com and ghostretail.com and others), adding 2.0 MB and 946 ms of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    400 ms · 176 KiB

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

  • Use efficient cache lifetimes

    350 ms · 58 KiB

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

  • Main-thread work: 3.9 s

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

  • Google Tag Manager adds 342 ms

    342 ms

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

    300 ms · 70 KiB

    Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • rebuyengine.com adds 239 ms

    239 ms

    rebuyengine.com costs a phone 239 ms of main-thread work and 627 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.

  • 2,396 HTML elements

    The page has 2,396 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • ghostretail.com adds 111 ms

    111 ms

    ghostretail.com costs a phone 111 ms of main-thread work and 634 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.

  • 13 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    46 KiB

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

6 to fix50
  • Largest Contentful Paint: 22.3 s

    22.3 s

    Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “REDEFINING WELLNESS FROM THE GROUND UP Elevate your morning…”.

  • Time to Interactive: 27.0 s

    27.0 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 577 ms

    577 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix28
  • Page weight: 5.1 MB in 314 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 314 requests on a phone: scripts 1.9 MB (87), images 1.5 MB (32) and other files 1.1 MB (148). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Mushroom_Series_copy_1.webp weighs 995 KiB. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (1.1 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.

  • 4 images below the first screen load straight away

    4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    344 KiB

    2 images are downloaded at several times the size a phone draws them, for example Mushroom_Series_copy_1.webp at 1,275 px wide, shown at 350 px. Resized copies would save about 344 KiB.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

Accessibility

2 to fixGoogle 9196
  • 3 text elements with low contrast

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

  • 21 images without alt text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Canonical points to another host

    Your canonical URL points to altrroot.com, not javashroom.com, so Google may credit that host instead.

  • Meta description is long (181 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 26 internal links, 12 external

    The homepage links to 26 pages on javashroom.com and 12 external pages.

5 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “ALTR ROOT - REDEFINING WELLNESS FROM THE GROUND UP”.

  • 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://javashroom.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 (1,720 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://javashroom.com/products/java-shroom is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://javashroom.com/collections/all, https://javashroom.com/policies/shipping-policy, https://javashroom.com/pages/our-story, https://javashroom.com/blogs/all, https://javashroom.com/blogs/all/tagged/recipes and https://javashroom.com/pages/shipping-information and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://javashroom.com/pages/our-story, https://javashroom.com/blogs/all, https://javashroom.com/blogs/all/tagged/recipes, https://javashroom.com/pages/track-my-order, https://javashroom.com/pages/shipping-information and https://javashroom.com/pages/terms-conditions and 4 others have 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 and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 594 words of copy

    The homepage carries about 594 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “TRY NOW” and “Shop Now”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop Java Shroom”, “Shop Matcha Shroom” and “Shop Calming Cocoa”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 30 cookies set on arrival

    30

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

  • 35 other companies contacted

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

Apps your storefront loads

Blotout Edgetag · Eg Auto Add To Cart · Wingify · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · rebuyengine.com · rechargecdn.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on javashroom.com, including 18 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