makitatools.com website review

137 files are served with short cache lifetimes, so returning visitors download them again (20.7 MB).

37 images could be 9.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.

About 781 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.2 s faster on a phone.

About 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.4 MB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 770 ms of main-thread work and 1.1 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.

A phone's processor spends 3.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

14 long tasks block the main thread while loading, the longest for 225 ms. During a long task the page ignores taps.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

11 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 66.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Makita Black Friday promotions: Buy a qualifying LXT combo …”.

The page becomes fully interactive after 71.2 s. Good is under 3.8 s.

The first text or image appears after 5.9 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 684 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 985 ms for your server to start answering (75th percentile). Good is under 800 ms.

6 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.9 MB in 199 requests on a phone: images 20.0 MB (113), scripts 1.7 MB (28) and stylesheets 810 KiB (6). Under 2 MB keeps phones on slow connections fast.

11 images weigh 9.4 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example grt01z-4.webp at 2,312 px wide, shown at 390 px. Resized copies would save about 2.2 MB.

32 images (9.6 MB) 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.

6 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 6.50 g of CO₂e: 779.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 88 characters, so Google will cut it off around 60: “Makita U.S.A | Cordless and Corded Power Tools, Power Equipment, Pneumatics, Accessories”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“BLACK FRIDAY SAVINGS ARE HERE”, “MORE WAYS TO BUILD YOUR MAKTRAK® SYSTEM” and “UP TO 580 FT. LBS. MAX TORQUE”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 521 pages on makitatools.com and 15 external pages.

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.

There is no https://makitatools.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.

/, https://makitatools.com/erebates, https://makitatools.com/promos/BlackFriday, https://makitatools.com/service/directrepair, https://makitatools.com/service/faq and https://makitatools.com/service/technical-documents and 1 other all use the title “Makita U.S.A | Cordless and Corded Power Tools, Power Equipment, Pneu…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://makitatools.com/promos, https://makitatools.com/erebates, https://makitatools.com/get-free-instantly-promos, https://makitatools.com/special-buys, https://makitatools.com/promos/BlackFriday and https://makitatools.com/service/directrepair and 8 others use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 191 found) and read each the way a search engine does.

2 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,169 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel 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.

Opening the homepage sets 16 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.