Website review, no card needed

icowhide.com logo

icowhide.com website review

Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 83 checks

This review found 32 issues worth fixing on icowhide.com, 11 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.9 s772 msMay 30Nov 141.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 2026988 ms
Oct 3, 2026907 ms
Oct 10, 2026966 ms
Oct 17, 2026967 ms
Oct 24, 2026959 ms
Oct 31, 2026998 ms
Nov 7, 20261.0 s
Nov 14, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
301 ms78 msMay 30Nov 14114 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026272 ms
Jun 6, 2026254 ms
Jun 13, 2026271 ms
Jun 20, 2026275 ms
Jun 27, 2026264 ms
Jul 4, 2026263 ms
Jul 11, 2026256 ms
Jul 18, 2026248 ms
Jul 25, 2026264 ms
Aug 1, 2026171 ms
Aug 8, 2026136 ms
Aug 15, 2026121 ms
Aug 22, 2026114 ms
Aug 29, 2026119 ms
Sep 5, 2026119 ms
Sep 12, 2026120 ms
Sep 19, 2026116 ms
Sep 26, 2026113 ms
Oct 3, 2026109 ms
Oct 10, 2026105 ms
Oct 17, 2026105 ms
Oct 24, 2026104 ms
Oct 31, 2026112 ms
Nov 7, 2026113 ms
Nov 14, 2026114 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of icowhide.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. icowhide.com at 0.6 s0.6 s
  2. icowhide.com at 1.2 s1.2 s
  3. icowhide.com at 1.8 s1.8 s
  4. icowhide.com at 2.4 s2.4 s
  5. icowhide.com at 3.0 s3.0 s
  6. icowhide.com at 3.6 s3.6 s
  7. icowhide.com at 4.2 s4.2 s
  8. icowhide.com at 4.8 s4.8 s

Speed

10 to fix59
  • Reduce unused JavaScript

    1.8 s · 469 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 274 KiB

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

  • Improve image delivery

    1.2 s · 429 KiB

    17 images could be 429 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • 4,106 HTML elements

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

  • Mobile performance score: 59

    59/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vitals.app, Affirm and tidio.co and others), adding 1.5 MB and 447 ms of main-thread time.

  • Legacy JavaScript

    300 ms · 35 KiB

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

  • Main-thread work: 2.0 s

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

  • vitals.app adds 128 ms

    128 ms

    vitals.app costs a phone 128 ms of main-thread work and 408 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 adds 68 ms

    68 ms

    tidio.co costs a phone 68 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.

  • Render-blocking requests

    200 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    20 ms · 17 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Time to Interactive: 16.8 s

    16.8 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • 30 images without width and height

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 114 ms

    114 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 349 ms

    349 ms

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

  • Tap response (INP) got 57% faster for real visitors

    -57%

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

  • Largest content (LCP) got 43% faster for real visitors

    -43%

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

  • Total Blocking Time: 122 ms

    122 ms

    Scripts block the page for only 122 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix76
  • Page weight: 3.8 MB in 264 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 264 requests on a phone: scripts 1.4 MB (94), images 1.2 MB (34) and other files 708 KiB (90). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    045.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 12 images below the first screen load straight away

    12 images further down the page (349 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.07 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9291
  • 26 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (156 elements)

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

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 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.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9287
  • Meta description is long (199 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 108 internal links, 1 external

    The homepage links to 108 pages on icowhide.com and 1 external page.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Best Cowhide and Sheepskin Rugs for Sale – iCowhide”.

  • Canonical URL set

    The canonical URL is https://icowhide.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://icowhide.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,666 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://icowhide.com/collections/sheepskin-rugs and https://icowhide.com/pages/get-inspired have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • 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 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    28 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • No analytics detected

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

  • No direct contact details

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

  • About 1,394 words of copy

    The homepage carries about 1,394 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”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact” and “SHOP NOW”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Klaviyo, Meta Pixel and Reddit 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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 3 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 icowhide.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Scrolly Infinite Scroll · Cartix · Vitals · Easylocation · Klaviyo Email Marketing · tidio.co · ywxi.net · covet.pics · chimpstatic.com · getscrolly.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on icowhide.com, including 15 speed issues, 3 SEO issues and 2 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25