Website review, no card needed
facethefuture.co.uk website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 95 checks
This review found 40 issues worth fixing on facethefuture.co.uk, 14 of them high impact, across 95 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #27,398 of 119,682 reviewed websitesbeats 72%
- #18,051 of 67,864 online storesbeats 67%
- #17,498 of 61,860 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 123 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 231 ms |
| Jun 6, 2026 | 343 ms |
| Jun 13, 2026 | 418 ms |
| Jun 20, 2026 | 360 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 255 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 192 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 330 ms |
| Aug 15, 2026 | 391 ms |
| Aug 22, 2026 | 344 ms |
| Aug 29, 2026 | 377 ms |
| Sep 5, 2026 | 348 ms |
| Sep 12, 2026 | 393 ms |
| Sep 19, 2026 | 540 ms |
| Sep 26, 2026 | 587 ms |
| Oct 3, 2026 | 478 ms |
| Oct 10, 2026 | 381 ms |
| Oct 17, 2026 | 93 ms |
| Oct 24, 2026 | 86 ms |
| Oct 31, 2026 | 84 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,264 HTML elements
The page has 5,264 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 (Google Tag Manager, Shopify and minmaxify.com and others), adding 3.0 MB and 2.0 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 539 KiB9 images could be 539 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 726 ms
726 msGoogle Tag Manager costs a phone 726 ms of main-thread work and 653 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.
Render-blocking requests
750 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Shopify adds 470 ms
470 msShopify costs a phone 470 ms of main-thread work and 1.9 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.
Reduce unused JavaScript
615 KiBAbout 615 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 432 KiB23 files are served with short cache lifetimes, so returning visitors download them again (432 KiB).
minmaxify.com adds 419 ms
419 msminmaxify.com costs a phone 419 ms of main-thread work and 15 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 283 ms. During a long task the page ignores taps.
cloudfront.net adds 207 ms
207 mscloudfront.net costs a phone 207 ms of main-thread work and 299 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
150 ms · 35 KiBAbout 35 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 24.6 s
24.6 sThe page becomes fully interactive after 24.6 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user TTFB: 876 ms
876 msReal visitors wait 876 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 83 ms
83 msReal visitors wait 83 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 341 requests
6.5 MBYour homepage downloads 6.5 MB in 341 requests on a phone: images 3.0 MB (77), scripts 1.8 MB (92) and other files 1.3 MB (124). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Winter-Radiance-Edit-Launch-Mobile_d8f55d59-055b-433c-8a21-8 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).
4 images far larger than shown
399 KiB4 images are downloaded at several times the size a phone draws them, for example SS_Wristband_01B.jpg at 2,183 px wide, shown at 50 px. Resized copies would save about 399 KiB.
4 images in older formats
4 images (280 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.8 g of CO₂ per visit
1.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.84 g of CO₂e: 221.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
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.
Orphan list items
Some list items are not inside a list.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and 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. (7 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (197 characters)
Your meta description is 197 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.facethefuture.co.uk)”.
875 internal links, 32 external
The homepage links to 875 pages on facethefuture.co.uk and 32 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Face the Future: Buy Skincare Products & Cosmeceuticals Online”.
Title: 63 characters
Your title is a healthy 63 characters: “Buy Skincare Products & Cosmeceuticals Online | Face the Future”.
Canonical URL set
The canonical URL is https://us.facethefuture.store/.
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://us.facethefuture.store/sitemap.xml.
AI search readiness
No llms.txt
There is no https://us.facethefuture.store/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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,658 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
7 checks passed
Linked pages load
2 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 2 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 2 pages that loaded have a <title>.
Best practices
5 broken images
5 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0419/5447/6194/files/ChatGPTImageAug25_2026_12_59_37PM.png?v=1787659207.
52 small tap targets
52 of 126 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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.
About 1,461 words of copy
The homepage carries about 1,461 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download Our App” and “Shop”.
56 calls to action
The homepage has 56 calls to action, for example “Download Our App”, “Shop” and “Christmas Gift Shop”.
41 short forms
41 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 10 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
35 cookies set on arrival
35Opening the homepage sets 35 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.
54 other companies contacted
Loading the homepage contacts 54 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 facethefuture.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Attentive · Minmaxify Order Limits · Freegifts · Swym Wishlist Plus · rakuten.com · cloudfront.net · gorgias.chat · bogos.io · rakutenadvertising.io · 9gtb.com · bazaarvoice.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Normanton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on facethefuture.co.uk, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.