Website review, no card needed

walcom.shop logo

walcom.shop website review

Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 81 checks

This review found 35 issues worth fixing on walcom.shop, 12 of them high impact, across 81 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

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 22, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
127 ms109 msMay 16Oct 31113 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026125 ms
Jun 13, 2026111 ms
Jul 11, 2026117 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Sep 26, 2026120 ms
Oct 3, 2026114 ms
Oct 10, 2026112 ms
Oct 17, 2026113 ms
Oct 31, 2026113 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 walcom.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. walcom.shop at 0.8 s0.8 s
  2. walcom.shop at 1.6 s1.6 s
  3. walcom.shop at 2.5 s2.5 s
  4. walcom.shop at 3.3 s3.3 s
  5. walcom.shop at 4.1 s4.1 s
  6. walcom.shop at 4.9 s4.9 s
  7. walcom.shop at 5.7 s5.7 s
  8. walcom.shop at 6.5 s6.5 s

Speed

9 to fix71
  • Render-blocking requests

    1.4 s

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

  • 5,900 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    790 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Shopify and shop.app and others), adding 1.9 MB and 466 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 190 KiB

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

  • YouTube adds 303 ms

    303 ms

    YouTube costs a phone 303 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.

  • Main-thread work: 2.9 s

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

  • Shopify adds 147 ms

    147 ms

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

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    26 KiB

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

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

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 14.1 s

    14.1 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

9 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.5 s

    1.5 s

    Real visitors wait 1.5 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 475 ms

    475 ms

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

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

    -17%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 454 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 454 requests on a phone: scripts 1.8 MB (190), other files 1,006 KiB (182) and images 640 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.16 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.6 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

11 to fixGoogle 8388
  • Invalid ARIA attributes

    5 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • 2 text elements with low contrast

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

  • 17 images without alt text

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (255 characters)

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

  • 219 internal links, 1 external

    The homepage links to 219 pages on walcom.shop and 1 external page.

7 checks passed
  • One H1 headline

    Your main headline reads: “Walcom Shop”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Walcom official authorized shop – Walcom Shop”.

  • Canonical URL set

    The canonical URL is https://usa.walcom.shop/.

  • Structured data in place

    Structured data found: Organization.

  • 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://usa.walcom.shop/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

    The site publishes https://usa.walcom.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 14 pages without a meta description

    https://usa.walcom.shop/collections/genesi-carbonio-360-evo, https://usa.walcom.shop/collections/genesi-carbonio/standard-edition, https://usa.walcom.shop/collections/genesi-carbonio-360-evo/special-edition, https://usa.walcom.shop/collections/gravity-cups/genesi-carbonio-360-evo, https://usa.walcom.shop/collections/nozzle-set/genesi-carbonio-360-evo and https://usa.walcom.shop/collections/parts/genesi-carbonio-360-evo and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://usa.walcom.shop/collections/adapters/genesi-carbonio, whose canonical is https://usa.walcom.shop/collections/adapters. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://usa.walcom.shop/collections/genesi-carbonio-360-evo, https://usa.walcom.shop/collections/genesi-carbonio/standard-edition, https://usa.walcom.shop/collections/genesi-carbonio-360-evo/special-edition, https://usa.walcom.shop/collections/gravity-cups/genesi-carbonio-360-evo, https://usa.walcom.shop/collections/nozzle-set/genesi-carbonio-360-evo and https://usa.walcom.shop/collections/parts/genesi-carbonio-360-evo and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7397
  • 5 third-party cookies

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

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    19 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

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

  • Only about 104 words

    The homepage has only about 104 words of visible text; thin pages give Google and first-time buyers little to go on.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Walcom Shop”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Walcom Shop”.

  • 2 short forms

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

  • 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
  • 4 trackers load before any consent

    4

    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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 walcom.shop, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Forms

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 35 issues on walcom.shop, including 12 speed issues, 1 SEO issue and 4 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