Website review, no card needed

diviofficial.com logo

diviofficial.com website review

Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 60 checks

This review found 25 issues worth fixing on diviofficial.com, 5 of them high impact, across 60 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.0 s3.0 sMay 23Nov 73.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.8 s
Sep 19, 20263.7 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.4 s
Nov 7, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
218 ms164 msMay 23Nov 7195 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026170 ms
May 30, 2026171 ms
Jun 6, 2026175 ms
Jun 13, 2026179 ms
Jun 20, 2026187 ms
Jun 27, 2026196 ms
Jul 4, 2026197 ms
Jul 11, 2026205 ms
Jul 18, 2026212 ms
Jul 25, 2026211 ms
Aug 1, 2026211 ms
Aug 8, 2026210 ms
Aug 15, 2026205 ms
Aug 22, 2026211 ms
Aug 29, 2026210 ms
Sep 5, 2026210 ms
Sep 12, 2026204 ms
Sep 19, 2026197 ms
Sep 26, 2026195 ms
Oct 3, 2026196 ms
Oct 10, 2026197 ms
Oct 17, 2026196 ms
Oct 24, 2026203 ms
Oct 31, 2026196 ms
Nov 7, 2026195 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 990 ms

    990 ms

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

2 checks passed
  • Real-user INP: 195 ms

    195 ms

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

  • Real-user CLS: 0.06

    0.06

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

Images and page weight

3 to fix53
  • Page weight: 6.9 MB

    6.9 MB

    Your homepage downloads 6.9 MB on a phone, 3.4 MB of it images (49%). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

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

  • 4 images far larger than shown

    153 KiB

    4 images are downloaded at several times the size a phone draws them, for example aHR0cHM6Ly9jZG4uZGFzaHNvY2lhbC5jb20vbWVkaWEvZnVsbC8xNzUzOTA0 at 640 px wide, shown at 110 px. Resized copies would save about 153 KiB.

  • About 2.0 g of CO₂ per visit

    1.95 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fix90
  • 3 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 6 images without alt text

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

  • All page content should be contained by landmarks (9 elements)

    All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 43 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 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: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fix91
  • 2 H1 headlines

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 197 internal links, 9 external

    The homepage links to 197 pages on diviofficial.com and 9 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Formulated for women by women, Divi is a haircare brand with vegan, science-backed formulas made to meet you where you …”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Divi Growth Care™ | Complete Care for Growing Hair™”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: AboutPage, BreadcrumbList, ImageObject, Organization and WebPage.

  • 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.diviofficial.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.diviofficial.com/pages/quiz-divi-hair-quiz has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.diviofficial.com/collections/all-products, https://www.diviofficial.com/pages/refer, https://www.diviofficial.com/collections/hair-scalp-products, https://www.diviofficial.com/collections/bundle and https://www.diviofficial.com/pages/quiz-divi-hair-quiz 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 51 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    8 pages 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.

  • 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 8 pages that loaded have a <title>.

Best practices

2 to fix87
  • 12 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 1,428 words of copy

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 47 calls to action

    The homepage has 47 calls to action, for example “Shop All”, “The Merch Shop” and “Shop by Need”.

  • 51 short forms

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

  • Social proof on the page

    Social proof on the homepage: 86 testimonial or review blocks, 2 customer or partner logos and a star rating.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 2 of them by other companies (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.

  • 71 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Angels Camp

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on diviofficial.com, including 4 speed issues, 3 SEO issues and 2 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