Website review, no card needed
besttools.net website review
Visit site (opens in a new tab)Reviewed 18 October 202645 issues · 91 checks
This review found 45 issues worth fixing on besttools.net, 15 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
70C- #98,292 of 117,615 reviewed websitesbeats 14%
- #60,175 of 66,923 online storesbeats 8%
- #55,783 of 61,018 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.1 s
5.8 s
Speed
Render-blocking requests
3.4 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
3,988 HTML elements
The page has 3,988 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
750 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Shopify and Facebook and others), adding 1.9 MB and 942 ms of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 237 KiBAbout 237 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
YouTube adds 430 ms
430 msYouTube costs a phone 430 ms of main-thread work and 967 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
200 ms · 295 KiB12 images could be 295 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
450 KiB25 files are served with short cache lifetimes, so returning visitors download them again (450 KiB).
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 167 ms
167 msShopify costs a phone 167 ms of main-thread work and 319 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.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 127 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).
Legacy JavaScript
41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SUPPORTING OUR FIRST RESPONDERS. VIEW LIGHTS >”.
Time to Interactive: 28.6 s
28.6 sThe page becomes fully interactive after 28.6 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 264 ms
264 msScripts block taps and scrolling for 264 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 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.038
0.038The layout barely moves while loading (CLS 0.038, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 313 requests
5.7 MBYour homepage downloads 5.7 MB in 313 requests on a phone: scripts 2.5 MB (75), images 1.7 MB (52) and other files 854 KiB (158). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (250 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (32 KiB) is 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.
About 1.6 g of CO₂ per visit
1.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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 (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 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.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
41 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: 41 passed and 14 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 (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Manufacturer of Lockout Tools - Supplier of Towing & Truck Equipment”.
Structured data has 2 problems
Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
43 internal links, 6 external
The homepage links to 43 pages on besttools.net and 6 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “We offer our brand of USA Made Lockout Tools, Lockout Kits, & Supply Truck Accessories, Towing Equipment, Emergency Lig…”.
Canonical URL set
The canonical URL is https://besttoolsusa.com/.
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://besttoolsusa.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,568 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://besttoolsusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://besttoolsusa.com/collections/lights and https://besttoolsusa.com/pages/lights all use the title “Lights”. Search engines can't tell which page to show for a search, so each competes with the others.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://besttoolsusa.com/collections/product-spotlight/products/2-pack-heavy-duty-container-chain-bridle-hooks-with-connecting-links-replacement-shipping-container-hooks-for-loading-transport-easy-installation, whose canonical is https://besttoolsusa.com/products/2-pack-heavy-duty-container-chain-bridle-hooks-with-connecting-links-replacement-shipping-container-hooks-for-loading-transport-easy-installation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages with very little text
https://besttoolsusa.com/pages/lights and https://besttoolsusa.com/pages/calendar-of-events 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 23 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 31 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.
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.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 265 words of copy
The homepage carries about 265 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”.
3 calls to action
The homepage has 3 calls to action, for example “Shop Now”, “Contact Us” and “Subscribe”.
9 short forms
9 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
47 other companies contacted
Loading the homepage contacts 47 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 besttools.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on besttools.net, including 17 speed issues, 5 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.