Website review, no card needed
likelondon.com website review
Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 83 checks
This review found 28 issues worth fixing on likelondon.com, 6 of them high impact, across 83 checks. The most urgent: page weight: 5.2 MB in 340 requests. 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
87B- #8,280 of 119,769 reviewed websitesbeats 90%
- #4,797 of 67,907 online storesbeats 89%
- #4,650 of 61,894 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 758 ms |
| May 23, 2026 | 759 ms |
| May 30, 2026 | 754 ms |
| Jun 6, 2026 | 756 ms |
| Jun 13, 2026 | 753 ms |
| Jun 20, 2026 | 753 ms |
| Jun 27, 2026 | 754 ms |
| Jul 4, 2026 | 765 ms |
| Jul 11, 2026 | 785 ms |
| Jul 18, 2026 | 810 ms |
| Jul 25, 2026 | 843 ms |
| Aug 1, 2026 | 870 ms |
| Aug 8, 2026 | 885 ms |
| Aug 15, 2026 | 908 ms |
| Aug 22, 2026 | 919 ms |
| Aug 29, 2026 | 926 ms |
| Sep 5, 2026 | 930 ms |
| Sep 12, 2026 | 923 ms |
| Sep 19, 2026 | 904 ms |
| Sep 26, 2026 | 886 ms |
| Oct 3, 2026 | 860 ms |
| Oct 10, 2026 | 836 ms |
| Oct 17, 2026 | 826 ms |
| Oct 24, 2026 | 822 ms |
| Oct 31, 2026 | 808 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 123 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 116 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 111 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
1.3 MB22 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.5 MB and 585 ms of main-thread time.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 993 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
354 KiBAbout 354 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 181 ms
181 msShopify costs a phone 181 ms of main-thread work and 813 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.
Google Tag Manager adds 215 ms
215 msGoogle Tag Manager costs a phone 215 ms of main-thread work and 333 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.
1,958 HTML elements
The page has 1,958 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
260 ms · 48 KiBAbout 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
53 KiB16 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
Legacy JavaScript
51 KiBPolyfills for old browsers add 51 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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
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
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 456 ms
456 msReal visitors wait 456 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 5.2 MB in 340 requests
5.2 MBYour homepage downloads 5.2 MB in 340 requests on a phone: images 2.8 MB (33), scripts 1.2 MB (163) and other files 1,016 KiB (117). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.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
6 tap targets too small
6 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.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 checks passed
Every image has alt text
All 106 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 3 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 (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
304 internal links, 4 external
The homepage links to 304 pages on likelondon.com and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “LikeLondon.com”.
Title: 34 characters
Your title is a healthy 34 characters: “LikeLondon - lækkert tøj på nettet”.
Canonical URL set
The canonical URL is https://likelondon.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://likelondon.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,021 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://likelondon.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 135 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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 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 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 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 664 words of copy
The homepage carries about 664 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: “SHOP HER”.
11 calls to action
The homepage has 11 calls to action, for example “SHOP HER”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before 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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
33 other companies contacted
Loading the homepage contacts 33 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 likelondon.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Sc Easy Redirects · Avada Seo Suite · Eg Auto Add To Cart · Hidepay · Stape Remix · viaads.dk · sprii.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 28 issues on likelondon.com, including 12 speed issues, 2 SEO issues and 5 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.