Website review, no card needed

stylethatkills.com logo

stylethatkills.com website review

Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 66 checks

This review found 32 issues worth fixing on stylethatkills.com, 9 of them high impact, across 66 checks. The most urgent: page weight: 14.1 MB in 61 requests. 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 stylethatkills.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stylethatkills.com at 0.6 s0.6 s
  2. stylethatkills.com at 1.2 s1.2 s
  3. stylethatkills.com at 1.9 s1.9 s
  4. stylethatkills.com at 2.5 s2.5 s
  5. stylethatkills.com at 3.1 s3.1 s
  6. stylethatkills.com at 3.7 s3.7 s
  7. stylethatkills.com at 4.3 s4.3 s
  8. stylethatkills.com at 4.9 s4.9 s

Speed

2 to fix95
  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and Shopify), adding 13.9 MB and 0 ms of main-thread time.

  • Shopify adds 0 ms

    0 ms

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

  • Render-blocking requests

    200 ms

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

  • Improve image delivery

    64 KiB

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

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

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 155 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

3 to fix99
  • Speed Index: 4.8 s

    4.8 s

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

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

  • 2 images without width and height

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

4 checks passed
  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “FLUSH COLLECTION VOUS OFFRE UN STYLE URBAIN ET MODERNE! CET…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.8 s

    1.8 s

    The page is fully interactive after 1.8 s.

Images and page weight

2 to fix60
  • Page weight: 14.1 MB in 61 requests

    14.1 MB

    Your homepage downloads 14.1 MB in 61 requests on a phone: media 13.7 MB (4), images 251 KiB (14) and scripts 158 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    302 KiB

    6 images are downloaded at several times the size a phone draws them, for example F_5bd23d60-11e5-44fd-b6a4-6093318f6849_1200x1200.jpg.webp at 960 px wide, shown at 190 px. Resized copies would save about 302 KiB.

  • 6 images in older formats

    6 images (466 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 4.0 g of CO₂ per visit

    4.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.01 g of CO₂e: 480.7 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 8789
  • 1 button without a name

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

  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (6 elements)

    Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

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

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

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

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

6 to fixGoogle 10070
  • No H1 headline

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

  • Canonical points to another host

    Your canonical URL points to stylethatkills.myshopify.com, not stylethatkills.com, so Google may credit that host instead.

  • No structured data

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

  • Meta description is short (25 characters)

    Your meta description is only 25 characters: “Une Vie, Une Collection !”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.stylethatkills.shopify.com/sitemap.xml, so Google discovers your pages only by following links.

  • 51 internal links, 8 external

    The homepage links to 51 pages on stylethatkills.com and 8 external pages.

2 checks passed
  • Title: 34 characters

    Your title is a healthy 34 characters: “STAKES - Une Vie, Une Collection !”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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.

  • No llms.txt

    There is no https://www.stylethatkills.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.

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.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 3 pages share a title

    /, https://www.stylethatkills.com/collections/flush-collection and https://www.stylethatkills.com/contacts all use the title “STAKES - Une Vie, Une Collection !”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.stylethatkills.com/collections/flush-collection, https://www.stylethatkills.com/product/survetement-gris, https://www.stylethatkills.com/product/survetement-noir, https://www.stylethatkills.com/product/stakes-p-05-2023, https://www.stylethatkills.com/product/stakes-p-02-2023 and https://www.stylethatkills.com/product/t-shirt-oversize-blanc and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.stylethatkills.com/collections/flush-collection has 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 and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 38 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 178 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

Privacy and tracking

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

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Apps on your store

No apps were seen in the code your storefront loads.

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

Framework
SvelteKit
E-commerce
Shopify
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on stylethatkills.com, including 5 speed issues, 6 SEO issues and 6 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