Website review, no card needed

amazingco.me logo

amazingco.me website review

Visit site (opens in a new tab)Reviewed 22 October 202643 issues · 75 checks

This review found 43 issues worth fixing on amazingco.me, 18 of them high impact, across 75 checks. The most urgent: mobile performance score: 43. 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
4.7 s3.8 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.2 s
May 16, 20264.1 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.6 s
Jul 11, 20264.6 s
Jul 18, 20264.4 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20264.2 s
Sep 5, 20264.0 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.2 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
173 ms156 msMay 2Oct 17171 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026161 ms
May 9, 2026159 ms
May 16, 2026159 ms
May 23, 2026160 ms
May 30, 2026161 ms
Jun 6, 2026161 ms
Jun 13, 2026160 ms
Jun 20, 2026158 ms
Jun 27, 2026161 ms
Jul 4, 2026162 ms
Jul 11, 2026165 ms
Jul 18, 2026167 ms
Jul 25, 2026163 ms
Aug 1, 2026162 ms
Aug 8, 2026162 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026161 ms
Sep 5, 2026160 ms
Sep 12, 2026159 ms
Sep 19, 2026159 ms
Sep 26, 2026159 ms
Oct 3, 2026161 ms
Oct 10, 2026163 ms
Oct 17, 2026171 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 amazingco.me (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amazingco.me at 0.5 s0.5 s
  2. amazingco.me at 1.0 s1.0 s
  3. amazingco.me at 1.6 s1.6 s
  4. amazingco.me at 2.1 s2.1 s
  5. amazingco.me at 2.6 s2.6 s
  6. amazingco.me at 3.1 s3.1 s
  7. amazingco.me at 3.7 s3.7 s
  8. amazingco.me at 4.2 s4.2 s

Speed

10 to fix43
  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 7.9 s

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

  • Use efficient cache lifetimes

    3.1 MB

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

  • Improve image delivery

    2.2 MB

    17 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Freshchat, Facebook and TikTok and others), adding 1.8 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    998 KiB

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

  • Freshchat adds 642 ms

    642 ms

    Freshchat costs a phone 642 ms of main-thread work and 774 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.

  • Reduce unused CSS

    300 ms · 60 KiB

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

  • Facebook adds 314 ms

    314 ms

    Facebook costs a phone 314 ms of main-thread work and 402 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 335 ms. During a long task the page ignores taps.

  • Render-blocking requests

    250 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

  • Legacy JavaScript

    55 KiB

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

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

    203 ms

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

Core Web Vitals

11 to fix33
  • 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.1 s

    5.1 s

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

  • Real-user FCP: 5.0 s

    5.0 s

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

  • Real-user TTFB: 4.7 s

    4.7 s

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

  • Time to Interactive: 35.0 s

    35.0 s

    The page becomes fully interactive after 35.0 s. Good is under 3.8 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.

  • Speed Index: 9.3 s

    9.3 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.14

    0.14

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

  • Cumulative Layout Shift: 0.156

    0.156

    The layout shifts by 0.156 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 16 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

2 checks passed
  • Real-user INP: 147 ms

    147 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

4 to fix33
  • Page weight: 6.6 MB in 184 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 184 requests on a phone: images 2.7 MB (51), scripts 2.5 MB (64) and other files 934 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    1.7 MB

    14 images are downloaded at several times the size a phone draws them, for example watch-party-reimagine-movie-night.jpg at 2,858 px wide, shown at 220 px. Resized copies would save about 1.7 MB.

  • 16 images in older formats

    16 images (2.3 MB) 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.

  • 14 images below the first screen load straight away

    14 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.88 g

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

Accessibility

6 to fixGoogle 8189
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 87 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.

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

5 to fixGoogle 7579
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

5 checks passed
  • One H1 headline

    Your main headline reads: “Mystery Picnics”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “AmazingCo - Experiences you’ll love”.

  • 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.amazingco.me/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    29%

    A phone browser shows 210 words, but the HTML your server sends has only 61. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.amazingco.me/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.

Best practices

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://www.ojrq.net/p/?return=&cid=26315&tpsync=no&auth=.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Segment snippet included twice.”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    6 of 6 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 210 words

    The homepage has only about 210 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 Mystery Picnic” and “Buy a Gift Card”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Book a Mystery Picnic” and “Buy a Gift Card”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Segment.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 4 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.

  • 27 cookies set on arrival

    27

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 amazingco.me, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager | Segment

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on amazingco.me, including 21 speed issues, 5 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