Website review, no card needed
dadgang.co website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 80 checks
This review found 31 issues worth fixing on dadgang.co, 9 of them high impact, across 80 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
83B- #28,143 of 123,862 reviewed websitesbeats 72%
- #18,424 of 69,698 online storesbeats 67%
- #17,844 of 63,406 Shopify storesbeats 65%
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.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 998 ms |
| Jul 4, 2026 | 971 ms |
| Jul 11, 2026 | 972 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 999 ms |
| Aug 8, 2026 | 971 ms |
| Aug 15, 2026 | 963 ms |
| Aug 22, 2026 | 989 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 990 ms |
| Sep 19, 2026 | 919 ms |
| Sep 26, 2026 | 887 ms |
| Oct 3, 2026 | 851 ms |
| Oct 10, 2026 | 839 ms |
| Oct 17, 2026 | 840 ms |
| Oct 24, 2026 | 843 ms |
| Oct 31, 2026 | 868 ms |
| Nov 7, 2026 | 860 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 100 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 99 ms |
| Sep 26, 2026 | 99 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 111 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
Speed
Reduce unused JavaScript
6.9 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 1.2 MB28 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,541 HTML elements
The page has 4,541 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 (Google Tag Manager, Google CDN and Shopify and others), adding 2.2 MB and 1.1 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
847 KiB12 images could be 847 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
350 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Reduce unused CSS
300 ms · 44 KiBAbout 44 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.
Google CDN adds 252 ms
252 msGoogle CDN costs a phone 252 ms of main-thread work and 774 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.
Google Tag Manager adds 280 ms
280 msGoogle Tag Manager costs a phone 280 ms of main-thread work and 344 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.
Shopify adds 172 ms
172 msShopify costs a phone 172 ms of main-thread work and 561 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 · 69 KiBPolyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 11.7 s
11.7 sThe first text or image appears after 11.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.1 s
22.1 sYour largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “White and orange dad gang hat against a dark background”.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 208 ms
208 msScripts block taps and scrolling for 208 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 100 ms to 111 ms 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: 106 ms
106 msReal visitors wait 106 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.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: 682 ms
682 msReal visitors wait 682 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 328 requests
6.0 MBYour homepage downloads 6.0 MB in 328 requests on a phone: scripts 2.7 MB (122), images 1.4 MB (54) and other files 1.0 MB (98). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 56 images in the HTML carry an alt attribute.
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (25 characters)
Your title is only 25 characters: “Dad Gang Co. – dadgang.co”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (163 characters)
Your meta description is 163 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.
94 internal links, 9 external
The homepage links to 94 pages on dadgang.co and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.dadgang.co/.
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.dadgang.co/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 (1,422 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dadgang.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://www.dadgang.co/collections/shop-all, https://www.dadgang.co/collections/t-shirts, https://www.dadgang.co/collections/bundles, https://www.dadgang.co/collections/kid-gang, https://www.dadgang.co/collections/sale and https://www.dadgang.co/pages/store-locator and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.dadgang.co/products/horsepower-black-gold and https://www.dadgang.co/products/the-garage-hat-black-red use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://www.dadgang.co/collections/shop-all, https://www.dadgang.co/collections/t-shirts, https://www.dadgang.co/collections/bundles, https://www.dadgang.co/collections/kid-gang, https://www.dadgang.co/collections/sale and https://www.dadgang.co/collections/collegiate 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 45 found) and read each the way a search engine does.
5 checks passed
Linked pages load
10 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 10 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 898 words of copy
The homepage carries about 898 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP HATS →” and “SHOP APPAREL →”.
8 calls to action
The homepage has 8 calls to action, for example “SHOP ALL”, “SHOP HATS →” and “SHOP APPAREL →”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 3 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 3 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.
41 other companies contacted
Loading the homepage contacts 41 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 dadgang.co, 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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Attentive · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Pagefly Ai Page Builder · Gempages Builder · Redo · Gdpr Cookie Consent · Applovin Shop Integration · Aftersell · Upcart · rise-ai.com · socialsnowball.io · richpanel.com · attn.tv · nfcube.com · hextom.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
- Hosting
- Shopify
Company
- Headquarters
- Seattle
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on dadgang.co, including 17 speed issues, 4 SEO issues and 1 conversion gap. 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.