tecovas.com website review

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

5 third-party services load with your homepage (Shopify, adn.cloud and Adobe TypeKit and others), adding 5.2 MB and 942 ms of main-thread time.

Shopify costs a phone 870 ms of main-thread work and 4.4 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 64. Pages that score under 90 lose visitors before the first paint.

1 file is served with short cache lifetimes, so returning visitors download them again (28 KiB).

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

10 images could be 358 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

sanity.io costs a phone 0 ms of main-thread work and 528 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.

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

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

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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

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.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Real visitors wait 295 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 5.2 MB in 81 requests on a phone: media 4.0 MB (2), images 548 KiB (12) and scripts 456 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

Your title is 79 characters, so Google will cut it off around 60: “Tecovas Cowboy Boots, Work Boots & Western Wear for Men, Women & Kids | Tecovas”.

The homepage links to 206 pages on tecovas.com and 9 external pages.

https://www.tecovas.com/shop, https://www.tecovas.com/shop/c/gifts-for-him, https://www.tecovas.com/shop/c/gifts-for-her, https://www.tecovas.com/shop/c/the-mini-me-shop, https://www.tecovas.com/shop/c/gifts-under-100 and https://www.tecovas.com/shop/c/boot-stuffers and 2 others all use the title “Handmade Boots from Classic Western Bootmakers | Tecovas | Tecovas”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tecovas.com/shop, https://www.tecovas.com/shop/c/gifts-for-him, https://www.tecovas.com/shop/c/gifts-for-her, https://www.tecovas.com/shop/c/the-mini-me-shop, https://www.tecovas.com/shop/c/gifts-under-100 and https://www.tecovas.com/shop/c/boot-stuffers and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.tecovas.com/shop/c/gift-guide took over 3 s to send its HTML from our server.

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

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.

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

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.

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.

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