Website review, no card needed
diamondsdirect.ca website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 78 checks
This review found 42 issues worth fixing on diamondsdirect.ca, 13 of them high impact, across 78 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
69D- #104,269 of 121,500 reviewed websitesbeats 12%
- #63,062 of 68,739 online storesbeats 7%
- #58,262 of 62,636 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Aug 22, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 105 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 97 ms |
| Sep 5, 2026 | 78 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.9 s
1.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.5 s
7.5 s
Speed
Reduce unused JavaScript
2.6 s · 457 KiBAbout 457 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.0 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 (logoshowcase.co, Google Tag Manager and Vimeo and others), adding 8.1 MB and 909 ms of main-thread time.
Use efficient cache lifetimes
400 ms · 647 KiB36 files are served with short cache lifetimes, so returning visitors download them again (647 KiB).
Vimeo adds 150 ms
150 msVimeo costs a phone 150 ms of main-thread work and 7.5 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
590 ms · 112 KiBAbout 112 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.
Improve image delivery
336 KiB5 images could be 336 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
2,105 HTML elements
The page has 2,105 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
60 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
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.
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
First Contentful Paint: 9.6 s
9.6 sThe first text or image appears after 9.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 25.7 s
25.7 sThe page becomes fully interactive after 25.7 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 567 ms
567 msScripts block taps and scrolling for 567 ms in total while the page loads. Good is under 200 ms.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.4 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: 12.0 MB in 307 requests
12.0 MBYour homepage downloads 12.0 MB in 307 requests on a phone: other files 7.9 MB (175), scripts 2.7 MB (89) and images 849 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
35 KiB1 image is downloaded at several times the size a phone draws it, for example Front___Shadowless.png at 660 px wide, shown at 121 px. Resized copies would save about 35 KiB.
1 image below the first screen load straight away
1 image further down the page (51 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.4 g of CO₂ per visit
3.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.41 g of CO₂e: 409.3 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
Images must have alternative text (2 elements)
Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “Diamonds Direct® DiamondsDirect.ca - Diamonds & Jewellery in Canada – DIAMONDS DIRECT®”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “Goodbye Markups.Hello Diamonds.”). One clear main headline is easier for people and search engines.
Meta description is long (308 characters)
Your meta description is 308 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.
36 internal links, 18 external
The homepage links to 36 pages on diamondsdirect.ca and 18 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://diamondsdirect.ca/.
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://diamondsdirect.ca/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 (467 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://diamondsdirect.ca/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://diamondsdirect.ca/pages/terms-of-service and https://diamondsdirect.ca/pages/privacy-policy, which answer with an error. Visitors hit a dead end and search engines drop them.
1 linked page hidden from search
https://diamondsdirect.ca/pages/training is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
9 pages without a meta description
https://diamondsdirect.ca/collections/engagement-ring, https://diamondsdirect.ca/pages/diamonds-engagement, https://diamondsdirect.ca/pages/showrooms, https://diamondsdirect.ca/pages/testimonials, https://diamondsdirect.ca/collections/earrings and https://diamondsdirect.ca/collections/necklaces and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://diamondsdirect.ca/collections/engagement-ring, https://diamondsdirect.ca/pages/testimonials, https://diamondsdirect.ca/collections/earrings, https://diamondsdirect.ca/collections/necklaces, https://diamondsdirect.ca/collections/bracelets and https://diamondsdirect.ca/pages/training have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
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.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.calendly.com/assets/external/widget.css' from origin 'https://diamondsdirec…”.
Missing source maps
Large scripts ship without source maps.
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 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: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 351 words of copy
The homepage carries about 351 words of visible text.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Shop Engagement Rings”, “Shop Diamonds” and “Book An Appointment”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 2 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.
42 other companies contacted
Loading the homepage contacts 42 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 diamondsdirect.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Clipara Shoppable Videos · Beast Currency Converter · klaviyo.com · testimonialhub.com · elfsight.com · covet.pics · nice-team.net · powr.io · logoshowcase.co · nfcube.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on diamondsdirect.ca, including 17 speed issues, 5 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.