Website review, no card needed

zammodigital.com logo

zammodigital.com website review

Visit site (opens in a new tab)Reviewed 11 November 202642 issues · 82 checks

This review found 42 issues worth fixing on zammodigital.com, 11 of them high impact, across 82 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

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

How it loaded on a phone

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

Speed

11 to fix37
  • Reduce unused JavaScript

    3.8 s · 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 3.8 s faster on a phone.

  • Mobile performance score: 37

    37/100

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

  • 8 third-party services on the page

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

  • Improve image delivery

    150 ms · 1.2 MB

    21 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    900 ms · 387 KiB

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

  • Reduce unused CSS

    540 ms · 145 KiB

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

  • Google Tag Manager adds 585 ms

    585 ms

    Google Tag Manager costs a phone 585 ms of main-thread work and 652 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.

  • YouTube adds 533 ms

    533 ms

    YouTube costs a phone 533 ms of main-thread work and 1,015 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.

  • Webflow adds 238 ms

    238 ms

    Webflow costs a phone 238 ms of main-thread work and 2.3 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.

  • Main-thread work: 3.9 s

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

  • Render-blocking requests

    300 ms

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

  • 19 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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.

1 checks passed
  • Server response: 28 ms

    28 ms

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

Core Web Vitals

6 to fix45
  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Largest Contentful Paint: 19.0 s

    19.0 s

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

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • Total Blocking Time: 809 ms

    809 ms

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

  • 33 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 5.3 MB in 126 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 126 requests on a phone: scripts 2.4 MB (27), images 2.1 MB (52) and fonts 505 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (847 KiB) 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.

  • 6 images below the first screen load straight away

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

  • 1 image far larger than shown

    54 KiB

    1 image is downloaded at several times the size a phone draws it, for example 61676a70cc53958182c6c0ec_-11590303444ezlkboanlo-p-500.png at 390 px wide, shown at 70 px. Resized copies would save about 54 KiB.

  • About 1.5 g of CO₂ per visit

    1.49 g

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

Accessibility

5 to fixGoogle 9092
  • 25 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 10073
  • Title is short (13 characters)

    Your title is only 13 characters: “Zammo Digital”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (267 characters)

    Your meta description is 267 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.

  • No robots.txt

    There is no robots.txt at zammodigital.com/robots.txt, the first file search crawlers ask for.

  • 23 internal links, 10 external

    The homepage links to 23 pages on zammodigital.com and 10 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “We help SaaS & B2B Companies Grow with Paid Ads”.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.zammodigital.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.zammodigital.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 3 pages share a title

    /, https://www.zammodigital.com/faq and https://www.zammodigital.com/contact-us all use the title “Zammo Digital”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.zammodigital.com/about, https://www.zammodigital.com/case-studies, https://www.zammodigital.com/services, https://www.zammodigital.com/resources, https://www.zammodigital.com/faq and https://www.zammodigital.com/contact-us and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.zammodigital.com/typeform has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

4 to fixGoogle 6571
  • 5 broken images

    5 images failed to load on a phone, for example https://assets-global.website-files.com/603320d897754ad85834ef5b/616f5126eee9f2ee7c3f80d1_Image%202-01-01-p-500.jpeg.

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Clearbit: Please migrate to the new script. See https://grow.clearbit.com/migrate”.

  • 1 distorted image

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

  • 1 low-resolution image

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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 opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 908 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: “Book a Free Discovery Call”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Book a Free Strategy Call”, “Book a Free Discovery Call” and “Schedule a FREE Strategy Session”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 16 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 4 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 zammodigital.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
Webflow
Analytics
Google Tag Manager
Hosting
Webflow

Hiring

Hiring
4 open roles
Job board
careers page

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on zammodigital.com, including 17 speed issues, 6 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