Website review, no card needed
iclothing.com website review
Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 85 checks
This review found 35 issues worth fixing on iclothing.com, 17 of them high impact, across 85 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
81B- #40,030 of 118,807 reviewed websitesbeats 61%
- #26,707 of 67,436 online storesbeats 54%
- #25,759 of 61,483 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
| Nov 14, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 133 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 139 ms |
| Nov 7, 2026 | 139 ms |
| Nov 14, 2026 | 136 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.5 s
3.0 s
4.4 s
5.9 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Improve image delivery
6.5 s · 1.2 MB1 image could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.
Reduce unused JavaScript
3.5 s · 815 KiBAbout 815 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 576 KiB17 files are served with short cache lifetimes, so returning visitors download them again (576 KiB).
Render-blocking requests
1.0 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.6 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 (hcaptcha.com, Google Tag Manager and segmentify.com and others), adding 3.0 MB and 1.8 s of main-thread time.
hcaptcha.com adds 845 ms
845 mshcaptcha.com costs a phone 845 ms of main-thread work and 1.5 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.
Google Tag Manager adds 358 ms
358 msGoogle Tag Manager costs a phone 358 ms of main-thread work and 522 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 · 83 KiBAbout 83 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 273 ms. During a long task the page ignores taps.
2,132 HTML elements
The page has 2,132 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 141 ms
141 msShopify costs a phone 141 ms of main-thread work and 389 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 JavaScript
150 ms · 23 KiB23 KiB could be saved by minifying JavaScript.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 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: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.6 s
27.6 sYour largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 21.5 s
21.5 sVisually, the page fills in at 21.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.5 s
36.5 sThe page becomes fully interactive after 36.5 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 616 ms
616 msScripts block taps and scrolling for 616 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 121 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 194 ms
194 msReal visitors wait 194 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: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 477 ms
477 msReal visitors wait 477 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 369 requests
7.1 MBYour homepage downloads 7.1 MB in 369 requests on a phone: images 2.4 MB (6), scripts 2.3 MB (68) and other files 1.5 MB (274). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.1 MB1 image is downloaded at several times the size a phone draws it, for example Untitled_design_2970x5280.png at 2,970 px wide, shown at 390 px. Resized copies would save about 1.1 MB.
About 2.0 g of CO₂ per visit
2.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.03 g of CO₂e: 243.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (2 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
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.
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.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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 39 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 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 (297 characters)
Your meta description is 297 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
169 internal links, 8 external
The homepage links to 169 pages on iclothing.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “<img src="//www.iclothing.com/cdn/shop/files/logo-1_150x44.jpg?v=1753092310" width="744" height="217" alt="" data-rimg=…”.
Title: 32 characters
Your title is a healthy 32 characters: “iCLOTHING | Irish Fashion Online”.
Canonical URL set
The canonical URL is https://www.iclothing.com/.
Structured data in place
Structured data found: 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.iclothing.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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,240 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.iclothing.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://www.iclothing.com/collections/sale, https://www.iclothing.com/collections/new-in, https://www.iclothing.com/collections/floral-dresses, https://www.iclothing.com/collections/day-dresses, https://www.iclothing.com/collections/jumper-dresses and https://www.iclothing.com/collections/long-sleeve-dresses and 9 others 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 80 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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to construct 'URL': Invalid URL”.
2 checks passed
Tap targets are thumb-sized
38 of 38 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 243 words
The homepage has only about 243 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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NEW”.
6 calls to action
The homepage has 6 calls to action, for example “Sign up”, “SHOP NEW” and “Shop all”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
25 other companies contacted
Loading the homepage contacts 25 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 iclothing.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
Pandectes Gdpr · Analyzify Ga4 Ads Tracking · Segmentify Micro Analytics · Seguno Popups · Gdpr Cookie Consent · Drop2shop Collect · stamped.io · nfcube.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
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on iclothing.com, including 18 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.