Website review, no card needed

amazingcosmetics.com logo

amazingcosmetics.com website review

Visit site (opens in a new tab)Reviewed 3 November 202626 issues · 75 checks

This review found 26 issues worth fixing on amazingcosmetics.com, 10 of them high impact, across 75 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
3.5 s1.2 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20262.9 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.6 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.3 s
Oct 3, 20262.1 s
Oct 10, 20261.9 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
206 ms121 msMay 16Oct 31148 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026161 ms
May 23, 2026162 ms
May 30, 2026161 ms
Jun 6, 2026178 ms
Jun 13, 2026187 ms
Jun 20, 2026187 ms
Jun 27, 2026179 ms
Jul 4, 2026162 ms
Jul 11, 2026161 ms
Jul 18, 2026152 ms
Jul 25, 2026163 ms
Aug 1, 2026169 ms
Aug 8, 2026167 ms
Aug 15, 2026169 ms
Aug 22, 2026171 ms
Aug 29, 2026175 ms
Sep 5, 2026191 ms
Sep 12, 2026196 ms
Sep 19, 2026194 ms
Sep 26, 2026179 ms
Oct 3, 2026159 ms
Oct 10, 2026138 ms
Oct 17, 2026131 ms
Oct 24, 2026134 ms
Oct 31, 2026148 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 amazingcosmetics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amazingcosmetics.com at 0.4 s0.4 s
  2. amazingcosmetics.com at 0.9 s0.9 s
  3. amazingcosmetics.com at 1.3 s1.3 s
  4. amazingcosmetics.com at 1.7 s1.7 s
  5. amazingcosmetics.com at 2.1 s2.1 s
  6. amazingcosmetics.com at 2.6 s2.6 s
  7. amazingcosmetics.com at 3.0 s3.0 s
  8. amazingcosmetics.com at 3.4 s3.4 s

Speed

8 to fix54
  • Reduce unused JavaScript

    1.8 s · 623 KiB

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

  • Main-thread work: 11.0 s

    A phone's processor spends 11.0 s on main-thread work while loading, 3.3 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 (Shopify, Klaviyo and Clarity and others), adding 2.0 MB and 1.0 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Use efficient cache lifetimes

    250 ms · 262 KiB

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

  • Shopify adds 301 ms

    301 ms

    Shopify costs a phone 301 ms of main-thread work and 1.0 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.

  • Klaviyo adds 239 ms

    239 ms

    Klaviyo costs a phone 239 ms of main-thread work and 502 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,676 HTML elements

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

  • Reduce unused CSS

    290 ms · 53 KiB

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

  • 10 long tasks on the main thread

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    100 ms · 19 KiB

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

  • Improve image delivery

    50 ms · 54 KiB

    2 images could be 54 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

    9 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.2 s

    14.2 s

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

  • Time to Interactive: 22.5 s

    22.5 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 334 ms

    334 ms

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

6 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 CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

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

    -13%

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

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

    -50%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 671 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 671 requests on a phone: scripts 2.3 MB (285), other files 1.5 MB (288) and images 356 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.36 g

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

4 to fixGoogle 9494
  • Elements must only use permitted ARIA attributes (16 elements)

    Elements must only use permitted ARIA attributes: 16 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 13 links without text

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 51 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: 51 passed and 3 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 10088
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “AMAZINGCOSMETICS | Amazing Ingredients. Amazing Results. – AmazingCosmetics”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Shop Best-Sellers”). One clear main headline is easier for people and search engines.

  • 103 internal links, 8 external

    The homepage links to 103 pages on amazingcosmetics.com and 8 external pages.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “We created our concealer, primer and foundation formulas with skin-loving ingredients so your makeup not only looks but…”.

  • Canonical URL set

    The canonical URL is https://www.amazingcosmetics.com/.

  • Structured data in place

    Structured data found: ItemList, 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://www.amazingcosmetics.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.amazingcosmetics.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: 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 (380 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    1 page 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 1 page 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 18 small tap targets

    18 of 41 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 “Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • 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 209 words

    The homepage has only about 209 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: “SHOP BROW POWDER”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP”, “Shop All” and “SHOP BROW POWDER”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 22 cookies set on arrival

    22

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

  • 46 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on amazingcosmetics.com, including 13 speed issues, 2 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