Website review, no card needed

wearelabels.com logo

wearelabels.com website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 76 checks

This review found 26 issues worth fixing on wearelabels.com, 7 of them high impact, across 76 checks. The most urgent: 2 linked pages are broken. 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
1.0 s688 msApr 25Oct 10860 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026726 ms
May 2, 2026755 ms
May 9, 2026738 ms
May 16, 2026761 ms
May 23, 2026788 ms
May 30, 2026784 ms
Jun 6, 2026801 ms
Jun 13, 2026792 ms
Jun 20, 2026831 ms
Jun 27, 2026881 ms
Jul 4, 2026901 ms
Jul 11, 2026966 ms
Jul 18, 2026934 ms
Jul 25, 2026943 ms
Aug 1, 2026979 ms
Aug 8, 2026932 ms
Aug 15, 2026939 ms
Aug 22, 2026920 ms
Aug 29, 2026860 ms
Sep 5, 2026857 ms
Sep 12, 2026863 ms
Sep 19, 2026877 ms
Sep 26, 2026890 ms
Oct 3, 2026883 ms
Oct 10, 2026860 ms
Real-visitor tap response (INP)75th percentile, phones
94 ms77 msApr 25Oct 1080 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202680 ms
May 2, 202679 ms
May 9, 202684 ms
May 16, 202685 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202685 ms
Jun 13, 202687 ms
Jun 20, 202688 ms
Jun 27, 202689 ms
Jul 4, 202692 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202684 ms
Aug 1, 202684 ms
Aug 8, 202684 ms
Aug 15, 202684 ms
Aug 22, 202686 ms
Aug 29, 202686 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202683 ms
Oct 3, 202681 ms
Oct 10, 202680 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 wearelabels.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wearelabels.com at 0.9 s0.9 s
  2. wearelabels.com at 1.7 s1.7 s
  3. wearelabels.com at 2.6 s2.6 s
  4. wearelabels.com at 3.4 s3.4 s
  5. wearelabels.com at 4.3 s4.3 s
  6. wearelabels.com at 5.1 s5.1 s
  7. wearelabels.com at 6.0 s6.0 s
  8. wearelabels.com at 6.8 s6.8 s

Speed

5 to fix64
  • Improve image delivery

    350 ms · 1.4 MB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 41 KiB

    About 41 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    350 ms · 31 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).

  • Main-thread work: 2.3 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 252 KiB and 245 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 27 KiB

    About 27 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.

  • Legacy JavaScript

    150 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 99 but mobile only 64. 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: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 11.8 s

    11.8 s

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

  • Time to Interactive: 12.2 s

    12.2 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

    The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.5 s

    5.5 s

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

  • Tap response (INP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 80 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 18% slower for real visitors

    +18%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 84 ms

    84 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 535 ms

    535 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 58 ms

    58 ms

    Scripts block the page for only 58 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 219 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 219 requests on a phone: images 1.9 MB (16), other files 1,002 KiB (145) and scripts 397 KiB (52). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (107 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 0.9 g of CO₂ per visit

    0.94 g

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

2 checks passed
  • 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

4 to fixGoogle 9395
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 120 links without text

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

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

    All page content should be contained by landmarks: 9 elements on the page fail 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.

2 checks passed
  • Every image has alt text

    All 131 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10080
  • Title is short (29 characters)

    Your title is only 29 characters: “We Are Labels – We Are Labels”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “BRANDS”). One clear main headline is easier for people and search engines.

  • Meta description is long (199 characters)

    Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 35 internal links, 5 external

    The homepage links to 35 pages on wearelabels.com and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://wearelabels.com/.

  • Structured data in place

    Structured data found: 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://wearelabels.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://wearelabels.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://wearelabels.com/collections/wal and https://wearelabels.com/pages/jobs, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 5 pages without a meta description

    https://wearelabels.com/pages/terms-conditions, https://wearelabels.com/pages/privacy-policy, https://wearelabels.com/pages/cookie-policy, https://wearelabels.com/pages/help-center and https://wearelabels.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://wearelabels.com/pages/brands, https://wearelabels.com/pages/stores, https://wearelabels.com/pages/about-us, https://wearelabels.com/pages/privacy-policy, https://wearelabels.com/pages/cookie-policy and https://wearelabels.com/pages/contact and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://wearelabels.com/pages/brands, https://wearelabels.com/pages/contact and https://wearelabels.com/collections/all have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • 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 9 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    128 of 131 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • 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 203 words

    The homepage has only about 203 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.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP WOMEN”, “SHOP ONLINE” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.

  • 8 cookies set on arrival

    8

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 wearelabels.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
Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on wearelabels.com, including 9 speed issues, 4 SEO issues and 4 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