Website review, no card needed

annmariegianni.com logo

annmariegianni.com website review

Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 86 checks

This review found 40 issues worth fixing on annmariegianni.com, 10 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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.9 s2.5 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
187 ms150 msMay 16Oct 31156 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026161 ms
May 23, 2026162 ms
May 30, 2026163 ms
Jun 6, 2026171 ms
Jun 13, 2026171 ms
Jun 20, 2026170 ms
Jun 27, 2026172 ms
Jul 4, 2026170 ms
Jul 11, 2026163 ms
Jul 18, 2026162 ms
Jul 25, 2026158 ms
Aug 1, 2026154 ms
Aug 8, 2026161 ms
Aug 15, 2026162 ms
Aug 22, 2026162 ms
Aug 29, 2026163 ms
Sep 5, 2026164 ms
Sep 12, 2026172 ms
Sep 19, 2026181 ms
Sep 26, 2026183 ms
Oct 3, 2026179 ms
Oct 10, 2026173 ms
Oct 17, 2026164 ms
Oct 24, 2026162 ms
Oct 31, 2026156 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 annmariegianni.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix51
  • Reduce unused JavaScript

    2.7 s · 711 KiB

    About 711 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Improve image delivery

    2.1 s · 530 KiB

    1 image could be 530 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Facebook and others), adding 3.6 MB and 1.6 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 872 KiB

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

  • Mobile performance score: 51

    51/100

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

  • Render-blocking requests

    900 ms

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

  • Google Tag Manager adds 740 ms

    740 ms

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

  • Legacy JavaScript

    700 ms · 90 KiB

    Polyfills for old browsers add 90 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 700 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 99 KiB

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

  • Main-thread work: 3.9 s

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

  • OptiMonk adds 160 ms

    160 ms

    OptiMonk costs a phone 160 ms of main-thread work and 1.7 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.

  • 14 long tasks on the main thread

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

  • Klaviyo adds 267 ms

    267 ms

    Klaviyo costs a phone 267 ms of main-thread work and 627 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,602 HTML elements

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

  • Duplicated JavaScript

    150 ms · 17 KiB

    17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    6 KiB

    6 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: 13 ms

    13 ms

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

Core Web Vitals

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

    19.8 s

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

  • Time to Interactive: 24.6 s

    24.6 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Total Blocking Time: 636 ms

    636 ms

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 151 ms

    151 ms

    Real visitors wait 151 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.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • Page weight: 4.7 MB in 276 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 276 requests on a phone: images 2.1 MB (83), scripts 2.1 MB (104) and other files 267 KiB (70). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    SkinQuiz_GIF_Slow-1.gif weighs 680 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

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

  • 1 image below the first screen load straight away

    1 image further down the page (680 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.34 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 161.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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10099
  • 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 53 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: 53 passed and 1 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 8580
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Organic Ingredients, Handcrafted Skin Care & Makeup | Annmarie Gianni”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Wildcrafted Skin Care Made With Organic Ingredien…” and “Build Your PerfectSkin Care Regimen”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (HealthAndBeautyBusiness, Organization, Person and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 14 links crawlers can't follow

    14 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 55 internal links, 181 external

    The homepage links to 55 pages on annmariegianni.com and 181 external pages.

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Transform your skin care routine and achieve naturally healthy skin with our wildcrafted skin care products made with o…”.

  • Canonical URL set

    The canonical URL is https://www.annmariegianni.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.annmariegianni.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.annmariegianni.com/skin-consultation is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://www.annmariegianni.com/events, https://www.annmariegianni.com/store-locations, https://www.annmariegianni.com/our-beginning, https://www.annmariegianni.com/our-process, https://www.annmariegianni.com/our-team and https://www.annmariegianni.com/our-values and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.annmariegianni.com/skin-care-articles has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 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 a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 1,039 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop”, “View Shop” and “Book Consultation”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

  • 45 other companies contacted

    Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 annmariegianni.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
WordPress
Framework
jQuery
E-commerce
Shopify;Shopify Plus
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
2009
Headquarters
Berkeley

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 annmariegianni.com, including 22 speed issues, 5 SEO issues 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