Website review, no card needed
deathwishinc.com website review
Visit site (opens in a new tab)Reviewed 5 November 202654 issues · 91 checks
This review found 54 issues worth fixing on deathwishinc.com, 22 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60D- #120,485 of 123,879 reviewed websitesbeats 2%
- #69,035 of 69,698 online storesbeats 1%
- #62,950 of 63,406 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 122 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 121 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Reduce unused JavaScript
4.8 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Improve image delivery
2.8 s · 1.2 MB21 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 1.1 MB27 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
1.6 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9,472 HTML elements
The page has 9,472 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Facebook and PayPal and others), adding 2.8 MB and 1.1 s of main-thread time.
Reduce unused CSS
300 ms · 133 KiBAbout 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 413 ms. During a long task the page ignores taps.
YouTube adds 305 ms
305 msYouTube costs a phone 305 ms of main-thread work and 983 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Shopify adds 147 ms
147 msShopify costs a phone 147 ms of main-thread work and 780 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.
cloudfront.net adds 106 ms
106 mscloudfront.net costs a phone 106 ms of main-thread work and 299 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.
Legacy JavaScript
150 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
6 KiB6 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: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user CLS: 1.00
1.00For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 32.5 s
32.5 sYour largest element takes 32.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: 41.1 s
41.1 sThe page becomes fully interactive after 41.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.657
0.657The layout shifts by 0.657 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 674 ms
674 msScripts block taps and scrolling for 674 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
97 images without width and height
97 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 122 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 434 ms
434 msReal visitors wait 434 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 10.8 MB in 396 requests
10.8 MBYour homepage downloads 10.8 MB in 396 requests on a phone: images 6.2 MB (150), scripts 2.9 MB (86) and other files 887 KiB (131). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (535 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.
2 images far larger than shown
298 KiB2 images are downloaded at several times the size a phone draws them, for example Pelican-AfterTheCeilingCracked-Cover_1400x.jpg at 1,400 px wide, shown at 146 px. Resized copies would save about 298 KiB.
3 images below the first screen load straight away
3 images further down the page (577 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
3.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.05 g of CO₂e: 365.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
63 text elements with low contrast
63 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (270 elements)
All page content should be contained by landmarks: 270 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
62 form fields without a label
62 form fields have no label, so screen readers announce an empty box and autofill guesses.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 115 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (14 characters)
Your title is only 14 characters: “Deathwish Inc.”. 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.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
734 internal links, 30 external
The homepage links to 734 pages on deathwishinc.com and 30 external pages.
5 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Deathwish Inc. is an independent record label & distribution company founded by Jacob Bannon and Tre McCarthy in 2000.”.
Canonical URL set
The canonical URL is https://deathwishinc.com/.
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://deathwishinc.com/sitemap.xml.
AI search readiness
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 (2,985 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://deathwishinc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://deathwishinc.com/collections/deathwish-vault, which answers with an error. Visitors hit a dead end and search engines drop it.
5 pages without a meta description
https://deathwishinc.com/collections/chastity, https://deathwishinc.com/collections/pre-order, https://deathwishinc.com/collections/deathwish, https://deathwishinc.com/collections/deathwish-releases and https://deathwishinc.com/collections/deathwish-merch have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://deathwishinc.com/collections/chastity, https://deathwishinc.com/collections/converge, https://deathwishinc.com/collections/pre-order, https://deathwishinc.com/collections/deathwish, https://deathwishinc.com/collections/deathwish-releases and https://deathwishinc.com/collections/deathwish-merch 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 196 found) and read each the way a search engine does.
4 checks passed
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 6 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
162 of 171 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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 598 words of copy
The homepage carries about 598 words of visible text.
2 checks passed
37 calls to action
The homepage has 37 calls to action, for example “Pre-Order”, “Shop” and “Pre-order”.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
40 other companies contacted
Loading the homepage contacts 40 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 deathwishinc.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wishlist Hero · Ufe · Omnisend · Upsell Funnel Engine Upsells · Aftersell · helixo.co · conversionbear.com · cloudfront.net · omegacommerce.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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Founded
- 1999
- Headquarters
- Salem
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on deathwishinc.com, including 24 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.