Website review, no card needed

stynkeez.com logo

stynkeez.com website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 82 checks

This review found 39 issues worth fixing on stynkeez.com, 14 of them high impact, across 82 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 stynkeez.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stynkeez.com at 0.4 s0.4 s
  2. stynkeez.com at 0.8 s0.8 s
  3. stynkeez.com at 1.3 s1.3 s
  4. stynkeez.com at 1.7 s1.7 s
  5. stynkeez.com at 2.1 s2.1 s
  6. stynkeez.com at 2.5 s2.5 s
  7. stynkeez.com at 3.0 s3.0 s
  8. stynkeez.com at 3.4 s3.4 s

Speed

9 to fix56
  • Reduce unused JavaScript

    2.3 s · 395 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 274 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Yotpo and others), adding 15.8 MB and 746 ms of main-thread time.

  • Shopify adds 214 ms

    214 ms

    Shopify costs a phone 214 ms of main-thread work and 14.9 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.

  • Mobile performance score: 56

    56/100

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

  • Improve image delivery

    300 ms · 364 KiB

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

  • Render-blocking requests

    300 ms

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

  • Main-thread work: 2.7 s

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

  • Yotpo adds 206 ms

    206 ms

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

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 236 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

    44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

6 to fix62
  • Largest Contentful Paint: 16.0 s

    16.0 s

    Your largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Coconut scented Flip flops that feel as good as your favori…”.

  • Time to Interactive: 16.2 s

    16.2 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • 16 images without width and height

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

  • Total Blocking Time: 227 ms

    227 ms

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

  • 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

1 to fix70
  • Page weight: 17.9 MB in 305 requests

    17.9 MB

    Your homepage downloads 17.9 MB in 305 requests on a phone: media 14.3 MB (3), other files 1.3 MB (185) and scripts 1.1 MB (58). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 5.1 g of CO₂ per visit

    5.09 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 6885
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

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

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • 4 form fields without a label

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

  • 4 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 44 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: 44 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9289
  • Title is short (8 characters)

    Your title is only 8 characters: “Stynkeez”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 30 internal links, 5 external

    The homepage links to 30 pages on stynkeez.com and 5 external pages.

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “🌴 Calling All Coconut Lovers! 🌴 Let the soothing scent of coconut carry you away. Every day feels like a beach day wi…”.

  • One H1 headline

    Your main headline reads: “Stynkeez”.

  • Canonical URL set

    The canonical URL is https://stynkeez.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://stynkeez.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

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

Other pages

5 to fix60
  • 1 page without a title

    https://stynkeez.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 2 pages share a title

    / and https://stynkeez.com/products/stynkeez all use the title “Stynkeez”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://stynkeez.com/customer_authentication/redirect, https://stynkeez.com/pages/about, https://stynkeez.com/pages/contact, https://stynkeez.com/policies/shipping-policy, https://stynkeez.com/policies/refund-policy and https://stynkeez.com/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://stynkeez.com/customer_authentication/redirect, https://stynkeez.com/pages/about and https://stynkeez.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://stynkeez.com/pages/contact has 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.

  • 9 internal pages checked

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

2 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

Best practices

3 to fixGoogle 7385
  • 3 small tap targets

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

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 692 words of copy

    The homepage carries about 692 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Register”, “Shop” and “Contact”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 126 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: 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 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.

  • 18 cookies set on arrival

    18

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

  • 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 stynkeez.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Yotpo Loyalty Rewards · Ymq B2b Login Lock Hide Price · Pagefly Ai Page Builder · Essential Post Purchase Upsell

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

  • The footer still says © 2025.

Stack

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on stynkeez.com, including 15 speed issues, 2 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