Website review, no card needed

overkillshop.com logo

overkillshop.com website review

Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 81 checks

This review found 31 issues worth fixing on overkillshop.com, 12 of them high impact, across 81 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
201 ms120 msMay 16Oct 31192 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026136 ms
May 30, 2026138 ms
Jun 6, 2026133 ms
Jun 13, 2026133 ms
Jun 20, 2026134 ms
Jun 27, 2026129 ms
Jul 4, 2026139 ms
Jul 11, 2026148 ms
Jul 18, 2026164 ms
Jul 25, 2026176 ms
Aug 1, 2026178 ms
Aug 8, 2026174 ms
Aug 15, 2026174 ms
Aug 22, 2026173 ms
Aug 29, 2026177 ms
Sep 5, 2026186 ms
Sep 12, 2026184 ms
Sep 19, 2026177 ms
Sep 26, 2026169 ms
Oct 3, 2026165 ms
Oct 10, 2026167 ms
Oct 17, 2026173 ms
Oct 24, 2026182 ms
Oct 31, 2026192 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 overkillshop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. overkillshop.com at 2.3 s2.3 s
  2. overkillshop.com at 4.5 s4.5 s
  3. overkillshop.com at 6.8 s6.8 s
  4. overkillshop.com at 9.1 s9.1 s
  5. overkillshop.com at 11.3 s11.3 s
  6. overkillshop.com at 13.6 s13.6 s
  7. overkillshop.com at 15.9 s15.9 s
  8. overkillshop.com at 18.1 s18.1 s

Speed

10 to fix68
  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 4.7 s

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

  • 3,999 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Cookiebot and others), adding 1.6 MB and 1.0 s of main-thread time.

  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    530 KiB

    About 530 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 313 ms

    313 ms

    Google Tag Manager costs a phone 313 ms of main-thread work and 645 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.

  • Clarity adds 312 ms

    312 ms

    Clarity costs a phone 312 ms of main-thread work and 30 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.

  • Klaviyo adds 132 ms

    132 ms

    Klaviyo costs a phone 132 ms of main-thread work and 322 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.

  • azurefd.net adds 32 ms

    32 ms

    azurefd.net costs a phone 32 ms of main-thread work and 323 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

    150 ms · 128 KiB

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

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    77 KiB

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

  • Reduce unused CSS

    43 KiB

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

  • Legacy JavaScript

    28 KiB

    Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    19 KiB

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

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Speed Index: 20.4 s

    20.4 s

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

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person wearing waterproof sneakers and blue jeans standing …”.

  • Real-user INP: 221 ms

    221 ms

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

  • Total Blocking Time: 363 ms

    363 ms

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 628 ms

    628 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • 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 471 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 471 requests on a phone: images 1.9 MB (51), scripts 1.6 MB (110) and other files 1.5 MB (284). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (586 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.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8995
  • 50 tap targets too small

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

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

    All page content should be contained by landmarks: 16 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.

  • 5 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 235 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • Meta description is long (268 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 413 internal links, 6 external

    The homepage links to 413 pages on overkillshop.com and 6 external pages.

5 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “OVERKILL | Finest sneaker & streetwear from Berlin to the world”.

  • Canonical URL set

    The canonical URL is https://www.overkillshop.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.overkillshop.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.overkillshop.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, 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 (1,142 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.overkillshop.com/collections/archive has no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.overkillshop.com/collections/soon, https://www.overkillshop.com/collections/sneaker-men, https://www.overkillshop.com/collections/sneaker-women, https://www.overkillshop.com/collections/sneaker-kids, https://www.overkillshop.com/collections/apparel-men and https://www.overkillshop.com/collections/apparel-women and 6 others 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 194 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    12 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9684
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=211049975&Ver=2&mid=b5dcd8ea-88a0-44c0-b32c-387c4a7c9ee1&bo=3&sid=965bf700d8b111f18466e3843257a6ba&vid=965c0fd0d8b111f1a8ccd112b834a671&vids=1&msclkid=N&pi=918639831&l.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 720 words of visible text.

3 checks passed
  • 35 calls to action

    The homepage has 35 calls to action, for example “SHOP THE LOOK”, “Quick buy” and “Shop the whole collection”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

  • 8 trackers load before any consent

    8

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

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 overkillshop.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Latori Best Price Indicator · Analyzify Ga4 Ads Tracking · Klaviyo Email Marketing · Price Indication Regulation · Klarna On Site Messaging · Eu Widerruf Button · webgains.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
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on overkillshop.com, including 17 speed issues, 3 SEO issues and 2 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