Website review, no card needed

zeald.com logo

zeald.com website review

Visit site (opens in a new tab)Reviewed 23 October 202621 issues · 61 checks

This review found 21 issues worth fixing on zeald.com, 3 of them high impact, across 61 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.3 s1.8 sJun 27Jul 182.1 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20261.9 s
Jul 18, 20262.1 s

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 zeald.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix73
  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    600 ms · 1.2 MB

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

  • Mobile performance score: 73

    73/100

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

  • Improve image delivery

    150 ms · 642 KiB

    29 images could be 642 KiB 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.

  • Legacy JavaScript

    200 ms · 7 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cloudflare CDN, Google/Doubleclick Ads and alliai.com and others), adding 110 KiB and 110 ms of main-thread time.

  • Reduce unused CSS

    23 KiB

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

  • Reduce unused JavaScript

    23 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 202 ms

    202 ms

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

Core Web Vitals

5 to fix72
  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner-1011-111”.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Time to Interactive: 5.9 s

    5.9 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • 16 images without width and height

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

3 checks passed
  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.42 g

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

1 checks passed
  • Page weight: 1.5 MB in 96 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 96 requests on a phone: images 1.2 MB (55), scripts 129 KiB (16) and stylesheets 58 KiB (12). That is a lean page.

Accessibility

2 to fix88
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

SEO

5 to fixGoogle 9281
  • 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 (69 characters)

    Your meta description is only 69 characters: “We specialise in the rapid digital transformation of Kiwi businesses.”. 70 to 160 characters is enough to sell the click.

  • 13 H1 headlines

    There are 13 <h1> headlines (“NZ’s largest and most experienced digital transfo…”, “Since 2001, we have digitally transformed over 15…” and “How we can help”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links with vague text

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

  • No X (Twitter) card tag

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

  • 51 internal links, 17 external

    The homepage links to 51 pages on zeald.com and 17 external pages.

4 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “NZ's most experienced web design & digital marketing agency”.

  • Canonical URL set

    The canonical URL is https://www.zeald.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 http://www.zeald.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.zeald.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.

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

Other pages

2 to fix70
  • 3 linked pages are broken

    Your homepage links to https://www.zeald.com/resources/webinarlibrary.html, https://www.zeald.com/resources/business-insights.html and https://www.zeald.com/our-work.html, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://www.zeald.com/services.html has 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 35 found) and read each the way a search engine does.

5 checks passed
  • 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 7788
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 10 console errors

    10 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 1,120 words of copy

    The homepage carries about 1,120 words of visible text.

5 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact”, “Login / Register” and “Learn More”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 29 customer or partner logos, 1 trust badge and “15k businesses”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on zeald.com, including 9 speed issues and 5 SEO issues. 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