Website review, no card needed

iloveugly.com logo

iloveugly.com website review

Visit site (opens in a new tab)Reviewed 6 November 202640 issues · 90 checks

This review found 40 issues worth fixing on iloveugly.com, 14 of them high impact, across 90 checks. The most urgent: page weight: 9.7 MB in 507 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.1 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.5 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
170 ms143 msMay 16Oct 31165 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026159 ms
May 23, 2026160 ms
May 30, 2026161 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026161 ms
Jun 27, 2026158 ms
Jul 4, 2026153 ms
Jul 11, 2026154 ms
Jul 18, 2026153 ms
Jul 25, 2026149 ms
Aug 1, 2026146 ms
Aug 8, 2026146 ms
Aug 15, 2026149 ms
Aug 22, 2026149 ms
Aug 29, 2026152 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026159 ms
Sep 26, 2026161 ms
Oct 3, 2026161 ms
Oct 10, 2026164 ms
Oct 17, 2026164 ms
Oct 24, 2026167 ms
Oct 31, 2026165 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

Full-page screenshot of iloveugly.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iloveugly.com at 1.7 s1.7 s
  2. iloveugly.com at 3.3 s3.3 s
  3. iloveugly.com at 5.0 s5.0 s
  4. iloveugly.com at 6.6 s6.6 s
  5. iloveugly.com at 8.3 s8.3 s
  6. iloveugly.com at 9.9 s9.9 s
  7. iloveugly.com at 11.6 s11.6 s
  8. iloveugly.com at 13.2 s13.2 s

Speed

11 to fix53
  • Main-thread work: 8.3 s

    A phone's processor spends 8.3 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,629 HTML elements

    The page has 3,629 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.6 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Improve image delivery

    250 ms · 1.0 MB

    24 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 1,014 KiB

    52 files are served with short cache lifetimes, so returning visitors download them again (1,014 KiB).

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    600 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Google Tag Manager adds 490 ms

    490 ms

    Google Tag Manager costs a phone 490 ms of main-thread work and 629 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.

  • glasses4u.io adds 194 ms

    194 ms

    glasses4u.io costs a phone 194 ms of main-thread work and 765 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.

  • Shopify adds 219 ms

    219 ms

    Shopify costs a phone 219 ms of main-thread work and 421 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

    150 ms · 61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    150 ms · 20 KiB

    20 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.

  • Minify JavaScript

    84 KiB

    84 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    77 KiB

    Polyfills for old browsers add 77 KiB JavaScript that modern phones do not need.

  • Minify CSS

    20 ms · 2 KiB

    2 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: 19 ms

    19 ms

    Your server sent the HTML in 19 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Time to Interactive: 33.7 s

    33.7 s

    The page becomes fully interactive after 33.7 s. Good is under 3.8 s.

  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 880 ms

    880 ms

    Scripts block taps and scrolling for 880 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 5.9 s

    5.9 s

    Visually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.

  • 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

    +4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 159 ms to 165 ms 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: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 159 ms

    159 ms

    Real visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 787 ms

    787 ms

    Real visitors wait 787 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

    The layout barely moves while loading (CLS 0.011, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 9.7 MB in 507 requests

    9.7 MB

    Your homepage downloads 9.7 MB in 507 requests on a phone: images 4.8 MB (45), scripts 3.3 MB (131) and other files 1.5 MB (313). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    559 KiB

    10 images are downloaded at several times the size a phone draws them, for example 1_08831748-2488-4555-99d6-36dc27b1830d_1500x.jpg at 1,500 px wide, shown at 253 px. Resized copies would save about 559 KiB.

  • 1 image in older formats

    1 image (730 KiB) is 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 2.8 g of CO₂ per visit

    2.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.76 g of CO₂e: 331.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 8992
  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 137 images without alt text

    137 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • 77 links without text

    77 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 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: 48 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

2 to fixGoogle 8587
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 343 internal links, 27 external

    The homepage links to 343 pages on iloveugly.com and 27 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “I Love Ugly US”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Quality Goods for the Independent Mind | I Love Ugly”.

  • Canonical URL set

    The canonical URL is https://www.iloveugly.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://www.iloveugly.com/sitemap.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,644 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.iloveugly.com/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 7 pages without a meta description

    https://www.iloveugly.com/collections/accessories, https://www.iloveugly.com/collections/shop-all-mens, https://www.iloveugly.com/collections/sale-section, https://www.iloveugly.com/collections/ilu-x-basquiat-tops, https://www.iloveugly.com/collections/ilu-x-basquiat-bottoms and https://www.iloveugly.com/collections/ilu-x-basquiat-accessories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.iloveugly.com/pages/bundles and https://www.iloveugly.com/pages/active-bundles use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.iloveugly.com/collections/accessories, https://www.iloveugly.com/collections/shop-all-mens, https://www.iloveugly.com/pages/bundles, https://www.iloveugly.com/collections/new-items, https://www.iloveugly.com/collections/gifting and https://www.iloveugly.com/collections/sale-section 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 148 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

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://www.iloveugly.com/.

  • 15 small tap targets

    15 of 61 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.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Identifier 'setShopifyCurrencyToGeolizr' has already been declared”.

  • 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

3 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 1,217 words of copy

    The homepage carries about 1,217 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop All”, “Shop” and “Subscribe”.

  • 9 short forms

    9 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.

  • 40 cookies set on arrival

    40

    Opening the homepage sets 40 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.

  • 59 other companies contacted

    Loading the homepage contacts 59 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 iloveugly.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 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geoip Country Redirect · Klaviyo Email Marketing Sms · Microsoft Clarity · Pixelpro Easy Pixel Install · Triplewhale · Okendo · I Love Ugly Bundle App · Geolizr · Tapcart Mobile App · Elevar Conversion Tracking · Tiktok Pixel For Adtrace · Ilu Gift With Purchase Free Shipping · Glasson · Upcart · snapchat.com · amazonaws.com · sk-global.biz · retention.com · useamp.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 | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Auckland

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on iloveugly.com, including 16 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25