Website review, no card needed
plouise.co.uk website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 88 checks
This review found 46 issues worth fixing on plouise.co.uk, 17 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
69D- #108,092 of 126,225 reviewed websitesbeats 12%
- #64,534 of 70,400 online storesbeats 7%
- #59,431 of 63,919 Shopify storesbeats 6%
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.6 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 210 ms |
| May 23, 2026 | 221 ms |
| May 30, 2026 | 231 ms |
| Jun 6, 2026 | 235 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 217 ms |
| Jul 11, 2026 | 228 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 236 ms |
| Aug 1, 2026 | 226 ms |
| Aug 8, 2026 | 223 ms |
| Aug 15, 2026 | 227 ms |
| Aug 22, 2026 | 229 ms |
| Aug 29, 2026 | 225 ms |
| Sep 5, 2026 | 216 ms |
| Sep 12, 2026 | 208 ms |
| Sep 19, 2026 | 204 ms |
| Sep 26, 2026 | 210 ms |
| Oct 3, 2026 | 215 ms |
| Oct 10, 2026 | 220 ms |
| Oct 17, 2026 | 227 ms |
| Oct 24, 2026 | 238 ms |
| Oct 31, 2026 | 249 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
Speed
Improve image delivery
2.0 s · 6.3 MB18 images could be 6.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 10.0 s
A phone's processor spends 10.0 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,782 HTML elements
The page has 6,782 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
750 ms · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Shopify and wingify.net and others), adding 3.8 MB and 1.9 s of main-thread time.
Google CDN adds 587 ms
587 msGoogle CDN costs a phone 587 ms of main-thread work and 1.5 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.
Use efficient cache lifetimes
300 ms · 333 KiB28 files are served with short cache lifetimes, so returning visitors download them again (333 KiB).
Shopify adds 517 ms
517 msShopify costs a phone 517 ms of main-thread work and 935 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
450 ms · 158 KiBAbout 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
rebuyengine.com adds 152 ms
152 msrebuyengine.com costs a phone 152 ms of main-thread work and 419 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 142 ms
142 msKlaviyo costs a phone 142 ms of main-thread work and 340 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.
LoyaltyLion adds 72 ms
72 msLoyaltyLion costs a phone 72 ms of main-thread work and 368 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Legacy JavaScript
65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need.
Minify JavaScript
39 KiB39 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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 34 ms
34 msYour server sent the HTML in 34 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.
Largest Contentful Paint: 20.1 s
20.1 sYour largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop Christmas at P.Louise”.
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 60.2 s
60.2 sThe page becomes fully interactive after 60.2 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 247 ms
247 msReal visitors wait 247 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 545 ms
545 msScripts block taps and scrolling for 545 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 210 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 429 ms
429 msReal visitors wait 429 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.7 MB in 519 requests
23.7 MBYour homepage downloads 23.7 MB in 519 requests on a phone: images 8.8 MB (165), media 8.5 MB (4) and scripts 4.1 MB (174). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 17.3 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
13.8 MB2 images are downloaded at several times the size a phone draws them, for example Christmas_CTA_-_Black_-_Shop_Now_1bd00be0-47a5-497b-b381-60e at 2,000 px wide, shown at 240 px. Resized copies would save about 13.8 MB.
6 images in older formats
6 images (17.6 MB) 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.
5 images below the first screen load straight away
5 images further down the page (12.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.7 g of CO₂ per visit
6.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.73 g of CO₂e: 807.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 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.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “P.Louise Cosmetics | Makeup, Skincare & Beauty Products – P. Louise Cosmetics”.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
453 internal links, 0 external
The homepage links to 453 pages on plouise.co.uk and 0 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://plouise.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, OnlineStore, 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://plouise.co.uk/sitemap.xml.
AI search readiness
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,154 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://plouise.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://plouise.co.uk/collections/christmas, https://plouise.co.uk/collections/best-sellers, https://plouise.co.uk/products/p-louise-bad-bitch-energy-lip-duo, https://plouise.co.uk/pages/christmas-gift-guide, https://plouise.co.uk/collections/wonderful-world-of-p-louise-advent-calendar and https://plouise.co.uk/collections/makeup-beauty-stocking-fillers and 9 others 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 157 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://cdn.klaviyomail.com/company/XxqZhy/images/18d14317-17ef-475a-bcf8-1d15aa3ab01b.png.
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_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
57 of 61 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 523 words of copy
The homepage carries about 523 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Christmas Is Here! Shop Now” and “Shop Christmas”.
40 calls to action
The homepage has 40 calls to action, for example “Christmas Is Here! Shop Now”, “Shop all 🎠 Christmas” and “Shop By Budget”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
52 other companies contacted
Loading the homepage contacts 52 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 plouise.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 32 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Schema Plus For Seo · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Ta Mappy Store Locator Maps · Wingify · Tapcart Mobile App · Rebuy Personalization Engine · Attentive · Sortd Merchandiser · Regios Discounts · Ex Show Variants · Triplewhale · Omniconvert Explore · Langshop · Trymry · Variants As Separate Products · Announcement Bar Maker By Apphero · Aftersell · Bookeasy · Digital Appointments · Gdpr Backpack · rechargecdn.com · attn.tv · loox.io · rakutenadvertising.io · 9gtb.com · googleapis.com · rebuyengine.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
- 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 plouise.co.uk, including 24 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.