martineztools.com website review

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

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.5 s faster on a phone.

20 files are served with short cache lifetimes, so returning visitors download them again (926 KiB).

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

8 third-party services load with your homepage (route.com, Google Tag Manager and Shopify and others), adding 2.9 MB and 1.1 s of main-thread time.

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

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

About 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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.

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

Shopify costs a phone 202 ms of main-thread work and 814 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.

route.com costs a phone 224 ms of main-thread work and 542 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.

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

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

rebuyengine.com costs a phone 121 ms of main-thread work and 332 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.

Klaviyo costs a phone 101 ms of main-thread work and 329 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.

14 KiB JavaScript is shipped twice across bundles.

6 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.

Your largest element takes 53.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sign up to win a Murdered Out M1 Framing Hammer ​ But first…”.

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

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

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

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

Your homepage downloads 8.9 MB in 452 requests on a phone: images 3.9 MB (25), scripts 3.2 MB (128) and other files 1.4 MB (249). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

9 visible links have no text or label, so screen readers cannot say where they go.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url is not an absolute URL ("martineztools.myshopify.com")”.

The homepage links to 127 pages on martineztools.com and 7 external pages.

https://martineztools.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://martineztools.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://martineztools.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://martineztools.com/collections/m1-15oz-framing-hammers-use, whose canonical is https://martineztools.com/collections/m1-15oz-framing-hammers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://martineztools.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://martineztools.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

4 images failed to load on a phone, for example https://public-images.judge.me/judgeme/medals-v2-2025-rebranding/ver_rev/gold.svg?auto=format.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

The homepage carries about 563 words of visible text.

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

Opening the homepage sets 26 cookies, 1 of them by other companies (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 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.