Website review, no card needed
dzdiscs.com website review
Visit site (opens in a new tab)Reviewed 21 November 202644 issues · 86 checks
This review found 44 issues worth fixing on dzdiscs.com, 15 of them high impact, across 86 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
76C- #75,335 of 124,130 reviewed websitesbeats 35%
- #48,249 of 69,786 online storesbeats 26%
- #45,701 of 63,472 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.3 s |
| Nov 14, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 165 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 129 ms |
| Nov 14, 2026 | 129 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
4.0 s
7.9 s
11.9 s
15.8 s
19.8 s
23.7 s
27.7 s
31.7 s
Speed
Reduce unused JavaScript
7.0 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
3.0 s · 695 KiB18 files are served with short cache lifetimes, so returning visitors download them again (695 KiB).
Improve image delivery
2.6 s · 1.0 MB30 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Minify JavaScript
1.1 s · 201 KiB201 KiB could be saved by minifying JavaScript.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,233 HTML elements
The page has 4,233 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 (productcustomizer.com, Shopify and PayPal and others), adding 2.2 MB and 2.0 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
productcustomizer.com adds 968 ms
968 msproductcustomizer.com costs a phone 968 ms of main-thread work and 26 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 427 ms
427 msShopify costs a phone 427 ms of main-thread work and 1.1 MB 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.
Reduce unused CSS
300 ms · 83 KiBAbout 83 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.
PayPal adds 295 ms
295 msPayPal costs a phone 295 ms of main-thread work and 396 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.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Webkul adds 46 ms
46 msWebkul costs a phone 46 ms of main-thread work and 342 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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: 22 ms
22 msYour server sent the HTML in 22 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: 32.6 s
32.6 sYour largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Subscribe today and save 11% off your first order.”. Most of its time is element render delay (31.2 s).
Time to Interactive: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 232 ms
232 msScripts block taps and scrolling for 232 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user INP: 151 ms
151 msReal visitors wait 151 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: 606 ms
606 msReal visitors wait 606 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 139 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.3 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: 5.6 MB in 487 requests
5.6 MBYour homepage downloads 5.6 MB in 487 requests on a phone: scripts 2.1 MB (136), other files 1.7 MB (282) and images 1.3 MB (46). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (809 KiB) are 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.
7 images far larger than shown
412 KiB7 images are downloaded at several times the size a phone draws them, for example 20252_450x.webp at 450 px wide, shown at 115 px. Resized copies would save about 412 KiB.
5 images below the first screen load straight away
5 images further down the page (138 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 192.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail 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. (2 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “DZ Discs | Disc Golf Equipment and Gear – Drop Zone Disc Golf (DZDiscs)”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (177 characters)
Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.
424 internal links, 15 external
The homepage links to 424 pages on dzdiscs.com and 15 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Drop Zone Disc Golf (DZDiscs)”.
Canonical URL set
The canonical URL is https://www.dzdiscs.com/.
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.dzdiscs.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.
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 (2,645 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dzdiscs.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.dzdiscs.com/collections/new-new-releases and https://www.dzdiscs.com/collections/dzdiscs have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://www.dzdiscs.com/collections/axiom, https://www.dzdiscs.com/collections/discraft, https://www.dzdiscs.com/collections/discmania, https://www.dzdiscs.com/collections/dynamic-discs, https://www.dzdiscs.com/collections/dzdiscs and https://www.dzdiscs.com/collections/gateway and 6 others 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 195 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.
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 13 pages that loaded have a <title>.
Best practices
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 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
33 of 36 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.
Thin social proof
Social proof on the homepage: 30 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.
A 10-field form
Your longest form asks for 10 fields (5 required). Every extra field lowers completion.
About 1,110 words of copy
The homepage carries about 1,110 words of visible text.
3 checks passed
11 calls to action
The homepage has 11 calls to action, for example “DZDiscs Retail Shop - Lawrence, KS”, “Shop Now” and “SHOP NOW”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
38 other companies contacted
Loading the homepage contacts 38 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 dzdiscs.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ecomposer Builder · Judge Me Reviews · Seal Subscriptions · Xcloud Search Filter · Inbox · Forms · Joy Loyalty Program · kxcdn.com · trafficmanager.net · nfcube.com · netlify.app · cloudfront.net · webkul.com · hextom.com · Hulk Product Options
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
- jQuery
- 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 44 issues on dzdiscs.com, including 22 speed issues, 3 SEO issues and 4 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.