Website review, no card needed
placesplusfaces.com website review
Visit site (opens in a new tab)Reviewed 10 November 202627 issues · 78 checks
This review found 27 issues worth fixing on placesplusfaces.com, 6 of them high impact, across 78 checks. The most urgent: 2 tap targets too small. 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
82B- #28,256 of 99,641 reviewed websitesbeats 66%
- #18,274 of 54,609 online storesbeats 60%
- #17,647 of 49,565 Shopify storesbeats 57%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 977 ms |
| Aug 1, 2026 | 955 ms |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 80 ms |
| May 30, 2026 | 84 ms |
| Jun 6, 2026 | 70 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 69 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 68 ms |
| Jul 25, 2026 | 64 ms |
| Aug 1, 2026 | 63 ms |
| Aug 8, 2026 | 67 ms |
| Aug 15, 2026 | 71 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 84 ms |
| Sep 12, 2026 | 83 ms |
| Sep 19, 2026 | 80 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 82 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 88 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 87 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
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
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
250 ms · 347 KiB3 images could be 347 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused JavaScript
510 KiBAbout 510 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Privy and others), adding 1.0 MB and 353 ms of main-thread time.
Klaviyo adds 110 ms
110 msKlaviyo costs a phone 110 ms of main-thread work and 308 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.
Shopify adds 58 ms
58 msShopify costs a phone 58 ms of main-thread work and 389 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
150 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
28 KiB7 files are served with short cache lifetimes, so returning visitors download them again (28 KiB).
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 941 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.9
0.9The layout shifts by 0.9 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 80 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 498 ms
498 msReal visitors wait 498 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 98 ms
98 msScripts block the page for only 98 ms while loading. Good is under 200 ms.
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.6 MB in 231 requests
2.6 MBYour homepage downloads 2.6 MB in 231 requests on a phone: scripts 1.1 MB (76), other files 857 KiB (116) and images 637 KiB (29). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.0 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
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
47 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: 47 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (12 characters)
Your title is only 12 characters: “PLACES+FACES”. Between 30 and 65 characters leaves room to say what you do and for whom.
One H1 headline
Your <h1> is empty.
27 internal links, 0 external
The homepage links to 27 pages on placesplusfaces.com and 0 external pages.
6 checks passed
Meta description: 81 characters
Your meta description is 81 characters: “Shop the Online Store & browse through the Blog for Lifestyle brand PLACES+FACES.”.
Canonical URL set
The canonical URL is https://www.placesplusfaces.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://www.placesplusfaces.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.placesplusfaces.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://www.placesplusfaces.com/collections/newstuff, https://www.placesplusfaces.com/collections/womenswear, https://www.placesplusfaces.com/collections/cool-shit, https://www.placesplusfaces.com/collections/magazines, https://www.placesplusfaces.com/blogs/news and https://www.placesplusfaces.com/collections/arsenal-x-places-faces and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.placesplusfaces.com/collections/newstuff/products/cozy-hooded-sweatshirt, whose canonical is https://www.placesplusfaces.com/products/cozy-hooded-sweatshirt. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages with very little text
https://www.placesplusfaces.com/collections/newstuff, https://www.placesplusfaces.com/collections/womenswear, https://www.placesplusfaces.com/collections/cool-shit, https://www.placesplusfaces.com/collections/magazines, https://www.placesplusfaces.com/collections/arsenal-x-places-faces and https://www.placesplusfaces.com/pages/videos have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.placesplusfaces.com/pages/videos took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
5 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
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 10 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
32 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 104 words
The homepage has only about 104 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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “PLACES+FACES: THE BOOK £60.00”.
1 call to action
The homepage has 1 call to action, for example “Sign up”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
16 other companies contacted
Loading the homepage contacts 16 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 placesplusfaces.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Minmaxify Order Limits · Pushowl · Forms · nofraud.com · privy.com · autoketing.org
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
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on placesplusfaces.com, including 11 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.