Website review, no card needed
dannygonzalez.store website review
Visit site (opens in a new tab)Reviewed 10 November 202618 issues · 73 checks
This review found 18 issues worth fixing on dannygonzalez.store, 1 of them high impact, across 73 checks. The most urgent: 33 text elements with low contrast. 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
89B- #3,438 of 109,350 reviewed websitesbeats 95%
- #1,788 of 61,859 online storesbeats 95%
- #1,736 of 56,401 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 907 ms |
| May 30, 2026 | 871 ms |
| Jun 6, 2026 | 858 ms |
| Jun 13, 2026 | 894 ms |
| Jun 20, 2026 | 910 ms |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 890 ms |
| Aug 8, 2026 | 862 ms |
| Aug 15, 2026 | 883 ms |
| Aug 22, 2026 | 859 ms |
| Aug 29, 2026 | 868 ms |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 86 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 85 ms |
| Jun 13, 2026 | 84 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 72 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 67 ms |
| Aug 8, 2026 | 69 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 70 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 75 ms |
| Sep 19, 2026 | 76 ms |
| Sep 26, 2026 | 78 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 76 ms |
| Oct 24, 2026 | 73 ms |
| Oct 31, 2026 | 71 ms |
| Nov 7, 2026 | 70 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
Render-blocking requests
200 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Improve image delivery
95 KiB2 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 94 KiB and 27 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 95
95/100Your mobile performance score is 95. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 179 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
11 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 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: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 568 ms
568 msReal visitors wait 568 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 86 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Merch by Greg,”.
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.
Time to Interactive: 1.9 s
1.9 sThe page is fully interactive after 1.9 s.
Images and page weight
1 image far larger than shown
80 KiB1 image is downloaded at several times the size a phone draws it, for example unnamed.jpg at 3,993 px wide, shown at 306 px. Resized copies would save about 80 KiB.
2 images below the first screen load straight away
2 images further down the page (145 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.34 g of CO₂e: 41.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.2 MB in 107 requests
1.2 MBYour homepage downloads 1.2 MB in 107 requests on a phone: other files 626 KiB (58), images 323 KiB (5) and scripts 187 KiB (33). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
33 text elements with low contrast
33 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
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 19 images in the HTML carry an alt attribute.
44 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: 44 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Merch by Greg, for Greg .” and “LIVE SHOWS!”). One clear main headline is easier for people and search engines.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
38 internal links, 39 external
The homepage links to 38 pages on dannygonzalez.store and 39 external pages.
6 checks passed
Meta description: 87 characters
Your meta description is 87 characters: “Official site for all apparel, accessories, exclusive bundles and limited collectables!”.
Title: 49 characters
Your title is a healthy 49 characters: “Danny Gonzalez Official Store – Danny Gonzalez Us”.
Canonical URL set
The canonical URL is https://www.dannygonzalez.store/.
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.dannygonzalez.store/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 (710 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dannygonzalez.store/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.dannygonzalez.store/pages/live-shows, https://www.dannygonzalez.store/collections/all and https://www.dannygonzalez.store/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages with very little text
https://www.dannygonzalez.store/collections/t-shirts, https://www.dannygonzalez.store/collections/apparel and https://www.dannygonzalez.store/collections/accessories 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 17 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 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.
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
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
15 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 670 words of copy
The homepage carries about 670 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “Shop”.
4 calls to action
The homepage has 4 calls to action, for example “Shop”, “SIGN UP NOW” and “Sign up now”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
6 other companies contacted
Loading the homepage contacts 6 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 dannygonzalez.store, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Revoq Eu Withdrawal Button
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on dannygonzalez.store, including 3 speed issues, 3 SEO issues 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.