Programmable

Website review, no card needed

zesty.co logo

zesty.co website review

Visit site (opens in a new tab)Reviewed 2 November 202620 issues · 69 checks

This review found 20 issues worth fixing on zesty.co, 7 of them high impact, across 69 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

Site score

84B

Closest competitors among SaaS websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.8 s3.8 sMay 16Oct 314.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.5 s
May 23, 20264.5 s
May 30, 20264.6 s
Jun 6, 20264.7 s
Jun 13, 20264.7 s
Jun 20, 20265.1 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20265.2 s
Jul 18, 20264.9 s
Jul 25, 20265.4 s
Aug 1, 20265.6 s
Aug 8, 20265.6 s
Aug 15, 20265.5 s
Aug 22, 20265.1 s
Aug 29, 20264.5 s
Sep 5, 20264.4 s
Sep 12, 20264.2 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.1 s
Oct 24, 20264.5 s
Oct 31, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
404 ms118 msMay 16Oct 31245 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026151 ms
May 23, 2026154 ms
May 30, 2026157 ms
Jun 6, 2026157 ms
Jun 13, 2026166 ms
Jun 20, 2026189 ms
Jun 27, 2026236 ms
Jul 4, 2026297 ms
Jul 11, 2026344 ms
Jul 18, 2026340 ms
Jul 25, 2026371 ms
Aug 1, 2026310 ms
Aug 8, 2026261 ms
Aug 15, 2026209 ms
Aug 22, 2026176 ms
Aug 29, 2026186 ms
Sep 5, 2026273 ms
Sep 12, 2026297 ms
Sep 19, 2026296 ms
Sep 26, 2026296 ms
Oct 3, 2026178 ms
Oct 10, 2026183 ms
Oct 17, 2026193 ms
Oct 24, 2026235 ms
Oct 31, 2026245 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

zesty.co (opens in a new tab)
Full-page screenshot of zesty.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zesty.co at 0.7 s0.7 s
  2. zesty.co at 1.3 s1.3 s
  3. zesty.co at 2.0 s2.0 s
  4. zesty.co at 2.7 s2.7 s
  5. zesty.co at 3.4 s3.4 s
  6. zesty.co at 4.0 s4.0 s
  7. zesty.co at 4.7 s4.7 s
  8. zesty.co at 5.4 s5.4 s

Speed

3 to fix75

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 75

    75/100

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

  • Main-thread work: 2.6 s

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

  • Reduce unused CSS

    150 ms · 37 KiB

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

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 177 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.

  • 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: 38 ms

    38 ms

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

Core Web Vitals

8 to fix50

  • 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 LCP: 5.5 s

    5.5 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Total Blocking Time: 760 ms

    760 ms

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

  • Tap response (INP) got 57% slower for real visitors

    +57%

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Continuously optimize compute and GPU resources to match re…”. Most of its time is element render delay (4.3 s).

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed

  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Time to Interactive: 2.8 s

    2.8 s

    The page is fully interactive after 2.8 s.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • 1 image in older formats

    1 image (69 KiB) is 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.

  • About 0.10 g of CO₂ per visit

    0.10 g

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

3 checks passed

  • Page weight: 356 KiB in 44 requests

    356 KiB

    Your homepage downloads 356 KiB in 44 requests on a phone: fonts 115 KiB (3), stylesheets 103 KiB (26) and images 92 KiB (13). That is a lean page.

  • 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

6 to fixGoogle 9291

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 36 links without text

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298

  • 3 links with vague text

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

  • 72 internal links, 10 external

    The homepage links to 72 pages on zesty.co and 10 external pages.

8 checks passed

  • Meta description: 148 characters

    Your meta description is 148 characters: “Zesty helps companies reduce Kubernetes infrastructure costs through autonomous resource optimization, without compromi…”.

  • One H1 headline

    Your main headline reads: “Autonomous Kubernetes Optimization”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Zesty | Autonomous Kubernetes Optimization Platform”.

  • Canonical URL set

    The canonical URL is https://zesty.co/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://zesty.co/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://zesty.co/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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

1 to fix95

  • 2 pages without a meta description

    https://zesty.co/cost-efficiency-calculator and https://zesty.co/finops-academy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://zesty.co/platform/azure-commitment-optimization, https://zesty.co/cost-efficiency-calculator and https://zesty.co/finops-academy took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

Best practices

Google 100100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92

  • Only about 116 words

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

  • No form on the homepage

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

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

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK A DEMO”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Sales”, “Pricing” and “Book a Demo”.

  • Social proof on the page

    Social proof on the homepage: 11 customer or partner logos and 3 trust badges.

  • 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

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 zesty.co, 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 Tag Manager
Hosting
Google Cloud

Company

Employees
120
Headquarters
Vallejo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on zesty.co, including 11 speed issues, 1 SEO issue and 1 conversion gap. 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