Website review, no card needed

slickhair.com logo

slickhair.com website review

Visit site (opens in a new tab)Reviewed 11 November 202646 issues · 88 checks

This review found 46 issues worth fixing on slickhair.com, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
2.9 s2.1 sMay 23Nov 72.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.5 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.6 s
Nov 7, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
193 ms139 msMay 23Nov 7179 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026145 ms
May 30, 2026149 ms
Jun 6, 2026154 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026164 ms
Jul 4, 2026169 ms
Jul 11, 2026169 ms
Jul 18, 2026169 ms
Jul 25, 2026169 ms
Aug 1, 2026165 ms
Aug 8, 2026171 ms
Aug 15, 2026176 ms
Aug 22, 2026179 ms
Aug 29, 2026177 ms
Sep 5, 2026172 ms
Sep 12, 2026175 ms
Sep 19, 2026170 ms
Sep 26, 2026169 ms
Oct 3, 2026165 ms
Oct 10, 2026174 ms
Oct 17, 2026187 ms
Oct 24, 2026187 ms
Oct 31, 2026187 ms
Nov 7, 2026179 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 slickhair.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. slickhair.com at 1.0 s1.0 s
  2. slickhair.com at 2.0 s2.0 s
  3. slickhair.com at 3.1 s3.1 s
  4. slickhair.com at 4.1 s4.1 s
  5. slickhair.com at 5.1 s5.1 s
  6. slickhair.com at 6.1 s6.1 s
  7. slickhair.com at 7.1 s7.1 s
  8. slickhair.com at 8.1 s8.1 s

Speed

14 to fix49
  • Render-blocking requests

    1.2 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 6.3 s

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

  • Reduce unused JavaScript

    320 ms · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, Shopify and Klaviyo and others), adding 2.7 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 1.5 MB

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

  • Reduce unused CSS

    600 ms · 189 KiB

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

  • route.com adds 624 ms

    624 ms

    route.com costs a phone 624 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.

  • Duplicated JavaScript

    486 KiB

    486 KiB JavaScript is shipped twice across bundles.

  • 12 long tasks on the main thread

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

  • Shopify adds 290 ms

    290 ms

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

  • Klaviyo adds 200 ms

    200 ms

    Klaviyo costs a phone 200 ms of main-thread work and 517 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.

  • emotivecdn.io adds 155 ms

    155 ms

    emotivecdn.io costs a phone 155 ms of main-thread work and 384 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.

  • 1,834 HTML elements

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

  • Legacy JavaScript

    150 ms · 45 KiB

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

  • Improve image delivery

    96 KiB

    4 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

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

  • Time to Interactive: 28.0 s

    28.0 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Holiday 2026 mobile banner - Give the gift of Slick”.

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 660 ms

    660 ms

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 276 ms

    276 ms

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

  • Real-user CLS: 0.21

    0.21

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

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

    +24%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 861 ms

    861 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

1 checks passed
  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 296 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 296 requests on a phone: scripts 3.0 MB (113), other files 855 KiB (112) and images 472 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.35 g

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

3 checks passed
  • 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.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8391
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 14 text elements with low contrast

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

  • 12 images without alt text

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

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

  • 3 form fields without a label

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Meta description is long (309 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 98 internal links, 12 external

    The homepage links to 98 pages on slickhair.com and 12 external pages.

6 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “SLICKHAIR | Home of the world's first & original SLICK STICK®”.

  • Canonical URL set

    The canonical URL is https://slickhair.com/.

  • 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://slickhair.com/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 (590 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix81
  • 3 pages point its canonical at the homepage

    https://slickhair.com/products/slickhair-holiday-ultimate-cracker-set, https://slickhair.com/products/the-touch-up-trio-2 and https://slickhair.com/products/signature-slick-2 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.

  • 4 pages share a title

    /, https://slickhair.com/products/slickhair-holiday-ultimate-cracker-set, https://slickhair.com/products/the-touch-up-trio-2 and https://slickhair.com/products/signature-slick-2 all use the title “SLICKHAIR | Home of the world's first & original SLICK STICK®”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://slickhair.com/collections/clearance, https://slickhair.com/products/slickhair-holiday-ultimate-cracker-set, https://slickhair.com/products/the-touch-up-trio-2 and https://slickhair.com/products/signature-slick-2 use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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
  • 5 JavaScript errors while loading

    5 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

    43 of 51 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 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.

  • Thin social proof

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

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

    The homepage carries about 468 words of visible text.

3 checks passed
  • 23 calls to action

    The homepage has 23 calls to action, for example “SHOP”, “SHOP ALL” and “CONTACT US”.

  • 17 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

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

  • 53 other companies contacted

    Loading the homepage contacts 53 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 slickhair.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

Blotout Edgetag · Hotjar Install · Llama Cart Upsells · Tolstoy · Route Protection Tracking · Gorgias Live Chat Helpdesk · Cozy Country Redirect · Judge Me Reviews · Instafeed · Rez Preorder Back In Stock · Emotive · Klaviyo Email Marketing Sms · Bazaarvoice Reviews Photos · Upsell Prod · Countdown Timer · Order Value Booster · arhamcommerce.com · addons.business · revenuehunt.com · 9gtb.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
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on slickhair.com, including 27 speed issues, 2 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