Website review, no card needed

sexyliving.com logo

sexyliving.com website review

Visit site (opens in a new tab)Reviewed 17 November 202622 issues · 82 checks

This review found 22 issues worth fixing on sexyliving.com, 9 of them high impact, across 82 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
1.1 s586 msMay 30Nov 14986 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026670 ms
Jun 6, 2026644 ms
Jun 13, 2026717 ms
Jun 20, 2026712 ms
Jun 27, 2026744 ms
Jul 4, 2026775 ms
Jul 11, 2026834 ms
Jul 18, 2026818 ms
Jul 25, 2026778 ms
Aug 1, 2026728 ms
Aug 8, 2026695 ms
Aug 15, 2026680 ms
Aug 22, 2026712 ms
Aug 29, 2026752 ms
Sep 5, 2026671 ms
Sep 12, 2026701 ms
Sep 19, 2026759 ms
Sep 26, 2026785 ms
Oct 3, 2026901 ms
Oct 10, 2026976 ms
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 20261.0 s
Nov 14, 2026986 ms
Real-visitor tap response (INP)75th percentile, phones
137 ms70 msMay 30Nov 1478 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026129 ms
Jun 6, 2026106 ms
Jun 13, 202688 ms
Jun 20, 202685 ms
Jun 27, 202683 ms
Jul 4, 202687 ms
Jul 11, 202685 ms
Jul 18, 202687 ms
Jul 25, 202681 ms
Aug 1, 202680 ms
Aug 8, 202686 ms
Aug 15, 202683 ms
Aug 22, 202687 ms
Aug 29, 202686 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202681 ms
Oct 10, 202681 ms
Oct 17, 202680 ms
Oct 24, 202681 ms
Oct 31, 202679 ms
Nov 7, 202679 ms
Nov 14, 202678 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. sexyliving.com at 0.6 s0.6 s
  2. sexyliving.com at 1.1 s1.1 s
  3. sexyliving.com at 1.7 s1.7 s
  4. sexyliving.com at 2.3 s2.3 s
  5. sexyliving.com at 2.8 s2.8 s
  6. sexyliving.com at 3.4 s3.4 s
  7. sexyliving.com at 3.9 s3.9 s
  8. sexyliving.com at 4.5 s4.5 s

Speed

5 to fix64
  • Improve image delivery

    2.9 s · 898 KiB

    18 images could be 898 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 64

    64/100

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

  • Reduce unused JavaScript

    500 ms · 220 KiB

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

  • Shopify adds 130 ms

    130 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Hubspot and others), adding 743 KiB and 405 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    98 KiB

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

  • Reduce unused CSS

    50 ms · 10 KiB

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

  • Legacy JavaScript

    14 KiB

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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 668 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

7 to fix100
  • Largest Contentful Paint: 10.5 s

    10.5 s

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

  • Time to Interactive: 11.4 s

    11.4 s

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

  • Largest content (LCP) got 52% slower for real visitors

    +52%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.7 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 5.1 s

    5.1 s

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

  • Cumulative Layout Shift: 0.14

    0.14

    The layout shifts by 0.14 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 15 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 482 ms

    482 ms

    Real visitors wait 482 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 33% faster for real visitors

    -33%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 129 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 101 ms

    101 ms

    Scripts block the page for only 101 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 3.1 MB in 233 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 233 requests on a phone: images 1.4 MB (60), scripts 817 KiB (50) and other files 682 KiB (82). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    384 KiB

    6 images are downloaded at several times the size a phone draws them, for example HomePage_Hero_Image_with_logo_1.png at 1,739 px wide, shown at 390 px. Resized copies would save about 384 KiB.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

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

Accessibility

4 to fixGoogle 8294
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • 5 text elements with low contrast

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

  • 4 images without alt text

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

  • 55 links without text

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

Google 92100
  • 180 internal links, 20 external

    The homepage links to 180 pages on sexyliving.com and 20 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Wholesale sex toys in Canada from Sexy Living, distributor & dropshipper since 2000. 200 brands, testers, staff trainin…”.

  • One H1 headline

    Your main headline reads: “CANADA'S WHOLESALE SEX TOY DISTRIBUTOR & DROPSHIPPER”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Wholesale Sex Toys Canada | Sex Toy Distributor | Sexy Living”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, 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://sexyliving.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://sexyliving.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,116 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 105 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 1 page 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 1 page that loaded have a <title>.

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 “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix72
  • 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.

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

  • About 591 words of copy

    The homepage carries about 591 words of visible text.

6 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Sign Up”, “Wholesale Sign up” and “Drop-shipping Sign up”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics, HubSpot and Plausible.

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 5 of them by other companies (measured from a US location before any click).

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 sexyliving.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on sexyliving.com, including 12 speed 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