Website review, no card needed
30thstreetguitars.com website review
Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 77 checks
This review found 25 issues worth fixing on 30thstreetguitars.com, 10 of them high impact, across 77 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
83B- #28,732 of 126,652 reviewed websitesbeats 72%
- #18,592 of 70,540 online storesbeats 67%
- #17,991 of 64,024 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 841 ms |
| May 30, 2026 | 865 ms |
| Jun 6, 2026 | 870 ms |
| Jun 13, 2026 | 980 ms |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 947 ms |
| Jul 25, 2026 | 919 ms |
| Aug 1, 2026 | 816 ms |
| Aug 8, 2026 | 816 ms |
| Aug 15, 2026 | 825 ms |
| Aug 22, 2026 | 856 ms |
| Aug 29, 2026 | 870 ms |
| Sep 5, 2026 | 790 ms |
| Sep 12, 2026 | 799 ms |
| Sep 19, 2026 | 856 ms |
| Sep 26, 2026 | 878 ms |
| Oct 3, 2026 | 999 ms |
| Oct 10, 2026 | 920 ms |
| Oct 17, 2026 | 789 ms |
| Oct 24, 2026 | 786 ms |
| Oct 31, 2026 | 841 ms |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 58 ms |
| May 30, 2026 | 62 ms |
| Jun 6, 2026 | 62 ms |
| Jun 13, 2026 | 65 ms |
| Jun 20, 2026 | 62 ms |
| Jun 27, 2026 | 62 ms |
| Jul 4, 2026 | 62 ms |
| Jul 11, 2026 | 61 ms |
| Jul 18, 2026 | 61 ms |
| Jul 25, 2026 | 62 ms |
| Aug 1, 2026 | 59 ms |
| Aug 8, 2026 | 59 ms |
| Aug 15, 2026 | 56 ms |
| Aug 22, 2026 | 55 ms |
| Aug 29, 2026 | 55 ms |
| Sep 5, 2026 | 53 ms |
| Sep 12, 2026 | 53 ms |
| Sep 19, 2026 | 54 ms |
| Sep 26, 2026 | 54 ms |
| Oct 3, 2026 | 59 ms |
| Oct 10, 2026 | 62 ms |
| Oct 17, 2026 | 62 ms |
| Oct 24, 2026 | 62 ms |
| Oct 31, 2026 | 62 ms |
| Nov 7, 2026 | 54 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
Improve image delivery
2.1 s · 357 KiB5 images could be 357 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 33 KiBAbout 33 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 15 KiBAbout 15 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.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 69 KiB and 18 ms of main-thread time.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 258 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 58 ms to 54 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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 INP: 62 ms
62 msReal visitors wait 62 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 464 ms
464 msReal visitors wait 464 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
3 images below the first screen load straight away
3 images further down the page (152 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 119 requests
1.7 MBYour homepage downloads 1.7 MB in 119 requests on a phone: other files 719 KiB (73), images 671 KiB (8) and scripts 243 KiB (30). That is a lean page.
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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
45 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: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (19 characters)
Your title is only 19 characters: “30th Street Guitars”. 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
30 internal links, 2 external
The homepage links to 30 pages on 30thstreetguitars.com and 2 external pages.
4 checks passed
One H1 headline
Your main headline reads: “30th Street Guitars”.
Canonical URL set
The canonical URL is https://www.30thstreetguitars.com/.
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.30thstreetguitars.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.
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.
llms.txt published
The site publishes https://www.30thstreetguitars.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.30thstreetguitars.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.30thstreetguitars.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://www.30thstreetguitars.com/collections, https://www.30thstreetguitars.com/collections/guitars, https://www.30thstreetguitars.com/collections/effects, https://www.30thstreetguitars.com/collections/pickups, https://www.30thstreetguitars.com/collections/rust and https://www.30thstreetguitars.com/collections/accessories and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.30thstreetguitars.com/collections and https://www.30thstreetguitars.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.30thstreetguitars.com/collections and https://www.30thstreetguitars.com/pages/testimonials 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.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
9 of 10 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 60 words
The homepage has only about 60 words of visible text; thin pages give Google and first-time buyers little to go on.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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
2 calls to action
The homepage has 2 calls to action, for example “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
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 30thstreetguitars.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
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on 30thstreetguitars.com, including 6 speed issues, 5 SEO issues and 5 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.