Website review, no card needed

sweetspotskirts.com logo

sweetspotskirts.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 78 checks

This review found 36 issues worth fixing on sweetspotskirts.com, 12 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 sweetspotskirts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sweetspotskirts.com at 1.0 s1.0 s
  2. sweetspotskirts.com at 1.9 s1.9 s
  3. sweetspotskirts.com at 2.9 s2.9 s
  4. sweetspotskirts.com at 3.8 s3.8 s
  5. sweetspotskirts.com at 4.8 s4.8 s
  6. sweetspotskirts.com at 5.8 s5.8 s
  7. sweetspotskirts.com at 6.7 s6.7 s
  8. sweetspotskirts.com at 7.7 s7.7 s

Speed

10 to fix56
  • Reduce unused JavaScript

    3.2 s · 667 KiB

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

  • Improve image delivery

    600 ms · 1.5 MB

    21 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and improvedcontactform.com and others), adding 1.7 MB and 539 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 138 KiB

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

  • YouTube adds 324 ms

    324 ms

    YouTube costs a phone 324 ms of main-thread work and 992 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.

  • Main-thread work: 3.0 s

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

  • Render-blocking requests

    300 ms

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

  • 2,379 HTML elements

    The page has 2,379 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 171 ms

    171 ms

    Shopify costs a phone 171 ms of main-thread work and 534 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

    150 ms · 109 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    7 KiB

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

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

4 to fix66
  • Largest Contentful Paint: 26.5 s

    26.5 s

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

  • Time to Interactive: 27.7 s

    27.7 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 9.6 s

    9.6 s

    Visually, the page fills in at 9.6 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.

2 checks passed
  • Cumulative Layout Shift: 0.06

    0.06

    The layout barely moves while loading (CLS 0.06, good is under 0.1).

  • Total Blocking Time: 25 ms

    25 ms

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

Images and page weight

2 to fix69
  • Page weight: 8.0 MB in 409 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 409 requests on a phone: images 4.9 MB (51), scripts 1.5 MB (133) and other files 1.1 MB (184). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Photoroom_20251207_194956.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 (129 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.

  • 1 image below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.26 g

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

8 to fixGoogle 9291
  • Hidden but focusable

    15 elements hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

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

3 to fixGoogle 10081
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (204 characters)

    Your meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("/")”.

  • Open Graph partly set

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

  • 158 internal links, 8 external

    The homepage links to 158 pages on sweetspotskirts.com and 8 external pages.

4 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Activewear | Sweet Spot Skirts”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://sweetspotskirts.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://sweetspotskirts.com/collections/all-skirts-in-collection and https://sweetspotskirts.com/collections/all-tops have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://sweetspotskirts.com/collections/all-skirts-in-collection, https://sweetspotskirts.com/collections/classic-essentials, https://sweetspotskirts.com/collections/walkabout-skirt-2-inches-longer, https://sweetspotskirts.com/collections/fast-n-flirty-running-skirts and https://sweetspotskirts.com/collections/all-tops have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    5 pages 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.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 14 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 742 words of visible text.

2 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “QUICK SHOP”, “Join” and “SignUp”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

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

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

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

Inbox · improvedcontactform.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Vancouver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on sweetspotskirts.com, including 14 speed issues, 3 SEO issues and 4 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