Website review, no card needed

oshotwomen.com logo

oshotwomen.com website review

Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 78 checks

This review found 42 issues worth fixing on oshotwomen.com, 16 of them high impact, across 78 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 oshotwomen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix53
  • Reduce unused JavaScript

    4.8 s · 1.0 MB

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

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.4 s · 333 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Bold Commerce, Yotpo and rechargecdn.com and others), adding 3.6 MB and 833 ms of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Minify JavaScript

    450 ms · 63 KiB

    63 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    350 ms · 57 KiB

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

  • Reduce unused CSS

    300 ms · 60 KiB

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

  • 8 long tasks on the main thread

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

  • Main-thread work: 3.2 s

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

  • Bold Commerce adds 255 ms

    255 ms

    Bold Commerce costs a phone 255 ms of main-thread work and 484 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.

  • Yotpo adds 198 ms

    198 ms

    Yotpo costs a phone 198 ms of main-thread work and 405 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.

  • 1clicklabs.io adds 25 ms

    25 ms

    1clicklabs.io costs a phone 25 ms of main-thread work and 1.8 MB 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.

  • rechargecdn.com adds 91 ms

    91 ms

    rechargecdn.com costs a phone 91 ms of main-thread work and 298 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.

  • Improve image delivery

    62 KiB

    4 images could be 62 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • 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: 6 ms

    6 ms

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

Core Web Vitals

6 to fix58
  • Largest Contentful Paint: 18.8 s

    18.8 s

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

  • Time to Interactive: 21.5 s

    21.5 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Total Blocking Time: 342 ms

    342 ms

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

  • 5 images without width and height

    5 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

2 to fix60
  • Page weight: 5.4 MB in 259 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 259 requests on a phone: scripts 2.4 MB (111), images 2.0 MB (17) and other files 748 KiB (105). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    60 KiB

    2 images are downloaded at several times the size a phone draws them, for example bottle-front-glide-50ml.webp at 800 px wide, shown at 209 px. Resized copies would save about 60 KiB.

  • 2 images in older formats

    2 images (157 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 1.5 g of CO₂ per visit

    1.53 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 8991
  • 26 text elements with low contrast

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

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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

4 to fixGoogle 7769
  • 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.

  • 7 H1 headlines

    There are 7 <h1> headlines (“.cls-1{fill:#eb5c9e;}”, “Trusted for Your Most Intimate Moments” and “Trusted for Your Most Intimate Moments”). One clear main headline is easier for people and search engines.

  • 1 link crawlers can't follow

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

  • 40 internal links, 9 external

    The homepage links to 40 pages on oshotwomen.com and 9 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

  • llms.txt published

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

Other pages

4 to fix65
  • 13 pages without a title

    https://oshotwomen.com/collections/all, https://oshotwomen.com/pages/about-us, https://oshotwomen.com/blogs/news, https://oshotwomen.com/products/o-shot-liquid-glide-personal-lubricant, https://oshotwomen.com/products/o-shot-synbiotic-balance and https://oshotwomen.com/products/o-shot%C2%AE-liquid-glide-lube-50ml and 7 others have no <title>, so Google invents the link text in results.

  • 13 pages without a meta description

    https://oshotwomen.com/collections/all, https://oshotwomen.com/pages/about-us, https://oshotwomen.com/blogs/news, https://oshotwomen.com/products/o-shot-liquid-glide-personal-lubricant, https://oshotwomen.com/products/o-shot-synbiotic-balance and https://oshotwomen.com/products/o-shot%C2%AE-liquid-glide-lube-50ml and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://oshotwomen.com/products/o-shot%C2%AE-liquid-glide-lube-50ml, whose canonical is https://oshotwomen.com/products/o-shot%c2%ae-liquid-glide-lube-50ml. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://oshotwomen.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

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

2 checks passed
  • Linked pages load

    All 13 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

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Error from API: undefined”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 376 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “Log In / Register” and “Contact”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 16 cookies set on arrival

    16

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

  • 39 other companies contacted

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

Apps your storefront loads

Ta Mappy Store Locator Maps · Klaviyo Email Marketing Sms · Shopmessage · Yotpo Product Reviews · 1clickpopup · Pushowl · Spin Wheel Ea · Quick Announcement Bar Prod · nofraud.com · nfcube.com · rechargecdn.com · hextom.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 42 issues on oshotwomen.com, including 20 speed issues, 4 SEO issues and 3 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