Website review, no card needed

stratiapro.com logo

stratiapro.com website review

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

This review found 35 issues worth fixing on stratiapro.com, 13 of them high impact, across 73 checks. The most urgent: avoid multiple page redirects. 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 stratiapro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix47
  • Avoid multiple page redirects

    10.8 s

    The page goes through 3 redirects before it starts loading, costing about 10.8 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    5.4 s · 862 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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, Google Analytics and squarecdn.com and others), adding 1.3 MB and 1.0 s of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Google Tag Manager adds 777 ms

    777 ms

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

    450 ms · 264 KiB

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

  • Main-thread work: 3.8 s

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

  • 14 long tasks on the main thread

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

  • Document request latency

    200 ms

    The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

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

  • Legacy JavaScript

    34 KiB

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

  • Improve image delivery

    27 KiB

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

  • Reduce unused CSS

    18 KiB

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix45
  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Become a Stratia Pro and optimize your practice. Licensed s…”.

  • Time to Interactive: 23.4 s

    23.4 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 806 ms

    806 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 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

2 to fix64
  • Page weight: 4.3 MB in 241 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 241 requests on a phone: scripts 2.9 MB (97), other files 819 KiB (111) and images 284 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    StratiaNew47282_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (154 KiB) is 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 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.0 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

3 to fixGoogle 8893
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

4 to fixGoogle 8368
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 44 internal links, 10 external

    The homepage links to 44 pages on stratiapro.com and 10 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Science-First Skincare for Professionals”.

  • Canonical URL set

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

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

AI search readiness

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

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.

  • llms.txt published

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

Other pages

5 to fix32
  • 1 linked page is broken

    Your homepage links to https://stratiapro.com/pages/rewards, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a title

    https://stratiapro.com/collections/best-seller, https://stratiapro.com/pages/education, https://stratiapro.com/blogs/ingredients, https://stratiapro.com/customer_authentication/redirect, https://stratiapro.com/collections/all and https://stratiapro.com/collections/all-products and 8 others have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 14 pages without a meta description

    https://stratiapro.com/collections/best-seller, https://stratiapro.com/pages/education, https://stratiapro.com/blogs/ingredients, https://stratiapro.com/customer_authentication/redirect, https://stratiapro.com/collections/all and https://stratiapro.com/collections/all-products and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://stratiapro.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://stratiapro.com/collections/best-seller, https://stratiapro.com/blogs/ingredients, https://stratiapro.com/collections/all and https://stratiapro.com/collections/all-products have 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 23 found) and read each the way a search engine does.

1 checks passed
  • Canonical URLs point to themselves

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

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix72
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 21 words

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “apply here”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “SHOP NOW” and “Shop All Products”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 3 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.

  • 29 other companies contacted

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

Apps your storefront loads

Videowise Video Commerce · juniphq.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 35 issues on stratiapro.com, including 13 speed issues, 4 SEO issues and 5 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