Programmable

Website review, no card needed

namabeauty.co logo

namabeauty.co website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 77 checks

This review found 34 issues worth fixing on namabeauty.co, 10 of them high impact, across 77 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

Site score

77C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.3 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s

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

namabeauty.co (opens in a new tab)
Full-page screenshot of namabeauty.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. namabeauty.co at 0.6 s0.6 s
  2. namabeauty.co at 1.1 s1.1 s
  3. namabeauty.co at 1.7 s1.7 s
  4. namabeauty.co at 2.2 s2.2 s
  5. namabeauty.co at 2.8 s2.8 s
  6. namabeauty.co at 3.3 s3.3 s
  7. namabeauty.co at 3.9 s3.9 s
  8. namabeauty.co at 4.4 s4.4 s

Speed

5 to fix64

  • Reduce unused JavaScript

    1.0 s · 253 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Improve image delivery

    450 ms · 309 KiB

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

  • Render-blocking requests

    500 ms

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

  • Shopify adds 162 ms

    162 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, joy.so and Unpkg and others), adding 906 KiB and 281 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • Font display

    100 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    45 KiB

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

  • Reduce unused CSS

    10 KiB

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

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

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 1.4 s

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

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

  • Largest Contentful Paint: 11.6 s

    11.6 s

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

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 4 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed

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

    -19%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 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).

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

5 to fix28

  • 1 image over 500 KB

    GAMBAR_GERAK.gif weighs 8.2 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 7.3 MB in 244 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 244 requests on a phone: media 3.2 MB (2), images 2.0 MB (12) and scripts 871 KiB (81). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (8.5 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.

  • 7 images below the first screen load straight away

    7 images further down the page (609 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    90 KiB

    1 image is downloaded at several times the size a phone draws it, for example 01._WEBSITE-PDP-05.jpg at 2,000 px wide, shown at 360 px. Resized copies would save about 90 KiB.

  • About 2.1 g of CO₂ per visit

    2.07 g

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

Accessibility

4 to fixGoogle 8594

  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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 12 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 4 failed. 2 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 short (18 characters)

    Your title is only 18 characters: “Nama Beauty – NAMA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (47 characters)

    Your meta description is only 47 characters: “Nama Beauty by Luna Maya Beauty in your own way”. 70 to 160 characters is enough to sell the click.

  • 2 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 51 internal links, 5 external

    The homepage links to 51 pages on namabeauty.co and 5 external pages.

5 checks passed

  • Canonical URL set

    The canonical URL is https://namabeauty.co/.

  • Structured data in place

    Structured data found: 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://namabeauty.co/sitemap.xml.

AI search readiness

100
4 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 (690 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix71

  • 4 pages point its canonical at the homepage

    https://namabeauty.co/products/new-launch-nama-blurring-melt-lip-tint, https://namabeauty.co/products/nama-regenskin-anti-aging-moisturizer-hand-body, https://namabeauty.co/products/nama-barely-seen-physical-sunscreen-spf-50-pa and https://namabeauty.co/products/nama-duo-glo-cushion-eyeshadow declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 5 pages share a title

    /, https://namabeauty.co/products/new-launch-nama-blurring-melt-lip-tint, https://namabeauty.co/products/nama-regenskin-anti-aging-moisturizer-hand-body, https://namabeauty.co/products/nama-barely-seen-physical-sunscreen-spf-50-pa and https://namabeauty.co/products/nama-duo-glo-cushion-eyeshadow all use the title “Nama Beauty – NAMA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://namabeauty.co/collections/new-arrivals, https://namabeauty.co/collections/makeup, https://namabeauty.co/collections/best-seller, https://namabeauty.co/blogs/news, https://namabeauty.co/pages/about and https://namabeauty.co/blogs/key-ingredients and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://namabeauty.co/products/new-launch-nama-blurring-melt-lip-tint, https://namabeauty.co/products/nama-regenskin-anti-aging-moisturizer-hand-body, https://namabeauty.co/products/nama-barely-seen-physical-sunscreen-spf-50-pa and https://namabeauty.co/products/nama-duo-glo-cushion-eyeshadow use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://namabeauty.co/collections/new-arrivals, https://namabeauty.co/collections/makeup, https://namabeauty.co/collections/skincare, https://namabeauty.co/collections/best-seller, https://namabeauty.co/pages/about and https://namabeauty.co/blogs/key-ingredients and 4 others 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 16 found) and read each the way a search engine does.

3 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • 3 JavaScript errors while loading

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

2 checks passed

  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 461 words of visible text.

3 checks passed

  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP NOW”, “LEARN MORE” and “Shop Skincare”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 24 cookies set on arrival

    24

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

  • 29 other companies contacted

    Loading the homepage contacts 29 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 namabeauty.co, 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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Tabs Studio · Inbox · Pagefly Ai Page Builder · Joy Loyalty Program · Swym Wishlist Plus · powr.io · nfcube.com · devbdd.com · webmarked.net · stationmade.com · azureedge.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
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Jakarta

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on namabeauty.co, including 10 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