Website review, no card needed

wilcoimaging.com logo

wilcoimaging.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 89 checks

This review found 34 issues worth fixing on wilcoimaging.com, 10 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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

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

How it loaded on a phone

  1. wilcoimaging.com at 0.4 s0.4 s
  2. wilcoimaging.com at 0.8 s0.8 s
  3. wilcoimaging.com at 1.1 s1.1 s
  4. wilcoimaging.com at 1.5 s1.5 s
  5. wilcoimaging.com at 1.9 s1.9 s
  6. wilcoimaging.com at 2.3 s2.3 s
  7. wilcoimaging.com at 2.6 s2.6 s
  8. wilcoimaging.com at 3.0 s3.0 s

Speed

8 to fix82
  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 4.3 s

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

  • Reduce unused JavaScript

    2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    2.0 MB

    16 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 4.0 MB and 1.3 s of main-thread time.

  • YouTube adds 933 ms

    933 ms

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

  • Mobile performance score: 82

    82/100

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

  • 1,530 HTML elements

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

  • Reduce unused CSS

    164 KiB

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

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    84 KiB

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

  • Legacy JavaScript

    8 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 39.7 s

    39.7 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • 35 images without width and height

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

  • Total Blocking Time: 358 ms

    358 ms

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

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

    1.6 s

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

  • 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: 1.5 s

    1.5 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Select Watec Cameras- In Stock & Limited Time Discounts! Wa…”.

Images and page weight

4 to fix28
  • Page weight: 7.9 MB in 269 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 269 requests on a phone: scripts 3.8 MB (96), images 2.5 MB (42) and other files 740 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    IMX250_-_GLR_-_image1_e333752f-d809-4f6c-89dc-51ff12eaa237.j weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.7 MB

    8 images are downloaded at several times the size a phone draws them, for example IMX250_-_GLR_-_image1_e333752f-d809-4f6c-89dc-51ff12eaa237.j at 3,468 px wide, shown at 200 px. Resized copies would save about 1.7 MB.

  • 8 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.25 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8792
  • 20 text elements with low contrast

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

  • 110 images without alt text

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

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

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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • Meta description is long (283 characters)

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

  • 8 links with vague text

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 144 internal links, 7 external

    The homepage links to 144 pages on wilcoimaging.com and 7 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Wilco Imaging”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Wilco Imaging A Lore Technology Company”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ClothingStore, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

100
  • No llms.txt

    There is no https://wilcoimaging.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://wilcoimaging.com/collections/aida, https://wilcoimaging.com/collections/basler and https://wilcoimaging.com/collections/canon-medical 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 88 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

Best practices

5 to fixGoogle 7367
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=271003333&Ver=2&mid=8d99f024-5eed-4030-ba43-c43c9e82d28c&bo=1&sid=b6593d70d96c11f182f8f9d2619a33c7&vid=b6596c70d96c11f1918abf9efcd481a5&vids=1&msclkid=N&pi=918639831&l.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 5 third-party cookies

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “E.d is not a function”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    83 of 86 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

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

  • About 775 words of copy

    The homepage carries about 775 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “Learn More”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop now”, “Contact” and “Shop Now”.

  • 18 short forms

    18 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 wilcoimaging.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Simprosys Google Shopping Feed · Inbox · Ecomposer Builder · Dr Stacked Discounts · Pagefly Ai Page Builder · Minmaxify Order Limits · Hulk Product Options

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

  • The footer still says © 2021.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
West Sacramento

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on wilcoimaging.com, including 12 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