Website review, no card needed

ffs-outlet.co.uk logo

ffs-outlet.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202635 issues · 86 checks

This review found 35 issues worth fixing on ffs-outlet.co.uk, 13 of them high impact, across 86 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 ffs-outlet.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ffs-outlet.co.uk at 0.4 s0.4 s
  2. ffs-outlet.co.uk at 0.8 s0.8 s
  3. ffs-outlet.co.uk at 1.2 s1.2 s
  4. ffs-outlet.co.uk at 1.6 s1.6 s
  5. ffs-outlet.co.uk at 2.0 s2.0 s
  6. ffs-outlet.co.uk at 2.4 s2.4 s
  7. ffs-outlet.co.uk at 2.9 s2.9 s
  8. ffs-outlet.co.uk at 3.3 s3.3 s

Speed

12 to fix46
  • Reduce unused JavaScript

    3.7 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.7 s faster on a phone.

  • Avoid multiple page redirects

    3.6 s

    The page goes through 3 redirects before it starts loading, costing about 3.6 s. Link and advertise the final URL directly.

  • Use efficient cache lifetimes

    1.5 s · 282 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 2.2 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 (ffs.co.uk, dixa.io and posthog.com and others), adding 3.1 MB and 1.6 s of main-thread time.

  • ffs.co.uk adds 368 ms

    368 ms

    ffs.co.uk costs a phone 368 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.

  • dixa.io adds 296 ms

    296 ms

    dixa.io costs a phone 296 ms of main-thread work and 479 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.

  • Document request latency

    300 ms

    The HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 16 long tasks on the main thread

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

  • Shopify adds 183 ms

    183 ms

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

  • Reduce unused CSS

    160 ms · 49 KiB

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

  • Legacy JavaScript

    150 ms · 39 KiB

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

  • Improve image delivery

    150 ms · 8 KiB

    1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    14 KiB

    14 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: 16 ms

    16 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 15.9 s

    15.9 s

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

  • Time to Interactive: 23.3 s

    23.3 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Total Blocking Time: 722 ms

    722 ms

    Scripts block taps and scrolling for 722 ms in total while the page loads. Good is under 200 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.

7 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.5 s

    1.5 s

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

  • Real-user INP: 165 ms

    165 ms

    Real visitors wait 165 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 435 ms

    435 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 4.0 MB in 304 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 304 requests on a phone: scripts 2.4 MB (134), other files 904 KiB (120) and images 227 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    spring-sale-header-background.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.13 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8894
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 images without alt text

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

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), 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
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 8592
  • Canonical points to another host

    Your canonical URL points to ffs.co.uk, not ffs-outlet.co.uk, so Google may credit that host instead.

  • Structured data has 2 problems

    Structured data found (FAQPage, OnlineStore, Organization and Store) but with 2 problems, for example “Organization: url points at a different host (https://www.ffs.co.uk)”.

  • 93 internal links, 5 external

    The homepage links to 93 pages on ffs-outlet.co.uk and 5 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Multi-award winning shaving and beauty trusted by over 100,000 customers. It’s our ethos that beauty should be effortle…”.

  • One H1 headline

    Your main headline reads: “Women's Razor Subscription, Refill Blades & Skincare”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Women's Razor Subscription | Which? Best Buy | FFS Beauty”.

  • 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://ffs-outlet.co.uk/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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://ffs-outlet.co.uk/llms.txt (5 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://ffs-outlet.co.uk/pages/shaving, https://ffs-outlet.co.uk/pages/face, https://ffs-outlet.co.uk/pages/body-care, https://ffs-outlet.co.uk/collections/hair, https://ffs-outlet.co.uk/collections/bundles and https://ffs-outlet.co.uk/collections/accessories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://ffs-outlet.co.uk/pages/subscribe/razor-starter-set, https://ffs-outlet.co.uk/pages/shaving, https://ffs-outlet.co.uk/pages/face, https://ffs-outlet.co.uk/pages/body-care, https://ffs-outlet.co.uk/pages/about and https://ffs-outlet.co.uk/pages/recycle 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 37 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.

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

Best practices

3 to fixGoogle 7385
  • 12 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://app.groas.ai/content.js' from origin 'https://www.ffs.co.uk' has been blocked by CORS poli…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage has only about 239 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

5 checks passed
  • 43 calls to action

    The homepage has 43 calls to action, for example “Subscribe”, “Shop All” and “Shop By”.

  • 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: 24 testimonial or review blocks, a star rating, 11 trust badges and “10,000+ reviews”.

  • Analytics in place

    Analytics detected: PostHog.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 26 cookies set on arrival

    26

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

  • 50 other companies contacted

    Loading the homepage contacts 50 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 ffs-outlet.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Hulk Form Builder · Upload Lift · Klaviyo Email Marketing Sms · Seo Manager Venntov · Reelfy Videos · Forms · Pushowl · Geolocation Markets Selector · Sovendus App Ffsbeauty · Gift Box Builder · rechargecdn.com · snapchat.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

Framework
Bootstrap
E-commerce
Shopify
Analytics
PostHog
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ffs-outlet.co.uk, including 17 speed issues, 2 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