Website review, no card needed

growyze.com logo

growyze.com website review

Visit site (opens in a new tab)Reviewed 21 November 202633 issues · 79 checks

This review found 33 issues worth fixing on growyze.com, 11 of them high impact, across 79 checks. The most urgent: google Tag Manager adds 1.0 s. 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 growyze.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. growyze.com at 0.8 s0.8 s
  2. growyze.com at 1.7 s1.7 s
  3. growyze.com at 2.5 s2.5 s
  4. growyze.com at 3.4 s3.4 s
  5. growyze.com at 4.2 s4.2 s
  6. growyze.com at 5.1 s5.1 s
  7. growyze.com at 5.9 s5.9 s
  8. growyze.com at 6.7 s6.7 s

Speed

12 to fix48
  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 877 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 6.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and zohocdn.com and others), adding 5.3 MB and 3.3 s of main-thread time.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • website-files.com adds 581 ms

    581 ms

    website-files.com costs a phone 581 ms of main-thread work and 2.5 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.

  • zohocdn.com adds 418 ms

    418 ms

    zohocdn.com costs a phone 418 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.

  • Improve image delivery

    459 KiB

    16 images could be 459 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Hotjar adds 352 ms

    352 ms

    Hotjar costs a phone 352 ms of main-thread work and 65 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.

  • 20 long tasks on the main thread

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

  • zohopublic.eu adds 318 ms

    318 ms

    zohopublic.eu costs a phone 318 ms of main-thread work and 107 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.

  • 1,645 HTML elements

    The page has 1,645 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Font display

    250 ms

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

  • Render-blocking requests

    250 ms

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

  • Use efficient cache lifetimes

    242 KiB

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

  • Reduce unused CSS

    44 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

    5 ms

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

Core Web Vitals

6 to fix57
  • Time to Interactive: 29.9 s

    29.9 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Protect your margin across purchasing, invoices & stock”. Most of its time is element render delay (1.4 s).

  • 14 images without width and height

    14 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.075

    0.075

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

Images and page weight

2 to fix60
  • Page weight: 5.4 MB in 156 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 156 requests on a phone: scripts 2.5 MB (52), fonts 1.5 MB (7) and images 969 KiB (52). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    121 KiB

    1 image is downloaded at several times the size a phone draws it, for example 67d1a66c5afb2581396124ba_Ibis_Budget_Logo_2011.png at 500 px wide, shown at 64 px. Resized copies would save about 121 KiB.

  • 2 images in older formats

    2 images (277 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.

  • About 1.5 g of CO₂ per visit

    1.54 g

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

1 checks passed
  • Images load when needed

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

Accessibility

6 to fixGoogle 8992
  • 3 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 9 links without text

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

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 376 images in the HTML carry an alt attribute.

  • 42 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: 42 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

2 to fixGoogle 10089
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Hospitality Stock, Purchasing & Invoice Control Software | growyze”.

  • Structured data has 1 problem

    Structured data found (Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 74 internal links, 21 external

    The homepage links to 74 pages on growyze.com and 21 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “growyze connects purchasing, deliveries, supplier invoices and stocktakes, so hospitality operators see what they order…”.

  • One H1 headline

    Your main headline reads: “Protect your margin across purchasing, invoices & stock”.

  • Canonical URL set

    The canonical URL is https://www.growyze.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.growyze.com/sitemap.xml.

AI search readiness

100
4 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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.growyze.com/llms.txt (3 KiB, 2 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix68
  • 1 linked page is broken

    Your homepage links to https://www.growyze.com/partners, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.growyze.com/pricing is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 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.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

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

2 checks passed
  • 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
  • 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 971 words of copy

    The homepage carries about 971 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 Demo”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Pricing”, “Contact” and “Try for Free”.

  • 4 short forms

    4 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 64 testimonial or review blocks, 270 customer or partner logos and 2 trust badges.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 growyze.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 | Hotjar
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on growyze.com, including 18 speed issues, 2 SEO issues 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