Website review, no card needed

shadedbyshanell.com logo

shadedbyshanell.com website review

Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 75 checks

This review found 39 issues worth fixing on shadedbyshanell.com, 14 of them high impact, across 75 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

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

How it loaded on a phone

  1. shadedbyshanell.com at 1.8 s1.8 s
  2. shadedbyshanell.com at 3.5 s3.5 s
  3. shadedbyshanell.com at 5.3 s5.3 s
  4. shadedbyshanell.com at 7.1 s7.1 s
  5. shadedbyshanell.com at 8.8 s8.8 s
  6. shadedbyshanell.com at 10.6 s10.6 s
  7. shadedbyshanell.com at 12.3 s12.3 s
  8. shadedbyshanell.com at 14.1 s14.1 s

Speed

11 to fix30
  • Reduce unused JavaScript

    3.9 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Main-thread work: 32.2 s

    A phone's processor spends 32.2 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 2.5 s

    2.5 s

    Shopify costs a phone 2.5 s of main-thread work and 5.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,483 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, hcaptcha.com and laireviews.com and others), adding 6.8 MB and 3.9 s of main-thread time.

  • Use efficient cache lifetimes

    3.2 MB

    17 files are served with short cache lifetimes, so returning visitors download them again (3.2 MB).

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

  • hcaptcha.com adds 947 ms

    947 ms

    hcaptcha.com costs a phone 947 ms of main-thread work and 1.2 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.

  • Improve image delivery

    200 ms · 761 KiB

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

  • Render-blocking requests

    600 ms

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

  • Reduce unused CSS

    150 ms · 66 KiB

    About 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    59 KiB

    Polyfills for old browsers add 59 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix27
  • Largest Contentful Paint: 30.8 s

    30.8 s

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

  • Speed Index: 17.8 s

    17.8 s

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

  • Time to Interactive: 57.2 s

    57.2 s

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

  • Total Blocking Time: 3.7 s

    3.7 s

    Scripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.139

    0.139

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

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

1 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

1 to fix33
  • Page weight: 13.9 MB in 713 requests

    13.9 MB

    Your homepage downloads 13.9 MB in 713 requests on a phone: images 5.2 MB (49), other files 4.0 MB (306) and scripts 3.5 MB (282). Under 2 MB keeps phones on slow connections fast.

  • About 3.9 g of CO₂ per visit

    3.94 g

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

Accessibility

5 to fixGoogle 9279
  • Inline text spacing must be adjustable with custom stylesheets (1 element)

    Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 12 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Luxury Press-On Nails Designed for Everyday Wear | ShadedbyShanell”.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

  • Meta description is long (163 characters)

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 265 internal links, 2 external

    The homepage links to 265 pages on shadedbyshanell.com and 2 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://www.shadedbyshanell.com/sitemap.xml.

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.

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.

  • llms.txt published

    The site publishes https://www.shadedbyshanell.com/llms.txt (65 KiB, 185 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 6 linked pages are broken

    Your homepage links to https://www.shadedbyshanell.com/www.facebook.com/shadedbyshanell, https://www.shadedbyshanell.com/www.x.com/shadedbyshanell, https://www.shadedbyshanell.com/www.instagram.com/shadedbyshanell, https://www.shadedbyshanell.com/www.pinterest.com/shadedbyshanell, https://www.shadedbyshanell.com/www.youtube.com/shadedbyshanell and https://www.shadedbyshanell.com/www.tiktok.com/@shadedbyshanell, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://www.shadedbyshanell.com/pages/loyalty-program and https://www.shadedbyshanell.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.shadedbyshanell.com/collections/all, https://www.shadedbyshanell.com/collections, https://www.shadedbyshanell.com/collections/sale, https://www.shadedbyshanell.com/collections/25-under-collection and https://www.shadedbyshanell.com/collections/press-ons 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 84 found) and read each the way a search engine does.

4 checks passed
  • 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 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "product-card-basic" has already bee…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 74 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Book a 1:1 Session”, “SBS LOOK BOOK” and “Shop now”.

  • 16 short forms

    16 short forms (1 field at most) are right on the homepage, asking for an email.

  • Opening hours shown

    Your opening hours are on the homepage.

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 Pinterest Tag (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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 shadedbyshanell.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 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Lai Product Reviews · Xb Announcement Bar · Armex · Xb Trust Badges · Bm Country Blocker Ip Blocker · Reelfy Videos · Terms Checkbox · Boostymark Regionblock · Terms And Conditions In Cart · Ea Accessibility · Forms · Super Subscriptions · Essential Pre Order Presale · B Shipping Protection · Product Slide Design · Essential Post Purchase Upsell · Nexora Product Labels · fugu-it.com · cloudfront.net · amazonaws.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

Company

Headquarters
Norfolk

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on shadedbyshanell.com, including 16 speed issues, 4 SEO issues and 7 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