Website review, no card needed
lcofficial.com website review
Visit site (opens in a new tab)Reviewed 27 October 202644 issues · 95 checks
This review found 44 issues worth fixing on lcofficial.com, 17 of them high impact, across 95 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
Site score
68D- #106,077 of 120,787 reviewed websitesbeats 10%
- #63,747 of 68,384 online storesbeats 5%
- #58,756 of 62,314 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 170 ms |
| May 16, 2026 | 182 ms |
| May 23, 2026 | 193 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 198 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 215 ms |
| Aug 22, 2026 | 234 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 255 ms |
| Sep 12, 2026 | 295 ms |
| Sep 19, 2026 | 292 ms |
| Sep 26, 2026 | 378 ms |
| Oct 3, 2026 | 311 ms |
| Oct 10, 2026 | 295 ms |
| Oct 17, 2026 | 293 ms |
| Oct 24, 2026 | 256 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.8 s
3.5 s
5.3 s
7.1 s
8.9 s
10.6 s
12.4 s
14.2 s
Speed
Reduce unused JavaScript
2.6 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Main-thread work: 10.9 s
A phone's processor spends 10.9 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 2.9 MB and 2.1 s of main-thread time.
Use efficient cache lifetimes
900 ms · 661 KiB21 files are served with short cache lifetimes, so returning visitors download them again (661 KiB).
Google Tag Manager adds 674 ms
674 msGoogle Tag Manager costs a phone 674 ms of main-thread work and 567 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
700 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Reduce unused CSS
600 ms · 94 KiBAbout 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Shopify adds 458 ms
458 msShopify costs a phone 458 ms of main-thread work and 681 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 424 ms. During a long task the page ignores taps.
Klaviyo adds 276 ms
276 msKlaviyo costs a phone 276 ms of main-thread work and 514 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.
2,971 HTML elements
The page has 2,971 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Facebook adds 250 ms
250 msFacebook costs a phone 250 ms of main-thread work and 291 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 CDN adds 117 ms
117 msGoogle CDN costs a phone 117 ms of main-thread work and 379 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 · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
152 KiB2 images could be 152 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 28 ms
28 msYour server sent the HTML in 28 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 LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 17.6 s
17.6 sYour largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Soft Brown”.
Time to Interactive: 36.0 s
36.0 sThe page becomes fully interactive after 36.0 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Real-user INP: 331 ms
331 msReal visitors wait 331 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 56% slower for real visitors
+56%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 170 ms to 256 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 45% slower for real visitors
+45%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
2 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 458 requests
7.5 MBYour homepage downloads 7.5 MB in 458 requests on a phone: scripts 3.6 MB (145), images 2.2 MB (70) and other files 1.1 MB (218). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.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
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
44 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: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (2 characters)
Your title is only 2 characters: “LC”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
249 internal links, 6 external
The homepage links to 249 pages on lcofficial.com and 6 external pages.
6 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Refined everyday style. Modern designs that allow you to look and feel good. Rooted in the UAE and built around quality…”.
Canonical URL set
The canonical URL is https://lcofficial.com/.
Structured data in place
Structured data found: Organization.
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://lcofficial.com/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 (800 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lcofficial.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a meta description
https://lcofficial.com/collections/shop-all-womens, https://lcofficial.com/collections/flexluxe, https://lcofficial.com/collections/womens-adapt, https://lcofficial.com/collections/silk-touch-knit-2 and https://lcofficial.com/collections/cotton-poplin-2 use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://lcofficial.com/collections/shop-all-womens, https://lcofficial.com/collections/new-arrivals, https://lcofficial.com/collections/active, https://lcofficial.com/collections/lounge and https://lcofficial.com/collections/tops have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://lcofficial.com/collections/lounge took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 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://bat.bing.com/action/0?ti=134607143&Ver=2&mid=28d4ef8c-b863-4092-8bc7-78cdd6b6330a&bo=1&sid=91d27e60d21811f19f0fa1b9d3cd1835&vid=91d2c030d21811f192306504d58e8019&vids=1&msclkid=N&pi=918639831&l.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
44 of 51 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.
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 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 387 words of copy
The homepage carries about 387 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
24 calls to action
The homepage has 24 calls to action, for example “Shop By Collection”, “Shop By Style” and “Register / Login”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 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.
34 cookies set on arrival
34Opening the homepage sets 34 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.
65 other companies contacted
Loading the homepage contacts 65 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 lcofficial.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on lcofficial.com, including 26 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.