Website review, no card needed
duniquetools.com website review
Visit site (opens in a new tab)Reviewed 21 November 202638 issues · 79 checks
This review found 38 issues worth fixing on duniquetools.com, 15 of them high impact, across 79 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
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Reduce unused JavaScript
15.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 15.7 s faster on a phone.
YouTube adds 1.2 s
1.2 sYouTube costs a phone 1.2 s of main-thread work and 2.9 MB 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.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,040 HTML elements
The page has 7,040 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.5 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 (YouTube, loox.io and Klaviyo and others), adding 4.0 MB and 1.9 s of main-thread time.
Reduce unused CSS
930 ms · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 930 ms faster on a phone.
Improve image delivery
420 KiB9 images could be 420 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
loox.io adds 364 ms
364 msloox.io costs a phone 364 ms of main-thread work and 449 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 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 217 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 JavaScript
45 KiB45 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
43 KiB13 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
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
First Contentful Paint: 15.8 s
15.8 sThe first text or image appears after 15.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.9 s
26.9 sYour largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.8 s
15.8 sVisually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 29.4 s
29.4 sThe page becomes fully interactive after 29.4 s. Good is under 3.8 s.
Total Blocking Time: 300 ms
300 msScripts block taps and scrolling for 300 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 283 requests
5.8 MBYour homepage downloads 5.8 MB in 283 requests on a phone: scripts 3.2 MB (89), images 933 KiB (29) and other files 794 KiB (108). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Untitled_design_6_4939f18f-6901-4308-9408-9441b82aa4eb.png 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).
1 image far larger than shown
40 KiB1 image is downloaded at several times the size a phone draws it, for example Untitled_design_6_4939f18f-6901-4308-9408-9441b82aa4eb.png at 1,400 px wide, shown at 390 px. Resized copies would save about 40 KiB.
About 1.6 g of CO₂ per visit
1.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.63 g of CO₂e: 195.6 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
59 text elements with low contrast
59 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
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.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
55 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: 55 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (48 characters)
Your meta description is only 48 characters: “Woodworking Hand Tools Tool Kit Universal Square”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
95 internal links, 15 external
The homepage links to 95 pages on duniquetools.com and 15 external pages.
6 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “Woodworking Hand Tools – D-Unique Tools”.
Canonical URL set
The canonical URL is https://duniquetools.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://duniquetools.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 (3,064 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://duniquetools.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://duniquetools.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://duniquetools.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://duniquetools.com/collections/home-kitchen, https://duniquetools.com/collections/tool-boxes, https://duniquetools.com/collections/universal-tools, https://duniquetools.com/collections/rope, https://duniquetools.com/collections/tool-pouch and https://duniquetools.com/collections/buy-with-prime and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://duniquetools.com/apps/17TRACK, whose canonical is https://duniquetools.com/apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://duniquetools.com/collections, https://duniquetools.com/pages/universal-square-1, https://duniquetools.com/apps/17TRACK, https://duniquetools.com/pages/faq and https://duniquetools.com/customer_authentication/redirect 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 38 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
7 small tap targets
7 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 566 words of copy
The homepage carries about 566 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All” and “Shop Now”.
17 calls to action
The homepage has 17 calls to action, for example “Buy with Prime”, “Track Your Order” and “Contact Us”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks, 3 customer or partner logos, a star rating and 2 trust badges.
Phone number on the homepage
Your phone number is on the homepage.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
22 other companies contacted
Loading the homepage contacts 22 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 duniquetools.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gempages Builder · azureedge.net · nice-team.net · printful.com · klaviyo.com · mailmunch.co · loox.io
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
Company
- Headquarters
- Oakland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on duniquetools.com, including 16 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.