Website review, no card needed
alcltd.com website review
Visit site (opens in a new tab)Reviewed 18 October 202644 issues · 87 checks
This review found 44 issues worth fixing on alcltd.com, 19 of them high impact, across 87 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
74C- #86,762 of 124,214 reviewed websitesbeats 26%
- #54,521 of 69,818 online storesbeats 18%
- #51,215 of 63,493 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.4 s |
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 195 ms |
| May 2, 2026 | 186 ms |
| May 9, 2026 | 179 ms |
| May 16, 2026 | 172 ms |
| May 23, 2026 | 173 ms |
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 157 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 154 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
Reduce unused JavaScript
3.0 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.2 s · 690 KiB42 files are served with short cache lifetimes, so returning visitors download them again (690 KiB).
Render-blocking requests
1.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 55). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.7 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 (Google Tag Manager, Klaviyo and Facebook and others), adding 3.1 MB and 1.6 s of main-thread time.
Improve image delivery
900 ms · 622 KiB7 images could be 622 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Reduce unused CSS
900 ms · 133 KiBAbout 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 496 ms
496 msGoogle Tag Manager costs a phone 496 ms of main-thread work and 540 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.
Minify CSS
450 ms · 29 KiB29 KiB could be saved by minifying CSS.
Legacy JavaScript
350 ms · 111 KiBPolyfills for old browsers add 111 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Klaviyo adds 275 ms
275 msKlaviyo costs a phone 275 ms of main-thread work and 695 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 291 ms. During a long task the page ignores taps.
Shopify adds 178 ms
178 msShopify costs a phone 178 ms of main-thread work and 1.1 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.
Minify JavaScript
23 KiB23 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 55 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 10 ms
10 msYour server sent the HTML in 10 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: 0.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 25.4 s
25.4 sYour largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 39.1 s
39.1 sThe page becomes fully interactive after 39.1 s. Good is under 3.8 s.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 864 ms
864 msScripts block taps and scrolling for 864 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 904 ms
904 msReal visitors wait 904 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.166
0.166The layout shifts by 0.166 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 195 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.5 MB in 468 requests
6.5 MBYour homepage downloads 6.5 MB in 468 requests on a phone: scripts 3.7 MB (166), images 1.3 MB (34) and other files 1.1 MB (237). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
585 KiB6 images are downloaded at several times the size a phone draws them, for example MARTASKIRT-BLACK_5d110387-286a-4eca-9103-46afbf2a0334.jpg at 2,000 px wide, shown at 143 px. Resized copies would save about 585 KiB.
An image on the first screen is lazy-loaded
NAV_knits_1b714b85-e841-4516-bd00-d132635eada7.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (381 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.
About 1.8 g of CO₂ per visit
1.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 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 (312 characters)
Your meta description is 312 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
81 internal links, 5 external
The homepage links to 81 pages on alcltd.com and 5 external pages.
7 checks passed
One H1 headline
Your main headline reads: “ALC LTD”.
Title: 58 characters
Your title is a healthy 58 characters: “A.L.C. - Official Site | Designer Clothing and Accessories”.
Canonical URL set
The canonical URL is https://alcltd.com/.
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://alcltd.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 (262 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://alcltd.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://alcltd.com/pages/email-sms, https://alcltd.com/collections/clothing and https://alcltd.com/collections/denim have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://alcltd.com/collections/clothing, whose canonical is https://alcltd.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://alcltd.com/collections/new-arrivals, https://alcltd.com/pages/email-sms and https://alcltd.com/collections/clothing 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 53 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
16 small tap targets
16 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 207 words
The homepage has only about 207 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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “New Styles Added to Sale. Shop Now.” and “SHOP”.
3 calls to action
The homepage has 3 calls to action, for example “New Arrivals. Shop Now.”, “Shop” and “Shop All Sale”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Segment and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, FullStory, Google Ads, Google Tag Manager and Klaviyo and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (measured from a US location before any click).
71 other companies contacted
Loading the homepage contacts 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 alcltd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Segment | FullStory
Company
- Headquarters
- Los Angeles
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 alcltd.com, including 23 speed issues, 3 SEO issues and 2 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.