Website review, no card needed

shopdanileigh.com logo

shopdanileigh.com website review

Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 63 checks

This review found 33 issues worth fixing on shopdanileigh.com, 8 of them high impact, across 63 checks. The most urgent: page is set to noindex. 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

Full-page screenshot of shopdanileigh.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix72
  • Mobile performance score: 72

    72/100

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

  • Privy adds 377 ms

    377 ms

    Privy costs a phone 377 ms of main-thread work and 594 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.

  • Use efficient cache lifetimes

    428 KiB

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

  • Reduce unused JavaScript

    338 KiB

    About 338 KiB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Privy, lpage.co and Shopify and others), adding 831 KiB and 465 ms of main-thread time.

  • Render-blocking requests

    150 ms

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    54 KiB

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

  • Legacy JavaScript

    8 KiB

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix72
  • Time to Interactive: 12.2 s

    12.2 s

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

  • Cumulative Layout Shift: 0.408

    0.408

    The layout shifts by 0.408 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

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

2 checks passed
  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Contact Us FAQ Terms of Service Privacy Policy Terms of Ser…”.

  • Total Blocking Time: 121 ms

    121 ms

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

Images and page weight

1 to fix67
  • Page weight: 2.2 MB in 125 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 125 requests on a phone: other files 1.2 MB (58), scripts 770 KiB (46) and fonts 119 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

Accessibility

7 to fixGoogle 8986
  • Unlabelled dropdowns

    1 dropdown has no label.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Positive tabindex

    9 elements have a tabindex above 0, which scrambles the keyboard order.

  • 8 text elements with low contrast

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

  • 1 form field without a label

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

1 checks passed
  • 22 automated accessibility rules passed

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

SEO

9 to fixGoogle 5436
  • Page is set to noindex

    The robots meta tag says “noindex”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 249 links crawlers can't follow

    249 links have no real href, so search engines can't follow them.

  • Title is short (24 characters)

    Your title is only 24 characters: “DaniLeigh Official Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://shopdanileigh.com/sitemap.xml, so Google discovers your pages only by following links.

  • Only 4 internal links

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • Canonical URL set

    The canonical URL is https://shopdanileigh.com/password.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://shopdanileigh.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.

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

Other pages

100
  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Only about 22 words

    The homepage has only about 22 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 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.

  • 12 other companies contacted

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

Apps your storefront loads

privy.com · trackedlink.net · printful.com

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on shopdanileigh.com, including 8 speed issues, 9 SEO issues and 4 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