Website review, no card needed

agapee.com logo

agapee.com website review

Visit site (opens in a new tab)Reviewed 9 November 202622 issues · 73 checks

This review found 22 issues worth fixing on agapee.com, 6 of them high impact, across 73 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
1.1 s862 msMay 23Nov 7981 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 2026922 ms
Jun 6, 2026891 ms
Jun 13, 2026888 ms
Jun 20, 2026892 ms
Jun 27, 2026962 ms
Jul 4, 2026992 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 2026981 ms
Real-visitor tap response (INP)75th percentile, phones
197 ms93 msMay 23Nov 7185 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026105 ms
May 30, 2026121 ms
Jun 6, 2026129 ms
Jun 13, 2026130 ms
Jun 20, 2026130 ms
Jun 27, 2026128 ms
Jul 4, 2026127 ms
Jul 11, 2026131 ms
Jul 18, 2026134 ms
Jul 25, 2026136 ms
Aug 1, 2026137 ms
Aug 8, 2026138 ms
Aug 15, 2026138 ms
Aug 22, 2026139 ms
Aug 29, 2026141 ms
Sep 5, 2026143 ms
Sep 12, 2026144 ms
Sep 19, 2026144 ms
Sep 26, 2026146 ms
Oct 3, 2026152 ms
Oct 10, 2026160 ms
Oct 17, 2026170 ms
Oct 24, 2026178 ms
Oct 31, 2026185 ms
Nov 7, 2026185 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 agapee.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. agapee.com at 0.5 s0.5 s
  2. agapee.com at 1.0 s1.0 s
  3. agapee.com at 1.5 s1.5 s
  4. agapee.com at 2.0 s2.0 s
  5. agapee.com at 2.4 s2.4 s
  6. agapee.com at 2.9 s2.9 s
  7. agapee.com at 3.4 s3.4 s
  8. agapee.com at 3.9 s3.9 s

Speed

6 to fix69
  • Improve image delivery

    2.5 s · 1.3 MB

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

  • Mobile performance score: 69

    69/100

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

  • Use efficient cache lifetimes

    350 ms · 296 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Facebook and Google Tag Manager and others), adding 868 KiB and 531 ms of main-thread time.

  • Reduce unused JavaScript

    350 ms · 210 KiB

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

  • Main-thread work: 2.1 s

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    50 ms · 19 KiB

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

  • Font display

    50 ms

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

  • Render-blocking requests

    50 ms

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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

5 to fix100
  • Largest Contentful Paint: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ada necklace: a bezel-set lab-grown diamond pendant on a si…”.

  • Time to Interactive: 15.2 s

    15.2 s

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

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

    +64%

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

  • Speed Index: 5.2 s

    5.2 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 518 ms

    518 ms

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

  • Total Blocking Time: 86 ms

    86 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix65
  • 6 images far larger than shown

    934 KiB

    6 images are downloaded at several times the size a phone draws them, for example 4_5_Ada_Bracelet_C045-Diamonds_0008_Agapee_Diamant_NM_18_120 at 960 px wide, shown at 193 px. Resized copies would save about 934 KiB.

  • Page weight: 4.0 MB in 335 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 335 requests on a phone: images 1.5 MB (13), other files 1.4 MB (250) and scripts 947 KiB (60). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.13 g

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

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

Accessibility

2 to fixGoogle 9697
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 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 10095
  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 64 internal links, 6 external

    The homepage links to 64 pages on agapee.com and 6 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Agapée”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Agapée | Women's Jewelry | Official Site”.

  • Canonical URL set

    The canonical URL is https://agapee.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

1 to fix77
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://agapee.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
  • Organization data: 5 of 6 facts

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 5 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 18 small tap targets

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

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

3 to fix71
  • 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.

  • Only about 121 words

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SUBSCRIBE NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Subscribe Now”, “Track My Order” and “Contact”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

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

  • 19 other companies contacted

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

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Microsoft Clarity · Polar Analytics · Agapee Faq · Agp Cart Gifting · cloudfront.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on agapee.com, including 11 speed issues, 1 SEO issue and 3 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