Website review, no card needed

ganz.com logo

ganz.com website review

Visit site (opens in a new tab)Reviewed 26 October 202645 issues · 90 checks

This review found 45 issues worth fixing on ganz.com, 17 of them high impact, across 90 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
1.5 s1.2 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
69 ms59 msMay 9Oct 2466 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202662 ms
May 16, 202663 ms
May 23, 202662 ms
May 30, 202663 ms
Jun 6, 202663 ms
Jun 13, 202663 ms
Jun 20, 202661 ms
Jun 27, 202661 ms
Jul 4, 202660 ms
Jul 11, 202660 ms
Jul 18, 202664 ms
Jul 25, 202663 ms
Aug 1, 202667 ms
Aug 8, 202665 ms
Aug 15, 202664 ms
Aug 22, 202666 ms
Aug 29, 202664 ms
Sep 5, 202663 ms
Sep 12, 202663 ms
Sep 19, 202662 ms
Sep 26, 202662 ms
Oct 3, 202663 ms
Oct 10, 202663 ms
Oct 17, 202668 ms
Oct 24, 202666 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 ganz.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ganz.com at 0.5 s0.5 s
  2. ganz.com at 1.0 s1.0 s
  3. ganz.com at 1.5 s1.5 s
  4. ganz.com at 2.1 s2.1 s
  5. ganz.com at 2.6 s2.6 s
  6. ganz.com at 3.1 s3.1 s
  7. ganz.com at 3.6 s3.6 s
  8. ganz.com at 4.1 s4.1 s

Speed

12 to fix40
  • Render-blocking requests

    7.5 s

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

  • Reduce unused CSS

    4.3 s · 903 KiB

    About 903 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.3 s faster on a phone.

  • Improve image delivery

    2.8 s · 2.2 MB

    32 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    200 ms · 5.5 MB

    139 files are served with short cache lifetimes, so returning visitors download them again (5.5 MB).

  • Reduce unused JavaScript

    450 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

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

  • Google CDN adds 597 ms

    597 ms

    Google CDN costs a phone 597 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    400 ms · 55 KiB

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

  • Google Tag Manager adds 343 ms

    343 ms

    Google Tag Manager costs a phone 343 ms of main-thread work and 474 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: 3.8 s

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

  • LiveChat adds 49 ms

    49 ms

    LiveChat costs a phone 49 ms of main-thread work and 365 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.

  • Font display

    250 ms

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

  • 18 long tasks on the main thread

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

  • Document request latency

    69 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

1 checks passed
  • Server response: 59 ms

    59 ms

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

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 14.4 s

    14.4 s

    Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “mb_cbk2027_lets_eat-10222026.jpg”.

  • Time to Interactive: 30.4 s

    30.4 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Real-user TTFB: 808 ms

    808 ms

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

  • Total Blocking Time: 565 ms

    565 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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: 1.8 s

    1.8 s

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

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

    -13%

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

  • Cumulative Layout Shift: 0.083

    0.083

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

Images and page weight

4 to fix33
  • Page weight: 51.3 MB in 255 requests

    51.3 MB

    Your homepage downloads 51.3 MB in 255 requests on a phone: images 46.6 MB (158), scripts 2.6 MB (59) and stylesheets 952 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    853 KiB

    10 images are downloaded at several times the size a phone draws them, for example h14936.png at 450 px wide, shown at 104 px. Resized copies would save about 853 KiB.

  • 40 images in older formats

    40 images (4.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 18 images below the first screen load straight away

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

  • About 14.5 g of CO₂ per visit

    14.53 g

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

Accessibility

7 to fixGoogle 8091
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 236 internal links, 8 external

    The homepage links to 236 pages on ganz.com and 8 external pages.

5 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Ganz is a gift, home décor, seasonal décor, fashion accessories wholesaler. We offer a wide range of wholesale home dec…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Wholesale Home Décor, Gifts, Home Accents, Seasonal”.

  • Canonical URL set

    The canonical URL is https://www.ganz.com/.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

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.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.ganz.com/Giftware-For-The-Home all use the title “Wholesale Home Décor, Gifts, Home Accents, Seasonal”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.ganz.com/Giftware-For-The-Home has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.ganz.com/new-search-page has 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 88 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.

  • Canonical URLs point to themselves

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

  • 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

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://www.pages03.net/WTS/event.jpeg?accesskey=8cd6821-143bad11661-943e27de0c8b91cc3fcf1475c3e5d726&v=1.31&isNewSession=1&type=pageview&isNewVisitor=1&sessionGUID=a44e221c-946d-cac0-3693-878ebd058ad.

  • 86 small tap targets

    86 of 129 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 third-party cookies

    4 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”).

2 checks passed
  • No console errors

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

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

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

  • No phone number on the homepage

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

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

  • 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 652 words of copy

    The homepage carries about 652 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All” and “SHOP NOW”.

  • 32 calls to action

    The homepage has 32 calls to action, for example “LOGIN / REGISTER”, “Shop All” and “Shop All >”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 5 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.

  • 25 other companies contacted

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

Upkeep, stack and company

Company

Founded
1950
Headquarters
Vaughan

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on ganz.com, including 19 speed issues, 3 SEO issues 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