Website review, no card needed
heydude.com website review
Visit site (opens in a new tab)Reviewed 11 October 202647 issues · 100 checks
This review found 47 issues worth fixing on heydude.com, 22 of them high impact, across 100 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
65D- #107,677 of 115,917 reviewed websitesbeats 6%
- #64,306 of 66,651 online storesbeats 3%
- #213 of 272 Salesforce Commerce Cloud storesbeats 19%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.8 s |
| Apr 25, 2026 | 1.8 s |
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 194 ms |
| Apr 25, 2026 | 196 ms |
| May 2, 2026 | 196 ms |
| May 9, 2026 | 195 ms |
| May 16, 2026 | 191 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 204 ms |
| Aug 15, 2026 | 207 ms |
| Aug 22, 2026 | 208 ms |
| Aug 29, 2026 | 212 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 220 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 222 ms |
| Oct 3, 2026 | 221 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
1.4 s
2.8 s
4.3 s
5.7 s
7.1 s
8.5 s
10.0 s
11.4 s
Speed
Reduce unused JavaScript
5.7 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Render-blocking requests
4.8 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Use efficient cache lifetimes
1.6 s · 2.2 MB47 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Main-thread work: 14.3 s
A phone's processor spends 14.3 s on main-thread work while loading, 6.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 10). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ContentSquare and sinch.com and others), adding 2.0 MB and 2.4 s of main-thread time.
Google Tag Manager adds 794 ms
794 msGoogle Tag Manager costs a phone 794 ms of main-thread work and 630 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.
Improve image delivery
600 ms · 235 KiB4 images could be 235 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
450 ms · 129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
ContentSquare adds 460 ms
460 msContentSquare costs a phone 460 ms of main-thread work and 180 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.
sinch.com adds 311 ms
311 mssinch.com costs a phone 311 ms of main-thread work and 529 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.
Facebook adds 286 ms
286 msFacebook costs a phone 286 ms of main-thread work and 224 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,108 HTML elements
The page has 2,108 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 80 KiBPolyfills for old browsers add 80 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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: 3 ms
3 msYour server sent the HTML in 3 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: 47.4 s
47.4 sYour largest element takes 47.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 16.7 s
16.7 sVisually, the page fills in at 16.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 59.5 s
59.5 sThe page becomes fully interactive after 59.5 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.109
0.109The layout shifts by 0.109 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 194 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
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 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: 474 ms
474 msReal visitors wait 474 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 16.5 MB in 409 requests
16.5 MBYour homepage downloads 16.5 MB in 409 requests on a phone: images 10.8 MB (102), scripts 4.3 MB (107) and fonts 1,008 KiB (11). Under 2 MB keeps phones on slow connections fast.
22 images far larger than shown
1.6 MB22 images are downloaded at several times the size a phone draws them, for example Crocs at 1,905 px wide, shown at 311 px. Resized copies would save about 1.6 MB.
28 images below the first screen load straight away
28 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.7 g of CO₂ per visit
4.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.67 g of CO₂e: 560.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
21 buttons without a name
21 buttons have no accessible name, so screen readers announce just “button”.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Orphan list items
Some list items are not inside a list.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor 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.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 11 failed. 6 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.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
26 internal links, 6 external
The homepage links to 26 pages on heydude.com and 6 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Welcome to the World of Heydude”.
Title: 62 characters
Your title is a healthy 62 characters: “Comfortable & Durable Shoes for Men, Women, and Kids | HeyDude”.
Canonical URL set
The canonical URL is https://www.heydude.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.heydude.com/sitemap_index.xml.
AI search readiness
Most text only appears after JavaScript runs
10%A phone browser shows 924 words, but the HTML your server sends has only 96. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.heydude.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
1 page without a meta description
https://www.heydude.com/on/demandware.store/Sites-heydude_us-Site/default/SizeChart-Show has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.heydude.com/website-accessibility.html, https://www.heydude.com/on/demandware.store/Sites-heydude_us-Site/default/Cart-Show, https://www.heydude.com/c/women, https://www.heydude.com/c/men, https://www.heydude.com/c/kids and https://www.heydude.com/c/sale and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://www.heydude.com/website-accessibility.html, https://www.heydude.com/on/demandware.store/Sites-heydude_us-Site/default/Cart-Show, https://www.heydude.com/c/women, https://www.heydude.com/c/men, https://www.heydude.com/c/kids and https://www.heydude.com/c/sale and 5 others 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 21 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 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.heydude.com/.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 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”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
62 of 74 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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 924 words of copy
The homepage carries about 924 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 Now” and “Shop All Men's Shoes”.
3 calls to action
The homepage has 3 calls to action, for example “Track Your Order”, “Start a Return” and “Contact Us”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
65 cookies set on arrival
65Opening the homepage sets 65 cookies (measured from a US location before any click).
73 other companies contacted
Loading the homepage contacts 73 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 heydude.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on heydude.com, including 23 speed issues, 2 SEO issues and 2 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.