owdencraft.com website review

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

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

72 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Shopify and tidio.co and others), adding 17.4 MB and 965 ms of main-thread time.

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

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

About 761 KiB of JavaScript is downloaded but never used on this page.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

YouTube costs a phone 528 ms of main-thread work and 992 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.

tidio.co costs a phone 105 ms of main-thread work and 517 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.

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

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

About 128 KiB of CSS is downloaded but never applied on this page.

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

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “jewelry分类.jpg__PID:5bb73fca-7b61-4041-baaa-8f82576de241”.

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

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

Scripts block taps and scrolling for 351 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 97 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

Your homepage downloads 24.4 MB in 646 requests on a phone: media 14.9 MB (4), images 6.0 MB (348) and scripts 1.9 MB (87). Under 2 MB keeps phones on slow connections fast.

35 images are downloaded at several times the size a phone draws them, for example 8_740e3eb2-6e91-41b3-aca1-71117a5ef32a.jpg at 2,480 px wide, shown at 176 px. Resized copies would save about 2.1 MB.

10 images further down the page (995 KiB) 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.92 g of CO₂e: 830.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

Your <h1> is empty.

The homepage links to 51 pages on owdencraft.com and 5 external pages.

There is no https://www.owdencraft.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://www.owdencraft.com/collections/hammers, https://www.owdencraft.com/collections/measuring-tools, https://www.owdencraft.com/collections/tool-storage, https://www.owdencraft.com/collections/metal-stamps-art-font, https://www.owdencraft.com/collections/metal-stamps-kits and https://www.owdencraft.com/collections/stamping-blanks-bending-bar have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.owdencraft.com/collections/burnishing-edge-finishing-tools, https://www.owdencraft.com/collections/cutting-tools, https://www.owdencraft.com/collections/hammers, https://www.owdencraft.com/collections/punches, https://www.owdencraft.com/collections/stitching-lacing-tools and https://www.owdencraft.com/collections/stamping-carving and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0575/2566/5976/t/17/assets/1669359145845-1669359188599.png?v=1669359195.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 410 words of visible text.

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

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