Website review, no card needed
dormieworkshop.ca website review
Visit site (opens in a new tab)Reviewed 7 November 202644 issues · 83 checks
This review found 44 issues worth fixing on dormieworkshop.ca, 14 of them high impact, across 83 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,296 of 124,051 reviewed websitesbeats 35%
- #48,233 of 69,761 online storesbeats 26%
- #45,685 of 63,450 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 825 ms |
| May 23, 2026 | 793 ms |
| May 30, 2026 | 758 ms |
| Jun 6, 2026 | 749 ms |
| Jun 13, 2026 | 751 ms |
| Jun 20, 2026 | 742 ms |
| Jun 27, 2026 | 728 ms |
| Jul 4, 2026 | 727 ms |
| Jul 11, 2026 | 735 ms |
| Jul 18, 2026 | 755 ms |
| Jul 25, 2026 | 767 ms |
| Aug 1, 2026 | 797 ms |
| Aug 8, 2026 | 794 ms |
| Aug 15, 2026 | 809 ms |
| Aug 22, 2026 | 836 ms |
| Aug 29, 2026 | 852 ms |
| Sep 5, 2026 | 868 ms |
| Sep 12, 2026 | 883 ms |
| Sep 19, 2026 | 873 ms |
| Sep 26, 2026 | 807 ms |
| Oct 3, 2026 | 814 ms |
| Oct 10, 2026 | 783 ms |
| Oct 17, 2026 | 789 ms |
| Oct 24, 2026 | 778 ms |
| Oct 31, 2026 | 732 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 70 ms |
| May 23, 2026 | 70 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 73 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 69 ms |
| Aug 15, 2026 | 69 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 73 ms |
| Oct 24, 2026 | 73 ms |
| Oct 31, 2026 | 71 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
Reduce unused JavaScript
6.5 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 6.5 s faster on a phone.
Improve image delivery
3.0 s · 953 KiB7 images could be 953 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 310 KiB14 files are served with short cache lifetimes, so returning visitors download them again (310 KiB).
Mobile performance score: 39
39/100Your mobile performance score is 39. 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 (YouTube, Shopify and Google Tag Manager and others), adding 2.6 MB and 1.1 s of main-thread time.
Reduce unused CSS
960 ms · 199 KiBAbout 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 960 ms faster on a phone.
YouTube adds 478 ms
478 msYouTube costs a phone 478 ms of main-thread work and 991 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
450 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 293 ms
293 msShopify costs a phone 293 ms of main-thread work and 910 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.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.7 s
27.7 sYour largest element takes 27.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.0 s
28.0 sThe page becomes fully interactive after 28.0 s. Good is under 3.8 s.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 445 ms
445 msScripts block taps and scrolling for 445 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.144
0.144The layout shifts by 0.144 while loading, so content jumps under the reader's thumb. Good is under 0.1.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 70 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 91 ms
91 msReal visitors wait 91 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 401 ms
401 msReal visitors wait 401 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.5 MB in 424 requests
6.5 MBYour homepage downloads 6.5 MB in 424 requests on a phone: scripts 2.5 MB (150), images 2.1 MB (61) and other files 982 KiB (175). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
dormie_collections_blue.jpg weighs 655 KiB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
dormie_collections_blue.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (1,022 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.
1 image far larger than shown
371 KiB1 image is downloaded at several times the size a phone draws it, for example dormie_collections_blue.jpg at 1,667 px wide, shown at 366 px. Resized copies would save about 371 KiB.
About 1.8 g of CO₂ per visit
1.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
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.
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.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 3 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.
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Dormie Workshop | Premium Leather Golf Headcovers – Dormie Workshop Canada”.
Canonical points to another host
Your canonical URL points to dormieworkshop.com, not ca.dormieworkshop.com, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
14 links crawlers can't follow
14 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
90 internal links, 3 external
The homepage links to 90 pages on dormieworkshop.ca and 3 external pages.
4 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Handcrafted leather golf headcovers made by artisans in Halifax, Canada. Custom designs available. Shop the collection.”.
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://dormieworkshop.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 (601 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ca.dormieworkshop.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 broken image
1 image failed to load on a phone, for example https://placehold.it/40x40.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.
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 427 words of copy
The homepage carries about 427 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”.
12 calls to action
The homepage has 12 calls to action, for example “Shop All”, “Custom Shop” and “Go to the shop”.
7 short forms
7 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
35 other companies contacted
Loading the homepage contacts 35 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 dormieworkshop.ca, 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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Klaviyo Email Marketing Sms · Redo · Inbox · Restockrocket · Easify Product Options · Geolocation Markets Selector · shiptection.com · good-apps.co · instant.one
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
- The footer still says © 2023.
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- 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 dormieworkshop.ca, including 18 speed issues, 6 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.