Website review, no card needed

skullshaver.co.uk logo

skullshaver.co.uk website review

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

This review found 39 issues worth fixing on skullshaver.co.uk, 18 of them high impact, across 88 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

Real-visitor load time (LCP)75th percentile, phones
3.4 s1.3 sMay 23Nov 73.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.2 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20261.7 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20262.6 s
Nov 7, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
131 ms81 msMay 23Nov 7125 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202694 ms
May 30, 202688 ms
Jun 6, 202688 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202691 ms
Jul 4, 202692 ms
Jul 11, 202694 ms
Jul 18, 202695 ms
Jul 25, 202698 ms
Aug 1, 2026103 ms
Aug 8, 2026103 ms
Aug 15, 2026100 ms
Aug 22, 202691 ms
Aug 29, 202688 ms
Sep 5, 202689 ms
Sep 12, 202688 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202688 ms
Oct 24, 202688 ms
Oct 31, 2026112 ms
Nov 7, 2026125 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 skullshaver.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. skullshaver.co.uk at 0.7 s0.7 s
  2. skullshaver.co.uk at 1.5 s1.5 s
  3. skullshaver.co.uk at 2.2 s2.2 s
  4. skullshaver.co.uk at 2.9 s2.9 s
  5. skullshaver.co.uk at 3.7 s3.7 s
  6. skullshaver.co.uk at 4.4 s4.4 s
  7. skullshaver.co.uk at 5.1 s5.1 s
  8. skullshaver.co.uk at 5.8 s5.8 s

Speed

12 to fix35
  • Reduce unused JavaScript

    30.8 s · 4.1 MB

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

  • Use efficient cache lifetimes

    1.8 s · 645 KiB

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

  • YouTube adds 1.8 s

    1.8 s

    YouTube costs a phone 1.8 s of main-thread work and 5.8 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.

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 7.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 8.2 MB and 3.0 s of main-thread time.

  • Google Tag Manager adds 642 ms

    642 ms

    Google Tag Manager costs a phone 642 ms of main-thread work and 1.0 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

    569 KiB

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

  • 1,671 HTML elements

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

  • Shopify adds 120 ms

    120 ms

    Shopify costs a phone 120 ms of main-thread work and 439 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 93 ms

    93 ms

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

  • Legacy JavaScript

    200 ms · 56 KiB

    Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    30 ms · 120 KiB

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

  • 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

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

9 to fix100
  • First Contentful Paint: 30.1 s

    30.1 s

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

  • Largest Contentful Paint: 52.8 s

    52.8 s

    Your largest element takes 52.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Early Bird sale banner for Skull Shaver, featuring a man ho…”.

  • Speed Index: 30.1 s

    30.1 s

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

  • Time to Interactive: 63.5 s

    63.5 s

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

  • Total Blocking Time: 686 ms

    686 ms

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

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

    +30%

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

  • Largest content (LCP) got 38% slower for real visitors

    +38%

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

  • 42 images without width and height

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

  • Cumulative Layout Shift: 0.109

    0.109

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

6 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 387 ms

    387 ms

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

Images and page weight

2 to fix60
  • Page weight: 11.2 MB in 403 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 403 requests on a phone: scripts 7.8 MB (126), images 1,021 KiB (46) and other files 864 KiB (172). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    65 KiB

    1 image is downloaded at several times the size a phone draws it, for example Pitbull-GOLD-full-size-logo-5_1080x_54d90b26-7470-486b-a7dd- at 1,080 px wide, shown at 62 px. Resized copies would save about 65 KiB.

  • 3 images below the first screen load straight away

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

  • About 3.2 g of CO₂ per visit

    3.17 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.17 g of CO₂e: 380.1 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

6 to fixGoogle 9291
  • Hidden but focusable

    17 elements hidden from screen readers can still receive keyboard focus.

  • 9 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Electric Shavers for Head, Face and Body | Skull Shaver – Skull Shaver UK”.

  • No structured data

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

  • 4 links crawlers can't follow

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

  • 111 internal links, 13 external

    The homepage links to 111 pages on skullshaver.co.uk and 13 external pages.

6 checks passed
  • Meta description: 102 characters

    Your meta description is 102 characters: “Get faster and smoother shave thanks to the innovative design of Skull Shaver's game changing products”.

  • One H1 headline

    Your main headline reads: “Skull Shaver UK”.

  • Canonical URL set

    The canonical URL is https://skullshaver.co.uk/.

  • 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://skullshaver.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • 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://skullshaver.co.uk/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,091 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without an H1

    https://skullshaver.co.uk/collections and https://skullshaver.co.uk/pages/women-s-shavers 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 43 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0255/0156/4962/t/4/assets/Skullshave_Events_Videos.png.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 970 words of copy

    The homepage carries about 970 words of visible text.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop Now”, “SHOP ALL” and “Contact Us”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 150 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 2 of them by other companies (measured from a US location before any click).

  • 46 other companies contacted

    Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 skullshaver.co.uk, 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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Zoorix Cross Sell · Klaviyo Email Marketing Sms · Okendo · Freegifts · weglot.com · cloudfront.net · reamaze.com · addons.business · rechargecdn.com · bogos.io

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 Analytics | Google Tag Manager
Hosting
Shopify

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 skullshaver.co.uk, including 21 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