Website review, no card needed
chicagomusicexchange.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 84 checks
This review found 39 issues worth fixing on chicagomusicexchange.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
78C- #62,191 of 124,112 reviewed websitesbeats 44%
- #40,578 of 69,786 online storesbeats 36%
- #38,744 of 63,472 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 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.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 206 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 220 ms |
| Jun 13, 2026 | 224 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 236 ms |
| Jul 4, 2026 | 239 ms |
| Jul 11, 2026 | 242 ms |
| Jul 18, 2026 | 241 ms |
| Jul 25, 2026 | 241 ms |
| Aug 1, 2026 | 239 ms |
| Aug 8, 2026 | 239 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 245 ms |
| Aug 29, 2026 | 238 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 222 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 212 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 212 ms |
| Oct 31, 2026 | 213 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Improve image delivery
4.3 s · 1.7 MB33 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.
audioeye.com adds 2.4 s
2.4 saudioeye.com costs a phone 2.4 s of main-thread work and 333 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,159 HTML elements
The page has 7,159 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 (audioeye.com, Google Tag Manager and athoscommerce.io and others), adding 2.6 MB and 3.2 s of main-thread time.
Reduce unused JavaScript
450 ms · 782 KiBAbout 782 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 565 KiB46 files are served with short cache lifetimes, so returning visitors download them again (565 KiB).
Google Tag Manager adds 293 ms
293 msGoogle Tag Manager costs a phone 293 ms of main-thread work and 545 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
Shopify adds 139 ms
139 msShopify costs a phone 139 ms of main-thread work and 921 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
200 ms · 54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 36 KiBAbout 36 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
11 KiB11 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: 15 ms
15 msYour server sent the HTML in 15 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.
Largest Contentful Paint: 26.9 s
26.9 sYour largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.7 s
17.7 sVisually, the page fills in at 17.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.0 s
39.0 sThe page becomes fully interactive after 39.0 s. Good is under 3.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 553 ms
553 msScripts block taps and scrolling for 553 ms in total while the page loads. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.111
0.111The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 206 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 193 ms
193 msReal visitors wait 193 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.3 MB in 429 requests
9.3 MBYour homepage downloads 9.3 MB in 429 requests on a phone: images 5.4 MB (64), scripts 2.4 MB (156) and other files 963 KiB (153). Under 2 MB keeps phones on slow connections fast.
10 images far larger than shown
1.3 MB10 images are downloaded at several times the size a phone draws them, for example 10.27.26_-_Holiday_Sale_01-18.jpg at 1,620 px wide, shown at 390 px. Resized copies would save about 1.3 MB.
An image on the first screen is lazy-loaded
10.27.26_-_Holiday_Sale_01-18.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 (100 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.
About 2.6 g of CO₂ per visit
2.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.64 g of CO₂e: 316.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
75 text elements with low contrast
75 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 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 (22 characters)
Your title is only 22 characters: “Chicago Music Exchange”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (318 characters)
Your meta description is 318 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
88 internal links, 13 external
The homepage links to 88 pages on chicagomusicexchange.com and 13 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.chicagomusicexchange.com/.
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://www.chicagomusicexchange.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.chicagomusicexchange.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,158 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.chicagomusicexchange.com/pages/shipping, https://www.chicagomusicexchange.com/pages/about-contact-us, https://www.chicagomusicexchange.com/pages/sell-and-trade-your-gear and https://www.chicagomusicexchange.com/pages/support have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.chicagomusicexchange.com/pages/shipping, https://www.chicagomusicexchange.com/pages/about-contact-us, https://www.chicagomusicexchange.com/pages/sell-and-trade-your-gear, https://www.chicagomusicexchange.com/pages/support and https://www.chicagomusicexchange.com/collections/all-sale-items have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.chicagomusicexchange.com/pages/sell-and-trade-your-gear has 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 56 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
23 small tap targets
23 of 71 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'getRegistrations')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 690 words of copy
The homepage carries about 690 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download The CME App Today!” and “SHOP NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Download The CME App Today!”, “Contact” and “Call”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and 7 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (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.
51 other companies contacted
Loading the homepage contacts 51 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 chicagomusicexchange.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Buddha Mega Menu Navigation · Pagefly Ai Page Builder · Globo Mega Menu · Klaviyo Email Marketing Sms · Tapcart Mobile App · Tolstoy · Swish Wishlist King · stamped.io · trafficmanager.net · nofraud.com · gorgias.chat · cloudfront.net · 9gtb.com · googleapis.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
- Hosting
- Shopify
Company
- Headquarters
- Chicago
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on chicagomusicexchange.com, including 22 speed issues and 4 SEO issues. 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.