Website review, no card needed

stemutone.org logo

stemutone.org website review

Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 76 checks

This review found 28 issues worth fixing on stemutone.org, 7 of them high impact, across 76 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

Full-page screenshot of stemutone.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stemutone.org at 0.4 s0.4 s
  2. stemutone.org at 0.9 s0.9 s
  3. stemutone.org at 1.3 s1.3 s
  4. stemutone.org at 1.7 s1.7 s
  5. stemutone.org at 2.2 s2.2 s
  6. stemutone.org at 2.6 s2.6 s
  7. stemutone.org at 3.0 s3.0 s
  8. stemutone.org at 3.5 s3.5 s

Speed

5 to fix63
  • Render-blocking requests

    1.6 s

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

  • Reduce unused JavaScript

    900 ms · 213 KiB

    About 213 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Font display

    850 ms

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

  • Reduce unused CSS

    300 ms · 40 KiB

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

  • Use efficient cache lifetimes

    150 ms · 129 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Bold Commerce and Shopify and others), adding 486 KiB and 221 ms of main-thread time.

  • Improve image delivery

    150 ms · 112 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 493 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 11.9 s

    11.9 s

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

  • Time to Interactive: 12.0 s

    12.0 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 9 images without width and height

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

2 checks passed
  • Total Blocking Time: 110 ms

    110 ms

    Scripts block the page for only 110 ms while loading. 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.4 MB in 197 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 197 requests on a phone: other files 747 KiB (87), scripts 651 KiB (53) and images 522 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    46 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-instagram.png at 1,795 px wide, shown at 390 px. Resized copies would save about 46 KiB.

  • 1 image below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.69 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 8994
  • 6 text elements with low contrast

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

  • 9 images without alt text

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 8584
  • Canonical points to another host

    Your canonical URL points to stemutone.myshopify.com, not stemutone.org, so Google may credit that host instead.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Stemutone Serum”, “Stemutone Body Serum” and “AMA LABORATORIES”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://stemutone.myshopify.com)”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 24 internal links, 2 external

    The homepage links to 24 pages on stemutone.org and 2 external pages.

5 checks passed
  • Meta description: 93 characters

    Your meta description is 93 characters: “Adonia StemuTone body firming works on sagging skin, stretch marks, dryness, and crepey skin.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Adonia Organics: StemuTone Body Firming Serum – Stemutone Serum”.

  • 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://stemutone.org/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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.

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

  • llms.txt published

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

Other pages

1 to fix75
  • 1 linked page is broken

    Your homepage links to https://stemutone.org/apps/iwish, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 10 internal pages checked

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

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

    10 of 14 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 font at 'https://www.stemutone.com/cdn/fonts/work_sans/worksans_n4.29e3afeb38a0ba35e784cf169a40e8beaf814daa.w…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix91
  • 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.

  • Only about 167 words

    The homepage has only about 167 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “ORDER NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Order now” and “Order Now”.

  • 5 short forms

    5 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and “over 42,000 customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • 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
  • 3 trackers load before any consent

    3

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 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.

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on stemutone.org, including 10 speed issues, 5 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