Website review, no card needed
silkology.co.uk website review
Visit site (opens in a new tab)Reviewed 20 November 202629 issues · 69 checks
This review found 29 issues worth fixing on silkology.co.uk, 11 of them high impact, across 69 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.2 s · 400 KiBAbout 400 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 266 KiB11 files are served with short cache lifetimes, so returning visitors download them again (266 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 145 KiBAbout 145 KiB of CSS is downloaded but never applied 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 (POWr, powrcdn.com and Shopify and others), adding 822 KiB and 541 ms of main-thread time.
powrcdn.com adds 233 ms
233 mspowrcdn.com costs a phone 233 ms of main-thread work and 609 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.
POWr adds 276 ms
276 msPOWr costs a phone 276 ms of main-thread work and 59 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
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
21 KiB1 image could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 741 ms of it running JavaScript. That is comfortably low.
Server response: 40 ms
40 msYour server sent the HTML in 40 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.1 s
12.1 sYour largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 12.1 s
12.1 sThe page becomes fully interactive after 12.1 s. Good is under 3.8 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 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.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 99 ms
99 msScripts block the page for only 99 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 159 requests
2.5 MBYour homepage downloads 2.5 MB in 159 requests on a phone: other files 793 KiB (100), images 763 KiB (10) and scripts 725 KiB (36). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.6 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
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 4 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 (315 characters)
Your meta description is 315 characters; Google truncates after about 160, so the end of your pitch is cut.
28 internal links, 3 external
The homepage links to 28 pages on silkology.co.uk and 3 external pages.
7 checks passed
One H1 headline
Your main headline reads: “<img src="//www.silkology.co.uk/cdn/shop/files/WEB-LOGO_250x.png?v=1613545975" srcset="//www.silkology.co.uk/cdn/shop/f…”.
Title: 54 characters
Your title is a healthy 54 characters: “Luxury Silk hair & beauty care products. – Silkologyuk”.
Canonical URL set
The canonical URL is https://www.silkology.co.uk/.
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.silkology.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (634 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.silkology.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.silkology.co.uk/products/rose-pink-pillowcase, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.silkology.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.silkology.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.silkology.co.uk/customer_authentication/redirect, https://www.silkology.co.uk/collections/all and https://www.silkology.co.uk/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.silkology.co.uk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.silkology.co.uk/pages/trade-accounts-wholesale, https://www.silkology.co.uk/pages/contact-us and https://www.silkology.co.uk/pages/pr-enquiries 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
2 checks passed
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.
Best practices
7 small tap targets
7 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “POWr popup(id=27191527) cannot be rendered: The app is not active”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 19 testimonial or review blocks. 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 567 words of copy
The homepage carries about 567 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop”, “Contact us” and “Subscribe”.
2 short forms
2 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 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
12 other companies contacted
Loading the homepage contacts 12 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 silkology.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Fontify · powr.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 29 issues on silkology.co.uk, including 12 speed issues, 1 SEO issue 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.