Website review, no card needed

divinity-beauty.store logo

divinity-beauty.store website review

Visit site (opens in a new tab)Reviewed 6 November 202620 issues · 59 checks

This review found 20 issues worth fixing on divinity-beauty.store, 4 of them high impact, across 59 checks. The most urgent: no call to action on the first screen. 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
5.5 s2.4 sMay 16Sep 122.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.3 s
May 23, 20264.3 s
May 30, 20264.5 s
Jun 6, 20264.7 s
Jun 13, 20264.9 s
Jun 20, 20265.2 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20264.9 s
Jul 18, 20264.8 s
Jul 25, 20264.8 s
Aug 1, 20264.8 s
Aug 8, 20265.1 s
Aug 15, 20265.0 s
Aug 22, 20264.9 s
Aug 29, 20264.8 s
Sep 5, 20263.5 s
Sep 12, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
341 ms142 msMay 16Aug 29170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026285 ms
May 23, 2026318 ms
May 30, 2026279 ms
Jun 6, 2026221 ms
Jun 13, 2026212 ms
Jun 20, 2026191 ms
Jun 27, 2026190 ms
Jul 4, 2026179 ms
Jul 11, 2026178 ms
Jul 18, 2026170 ms
Jul 25, 2026165 ms
Aug 1, 2026181 ms
Aug 8, 2026171 ms
Aug 15, 2026180 ms
Aug 22, 2026206 ms
Aug 29, 2026170 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 divinity-beauty.store (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. divinity-beauty.store at 0.5 s0.5 s
  2. divinity-beauty.store at 1.1 s1.1 s
  3. divinity-beauty.store at 1.6 s1.6 s
  4. divinity-beauty.store at 2.1 s2.1 s
  5. divinity-beauty.store at 2.6 s2.6 s
  6. divinity-beauty.store at 3.2 s3.2 s
  7. divinity-beauty.store at 3.7 s3.7 s
  8. divinity-beauty.store at 4.2 s4.2 s

Speed

5 to fix92
  • Render-blocking requests

    850 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

  • Improve image delivery

    600 ms · 141 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Facebook, converty.shop and run.app), adding 1.3 MB and 365 ms of main-thread time.

  • converty.shop adds 155 ms

    155 ms

    converty.shop costs a phone 155 ms of main-thread work and 1.1 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.

  • Use efficient cache lifetimes

    250 KiB

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

  • Reduce unused JavaScript

    150 ms · 170 KiB

    About 170 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.

  • 3 long tasks on the main thread

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

  • 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: 92

    92/100

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

  • Main-thread work: 1.1 s

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

  • Server response: 20 ms

    20 ms

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

Core Web Vitals

3 to fix89
  • Time to Interactive: 6.8 s

    6.8 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

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

  • 1 image without width and height

    1 image 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.

6 checks passed
  • Tap response (INP) got 38% faster for real visitors

    -38%

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

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

    -27%

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

  • Total Blocking Time: 106 ms

    106 ms

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

  • Speed Index: 2.2 s

    2.2 s

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

  • Cumulative Layout Shift: 0.005

    0.005

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix90
  • 6 images far larger than shown

    197 KiB

    6 images are downloaded at several times the size a phone draws them, for example 99385b7c6886c4eefb956fee56a41e7383c24450568914b1281e0589f8f2 at 800 px wide, shown at 171 px. Resized copies would save about 197 KiB.

  • About 0.4 g of CO₂ per visit

    0.39 g

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

3 checks passed
  • Page weight: 1.4 MB in 45 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 45 requests on a phone: images 721 KiB (15), scripts 523 KiB (17) and fonts 109 KiB (7). That is a lean page.

  • 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 9896
  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (15 characters)

    Your title is only 15 characters: “Divinity.beauty”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (68 characters)

    Your meta description is only 68 characters: “Divinity.beauty is an online store that sells a variety of products.”. 70 to 160 characters is enough to sell the click.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

6 checks passed
  • One H1 headline

    Your main headline reads: “✨ مرحبا بحرفائنا ✨”.

  • Canonical URL set

    The canonical URL is https://divinity-beauty.store/.

  • Structured data in place

    Structured data found: Organization.

  • 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://divinity-beauty.store/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://divinity-beauty.store/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.

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 131 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 4 cookies set on arrival

    4

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 divinity-beauty.store, 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
AVADA Commerce;Shopify;Shopify Plus
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on divinity-beauty.store, including 8 speed issues, 3 SEO issues and 5 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