Website review, no card needed

amaze.co logo

amaze.co website review

Visit site (opens in a new tab)Reviewed 19 October 202640 issues · 82 checks

This review found 40 issues worth fixing on amaze.co, 10 of them high impact, across 82 checks. The most urgent: improve image delivery. 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.7 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
275 ms146 msMay 2Oct 17190 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026260 ms
May 9, 2026244 ms
May 16, 2026236 ms
May 23, 2026216 ms
May 30, 2026210 ms
Jun 6, 2026203 ms
Jun 13, 2026209 ms
Jun 20, 2026212 ms
Jun 27, 2026210 ms
Jul 4, 2026209 ms
Jul 11, 2026198 ms
Jul 18, 2026187 ms
Jul 25, 2026180 ms
Aug 1, 2026183 ms
Aug 8, 2026185 ms
Aug 15, 2026183 ms
Aug 22, 2026175 ms
Aug 29, 2026163 ms
Sep 5, 2026161 ms
Sep 12, 2026174 ms
Sep 19, 2026180 ms
Sep 26, 2026183 ms
Oct 3, 2026188 ms
Oct 10, 2026180 ms
Oct 17, 2026190 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 amaze.co (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix51
  • Improve image delivery

    8.0 s · 1.8 MB

    4 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.0 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • 8 third-party services on the page

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

  • Mobile performance score: 51

    51/100

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

  • Reduce unused JavaScript

    600 ms · 303 KiB

    About 303 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    450 ms · 396 KiB

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

  • Reduce unused CSS

    600 ms · 52 KiB

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

  • Google Tag Manager adds 528 ms

    528 ms

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

  • website-files.com adds 242 ms

    242 ms

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    17 KiB

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

  • Minify CSS

    9 KiB

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

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 19.7 s

    19.7 s

    Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CREATE SOMETHING AMAZING. Amaze helps creators monetize the…”.

  • Time to Interactive: 19.7 s

    19.7 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 529 ms

    529 ms

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

  • Speed Index: 4.3 s

    4.3 s

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

  • 6 images without width and height

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

7 checks passed
  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 611 ms

    611 ms

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

  • Tap response (INP) got 27% faster for real visitors

    -27%

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 56 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 56 requests on a phone: images 3.0 MB (14), scripts 1.0 MB (23) and fonts 180 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.1 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

5 to fixGoogle 9395
  • 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.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate 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.

  • 2 links without text

    2 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 11 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

6 to fixGoogle 9174
  • Title is short (5 characters)

    Your title is only 5 characters: “Amaze”. 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.

  • 6 H1 headlines

    There are 6 <h1> headlines (“1.7”, “BILLION+” and “163”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • No XML sitemap

    No XML sitemap at https://www.amaze.co/sitemap.xml, so Google discovers your pages only by following links.

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

  • 16 internal links, 15 external

    The homepage links to 16 pages on amaze.co and 15 external pages.

3 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Leading the future of the creator economy, Amaze helps creators make products, sell merch online, and increase revenue …”.

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

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    33%

    The HTML your server sends has 422 of the 1,274 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.amaze.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.

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

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://www.amaze.co/backup/fresh-vine-wine, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.amaze.co/privacy-policy and https://www.amaze.co/policies/corporate/privacy-policy all use the title “Privacy Policy”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.amaze.co/creators, https://www.amaze.co/brands, https://www.amaze.co/contact, https://www.amaze.co/about-us, https://www.amaze.co/privacy-policy and https://www.amaze.co/policies/corporate/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.amaze.co/policies/corporate/privacy-policy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.amaze.co/contact 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.

  • 8 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 19 small tap targets

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

  • 1 distorted image

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

2 checks passed
  • No console errors

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

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

    The homepage carries about 1,274 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: “GET STARTED”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Get Started”, “Request a Campaign” and “Request Access”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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, LinkedIn Insight 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 amaze.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
Webflow
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on amaze.co, 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