Website review, no card needed

zamboni.com logo

zamboni.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 76 checks

This review found 32 issues worth fixing on zamboni.com, 11 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
3.7 s2.8 sApr 25Oct 102.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.9 s
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.4 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
93 ms77 msApr 25Oct 1082 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202679 ms
May 2, 202680 ms
May 9, 202684 ms
May 16, 202688 ms
May 23, 202688 ms
May 30, 202689 ms
Jun 6, 202689 ms
Jun 13, 202687 ms
Jun 20, 202689 ms
Jun 27, 202689 ms
Jul 4, 202691 ms
Jul 11, 202690 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 8, 202684 ms
Aug 15, 202684 ms
Aug 22, 202687 ms
Aug 29, 202683 ms
Sep 5, 202685 ms
Sep 12, 202685 ms
Sep 19, 202682 ms
Sep 26, 202682 ms
Oct 3, 202682 ms
Oct 10, 202682 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 zamboni.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zamboni.com at 0.4 s0.4 s
  2. zamboni.com at 0.8 s0.8 s
  3. zamboni.com at 1.3 s1.3 s
  4. zamboni.com at 1.7 s1.7 s
  5. zamboni.com at 2.1 s2.1 s
  6. zamboni.com at 2.5 s2.5 s
  7. zamboni.com at 2.9 s2.9 s
  8. zamboni.com at 3.4 s3.4 s

Speed

8 to fix57
  • Use efficient cache lifetimes

    15.5 s · 2.7 MB

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

  • Reduce unused JavaScript

    4.7 s · 486 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    550 ms · 81 KiB

    1 image could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 465 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Google CDN adds 284 ms

    284 ms

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

  • Reduce unused CSS

    300 ms · 48 KiB

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

  • Font display

    150 ms

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

  • 5 long tasks on the main thread

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 700 ms of it running JavaScript. That is comfortably low.

  • Server response: 31 ms

    31 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user CLS: 0.85

    0.85

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

  • First Contentful Paint: 8.0 s

    8.0 s

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

  • Largest Contentful Paint: 22.6 s

    22.6 s

    Your largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text ““THE PRINCIPAL PRODUCT YOU HAVE TO SELL IS THE ICE ITSELF.”…”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

3 checks passed
  • Real-user INP: 85 ms

    85 ms

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

  • Total Blocking Time: 79 ms

    79 ms

    Scripts block the page for only 79 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

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

    4.1 MB

    Your homepage downloads 4.1 MB in 65 requests on a phone: images 2.6 MB (24), scripts 1.0 MB (22) and other files 351 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.17 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

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

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

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

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

  • Meta description is short (26 characters)

    Your meta description is only 26 characters: “Nothing else is even close”. 70 to 160 characters is enough to sell the click.

  • 84 internal links, 8 external

    The homepage links to 84 pages on zamboni.com and 8 external pages.

5 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Zamboni | Nothing else is even close”.

  • Canonical URL set

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

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

  • XML sitemap found

    Your XML sitemap is reachable at https://zamboni.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://zamboni.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 (384 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 12 pages without a meta description

    https://zamboni.com/options, https://zamboni.com/owners/zamboni-authentic-parts, https://zamboni.com/used-products, https://zamboni.com/resources, https://zamboni.com/new-owner and https://zamboni.com/bootcamp and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://zamboni.com/new-owner, https://zamboni.com/air-quality-and-emissions and https://zamboni.com/circle-check took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 14 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 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 305 words of copy

    The homepage carries about 305 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: “Download QR Code”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Gear / Shop” and “Shop”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

Company

Founded
1950
Headquarters
Paramount

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 zamboni.com, including 17 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