Website review, no card needed
steelydanshop.com website review
Visit site (opens in a new tab)Reviewed 13 November 202623 issues · 72 checks
This review found 23 issues worth fixing on steelydanshop.com, 8 of them high impact, across 72 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
80B- #43,283 of 109,350 reviewed websitesbeats 55%
- #28,717 of 61,859 online storesbeats 47%
- #27,632 of 56,401 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 966 ms |
| Jun 13, 2026 | 986 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 929 ms |
| Aug 1, 2026 | 882 ms |
| Aug 8, 2026 | 966 ms |
| Aug 15, 2026 | 946 ms |
| Aug 22, 2026 | 985 ms |
| Aug 29, 2026 | 987 ms |
| Sep 5, 2026 | 981 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.0 s |
| Nov 7, 2026 | 993 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 517 ms |
| May 30, 2026 | 537 ms |
| Jun 6, 2026 | 538 ms |
| Jun 13, 2026 | 544 ms |
| Jun 20, 2026 | 545 ms |
| Jun 27, 2026 | 540 ms |
| Jul 4, 2026 | 532 ms |
| Jul 11, 2026 | 526 ms |
| Jul 18, 2026 | 519 ms |
| Jul 25, 2026 | 517 ms |
| Aug 1, 2026 | 517 ms |
| Aug 8, 2026 | 516 ms |
| Aug 15, 2026 | 516 ms |
| Aug 22, 2026 | 518 ms |
| Aug 29, 2026 | 518 ms |
| Sep 5, 2026 | 517 ms |
| Sep 12, 2026 | 534 ms |
| Sep 19, 2026 | 535 ms |
| Sep 26, 2026 | 527 ms |
| Oct 3, 2026 | 534 ms |
| Oct 10, 2026 | 534 ms |
| Oct 17, 2026 | 536 ms |
| Oct 24, 2026 | 538 ms |
| Oct 31, 2026 | 532 ms |
| Nov 7, 2026 | 517 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.0 s · 324 KiBAbout 324 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 143 KiB11 files are served with short cache lifetimes, so returning visitors download them again (143 KiB).
Mobile performance score: 70
70/100Your mobile performance score is 70. 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 (Google Tag Manager, Attentive and Klaviyo and others), adding 702 KiB and 523 ms of main-thread time.
Render-blocking requests
350 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Improve image delivery
178 KiB9 images could be 178 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 172 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 776 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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 INP: 532 ms
532 msReal visitors wait 532 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 517 ms to 517 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 634 ms
634 msReal visitors wait 634 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 108 ms
108 msScripts block the page for only 108 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 247 requests
2.4 MBYour homepage downloads 2.4 MB in 247 requests on a phone: scripts 888 KiB (65), other files 886 KiB (142) and images 607 KiB (31). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (58 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.2 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (3 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
48 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: 48 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Steely Dan”. Between 30 and 65 characters leaves room to say what you do and for whom.
30 internal links, 4 external
The homepage links to 30 pages on steelydanshop.com and 4 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Official online store of the legendary band Steely Dan. Fans can purchase exclusive merchandise including t-shirts, swe…”.
One H1 headline
Your main headline reads: “<img src="//steelydan.store/cdn/shop/files/logo_250x.png?v=1613724374" srcset="//steelydan.store/cdn/shop/files/logo_25…”.
Canonical URL set
The canonical URL is https://steelydan.store/.
Structured data in place
Structured data found: 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://steelydan.store/sitemap.xml.
AI search readiness
4 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 (244 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://steelydan.store/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://steelydan.store/collections/featured-items, https://steelydan.store/collections/apparel, https://steelydan.store/collections/accessories and https://steelydan.store/collections/music have no meta description, so Google writes the search snippet from whatever text it finds.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://steelydan.store/collections/featured-items/products/the-royal-scam-lp, whose canonical is https://steelydan.store/products/the-royal-scam-lp. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages with very little text
https://steelydan.store/collections/accessories, https://steelydan.store/collections/featured-items/products/the-royal-scam-lp, https://steelydan.store/collections/featured-items/products/katy-lied-lp, https://steelydan.store/collections/featured-items/products/gaucho-lp, https://steelydan.store/collections/featured-items/products/aja-lp and https://steelydan.store/collections/featured-items/products/cant-buy-a-thrill-vinyl-lp and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 28 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
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 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 232 words
The homepage has only about 232 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Can't Buy A Thrill Vinyl”.
2 calls to action
The homepage has 2 calls to action, for example “Can't Buy A Thrill Vinyl” and “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
26 other companies contacted
Loading the homepage contacts 26 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 steelydanshop.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
Minmaxify Order Limits · Klaviyo Email Marketing Sms
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on steelydanshop.com, including 12 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.