Website review, no card needed

getmaycosmetics.com logo

getmaycosmetics.com website review

Visit site (opens in a new tab)Reviewed 10 November 202621 issues · 82 checks

This review found 21 issues worth fixing on getmaycosmetics.com, 6 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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.4 s848 msMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 2026979 ms
Aug 8, 2026916 ms
Aug 15, 2026914 ms
Aug 22, 2026932 ms
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026969 ms
Oct 3, 2026970 ms
Oct 10, 2026973 ms
Oct 17, 20261.1 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
318 ms201 msMay 23Nov 7261 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026214 ms
May 30, 2026238 ms
Jun 6, 2026250 ms
Jun 13, 2026253 ms
Jun 20, 2026253 ms
Jun 27, 2026252 ms
Jul 4, 2026239 ms
Jul 11, 2026236 ms
Jul 18, 2026241 ms
Jul 25, 2026253 ms
Aug 1, 2026270 ms
Aug 8, 2026276 ms
Aug 15, 2026282 ms
Aug 22, 2026288 ms
Aug 29, 2026291 ms
Sep 5, 2026295 ms
Sep 12, 2026292 ms
Sep 19, 2026294 ms
Sep 26, 2026294 ms
Oct 3, 2026298 ms
Oct 10, 2026304 ms
Oct 17, 2026297 ms
Oct 24, 2026289 ms
Oct 31, 2026278 ms
Nov 7, 2026261 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 getmaycosmetics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix96
  • Render-blocking requests

    1.4 s

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

  • Use efficient cache lifetimes

    50 ms · 286 KiB

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

  • 1,515 HTML elements

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

  • Shopify adds 2 ms

    2 ms

    Shopify costs a phone 2 ms of main-thread work and 322 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 JavaScript

    150 ms · 179 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and visually-io.com and others), adding 912 KiB and 232 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Improve image delivery

    98 KiB

    4 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    45 KiB

    About 45 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    13 KiB

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

3 checks passed
  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.7 s

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

  • Server response: 16 ms

    16 ms

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

Core Web Vitals

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

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Real-user INP: 228 ms

    228 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 11 images without width and height

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

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

    +19%

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

9 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

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

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

    1.0 s

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

  • Real-user TTFB: 500 ms

    500 ms

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

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

    -11%

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

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 85 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 85 requests on a phone: scripts 1.3 MB (47), images 575 KiB (21) and HTML 115 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.4 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 9293
  • 10 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 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.

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

  • Headings skip levels

    Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 76 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more 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 (208 characters)

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

  • 75 internal links, 3 external

    The homepage links to 75 pages on getmaycosmetics.com and 3 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “GetMayCosmetics”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Live to Glow! With May Cosmetics”.

  • Canonical URL set

    The canonical URL is https://getmaycosmetics.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://getmaycosmetics.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 11 pages without a meta description

    /collections/bestsellers, /products/mascara, /products/changing-foundation-starters-set, /products/pro-foundation-set, /products/eye-duo-set and /products/complete-beaty-set and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    /collections/bestsellers, /collections/bundels-sets, /pages/about, /pages/contact and /collections/all have 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 28 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 11 small tap targets

    11 of 21 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

1 to fix94
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

  • About 787 words of copy

    The homepage carries about 787 words of visible text.

8 checks passed
  • Clear next step on the first screen

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

  • 18 calls to action

    The homepage has 18 calls to action, for example “SHOP ALL”, “SHOP ALL BUNDLES & SETS” and “Contact”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, 2 customer or partner logos, a star rating, 9 trust badges and “250.000+ Happy customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo 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.

  • 7 cookies set on arrival

    7

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 getmaycosmetics.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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gempages Builder · Triplewhale · Vitals · Google Ads Pixel By Nabu · Kaching Bundles · Microsoft Clarity · Ez Product Translate · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Abconvert · Applovin Shop Integration · Upsellin · Freegifts · Kaching Subscriptions · Appstle Bundles · bestads.com · bogos.io

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | 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 21 issues on getmaycosmetics.com, including 9 speed issues, 1 SEO issue 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