Website review, no card needed
lazyoaf.co.uk website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 79 checks
This review found 37 issues worth fixing on lazyoaf.co.uk, 14 of them high impact, across 79 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
64D- #109,621 of 116,487 reviewed websitesbeats 5%
- #64,943 of 66,776 online storesbeats 2%
- #59,579 of 60,929 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 418 ms |
| May 30, 2026 | 365 ms |
| Jun 6, 2026 | 282 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 195 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 178 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 164 ms |
| Oct 24, 2026 | 171 ms |
| Oct 31, 2026 | 179 ms |
| Nov 7, 2026 | 180 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.2 s
2.3 s
3.5 s
4.7 s
5.8 s
7.0 s
8.1 s
9.3 s
Speed
Improve image delivery
1.9 s · 683 KiB7 images could be 683 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.9 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 21
21/100Your mobile performance score is 21. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (negate.io, Klaviyo and cloudfront.net and others), adding 1.6 MB and 1.8 s of main-thread time.
negate.io adds 838 ms
838 msnegate.io costs a phone 838 ms of main-thread work and 40 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 JavaScript
300 ms · 529 KiBAbout 529 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
504 KiB13 files are served with short cache lifetimes, so returning visitors download them again (504 KiB).
Klaviyo adds 337 ms
337 msKlaviyo costs a phone 337 ms of main-thread work and 635 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
300 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,691 HTML elements
The page has 2,691 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.
cloudfront.net adds 221 ms
221 mscloudfront.net costs a phone 221 ms of main-thread work and 314 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
200 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
83 KiB83 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 77 ms
77 msYour server sent the HTML in 77 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.
Real-user CLS: 1.00
1.00For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.5 s
11.5 sYour largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 1.215
1.215The layout shifts by 1.215 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 619 ms
619 msScripts block taps and scrolling for 619 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 201 ms
201 msReal visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
5 checks passed
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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 372 ms
372 msReal visitors wait 372 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 54% faster for real visitors
-54%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 418 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 58% faster for real visitors
-58%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.1 MB in 419 requests
5.1 MBYour homepage downloads 5.1 MB in 419 requests on a phone: scripts 1.9 MB (180), images 1.9 MB (23) and other files 1.0 MB (180). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (740 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.
3 images below the first screen load straight away
3 images further down the page (467 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Shop Gifting”, “Shop Women's Dresses” and “Two-in-One”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
381 internal links, 15 external
The homepage links to 381 pages on lazyoaf.co.uk and 15 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Lazy Oaf create irreverent streetwear clothing for men and women, inspired by youth nostalgia, teenage rebellion and a …”.
Title: 51 characters
Your title is a healthy 51 characters: “Men's and Women's Independent Streetwear I Lazy Oaf”.
Canonical URL set
The canonical URL is https://www.lazyoaf.com/.
Structured data in place
Structured data found: Organization.
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.lazyoaf.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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 (950 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.lazyoaf.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.lazyoaf.com/collections/all-1, https://www.lazyoaf.com/collections/all-shirts and https://www.lazyoaf.com/collections/bottoms have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.lazyoaf.com/pages/oafy has 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 116 found) and read each the way a search engine does.
5 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.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: $ is not a function”.
2 checks passed
Tap targets are thumb-sized
24 of 25 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 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 177 words
The homepage has only about 177 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Archive” and “SHOP NOW”.
55 calls to action
The homepage has 55 calls to action, for example “Shop”, “Shop all New In” and “Shop all Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
30 other companies contacted
Loading the homepage contacts 30 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 lazyoaf.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
C Hub Customer Accounts · Personizely A B Testing Cro · Klaviyo Email Marketing Sms · Protectmyorder · Foursixty Shopify App · verifypass.com · b-cdn.net · locationinventory.info · cloudfront.net · esc-apps-cdn.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on lazyoaf.co.uk, including 22 speed issues, 2 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.