Website review, no card needed
dingo1969.com website review
Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 91 checks
This review found 39 issues worth fixing on dingo1969.com, 14 of them high impact, across 91 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
82B- #32,067 of 112,955 reviewed websitesbeats 66%
- #21,630 of 64,988 online storesbeats 60%
- #20,934 of 59,421 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 125 ms |
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 131 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 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
3.8 s · 909 KiBAbout 909 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Use efficient cache lifetimes
2.8 s · 502 KiB36 files are served with short cache lifetimes, so returning visitors download them again (502 KiB).
audioeye.com adds 2.3 s
2.3 saudioeye.com costs a phone 2.3 s of main-thread work and 312 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.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Yotpo and Klaviyo and others), adding 2.5 MB and 3.0 s of main-thread time.
Improve image delivery
750 ms · 617 KiB21 images could be 617 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
350 ms · 114 KiBPolyfills for old browsers add 114 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Duplicated JavaScript
350 ms · 17 KiB17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.
Yotpo adds 237 ms
237 msYotpo costs a phone 237 ms of main-thread work and 438 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.
2,714 HTML elements
The page has 2,714 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 166 ms
166 msKlaviyo costs a phone 166 ms of main-thread work and 346 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 72 ms
72 msShopify costs a phone 72 ms of main-thread work and 1.0 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.
Reduce unused CSS
30 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.
Render-blocking requests
50 ms19 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
Minify JavaScript
38 KiB38 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.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.6 s
27.6 sYour largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.1 s
17.1 sVisually, the page fills in at 17.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 34.0 s
34.0 sThe page becomes fully interactive after 34.0 s. Good is under 3.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 223 ms
223 msScripts block taps and scrolling for 223 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (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: 579 ms
579 msReal visitors wait 579 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 507 requests
6.5 MBYour homepage downloads 6.5 MB in 507 requests on a phone: scripts 2.4 MB (252), images 2.1 MB (52) and fonts 1.1 MB (23). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (63 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 222.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (8 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 37 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
89 internal links, 5 external
The homepage links to 89 pages on dingo1969.com and 5 external pages.
6 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Dingo 1969 - Fashion Boots for Women and Men – Dingo1969”.
Canonical URL set
The canonical URL is https://dingo1969.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://dingo1969.com/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 (573 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dingo1969.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a title
https://dingo1969.com/products/thunder-road-leather-boot-green, https://dingo1969.com/products/thunder-road-leather-boot-red, https://dingo1969.com/products/thunder-road-leather-boot-camel, https://dingo1969.com/products/thunder-road-leather-boot-blue and https://dingo1969.com/products/thunder-road-leather-boot-fuchsia all use the title “THUNDER ROAD LEATHER BOOT – Dingo1969”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://dingo1969.com/collections/all, https://dingo1969.com/collections/women, https://dingo1969.com/collections/womens-new-arrivals, https://dingo1969.com/collections/womens-boots, https://dingo1969.com/collections/womens-booties and https://dingo1969.com/collections/vintage and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://dingo1969.com/products/thunder-road-leather-boot-green, https://dingo1969.com/products/thunder-road-leather-boot-red, https://dingo1969.com/products/thunder-road-leather-boot-camel, https://dingo1969.com/products/thunder-road-leather-boot-blue and https://dingo1969.com/products/thunder-road-leather-boot-fuchsia use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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.
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 14 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
29 of 31 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 268 words of copy
The homepage carries about 268 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NEW” and “SIGN UP NOW”.
8 calls to action
The homepage has 8 calls to action, for example “Shop All”, “SHOP NEW” and “Shop the Collection”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
50 other companies contacted
Loading the homepage contacts 50 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 dingo1969.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
Powerful Form Builder · Yotpo Product Reviews · Optimonk Popup Cro A B Test · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Cartbite · Monk Free Gift With Purchase · Forms · Product Colors · Wishlist Power · Back In Stock · cnversion.io · gorgias.chat · 9gtb.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
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 dingo1969.com, including 19 speed issues, 2 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.