Website review, no card needed

lookhuman.com logo

lookhuman.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 77 checks

This review found 34 issues worth fixing on lookhuman.com, 10 of them high impact, across 77 checks. The most urgent: reduce initial server response time. 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
3.0 s1.2 sJun 6Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.8 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20261.7 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
133 ms91 msJun 6Oct 31128 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 2026108 ms
Jun 13, 2026108 ms
Jun 20, 2026108 ms
Jun 27, 2026108 ms
Jul 4, 2026107 ms
Jul 11, 2026105 ms
Jul 18, 2026106 ms
Jul 25, 2026111 ms
Aug 1, 2026112 ms
Aug 8, 2026117 ms
Aug 15, 2026112 ms
Aug 22, 2026108 ms
Aug 29, 2026104 ms
Sep 5, 202696 ms
Sep 12, 202697 ms
Sep 19, 2026100 ms
Sep 26, 2026104 ms
Oct 3, 2026115 ms
Oct 10, 2026120 ms
Oct 17, 2026127 ms
Oct 24, 2026128 ms
Oct 31, 2026128 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 lookhuman.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lookhuman.com at 0.4 s0.4 s
  2. lookhuman.com at 0.8 s0.8 s
  3. lookhuman.com at 1.1 s1.1 s
  4. lookhuman.com at 1.5 s1.5 s
  5. lookhuman.com at 1.9 s1.9 s
  6. lookhuman.com at 2.3 s2.3 s
  7. lookhuman.com at 2.6 s2.6 s
  8. lookhuman.com at 3.0 s3.0 s

Speed

10 to fix72
  • Reduce initial server response time

    1.3 s

    Reduce initial server response time. Google estimates savings of 1.3 s on a phone.

  • Document request latency

    1.3 s

    The HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused JavaScript

    900 ms · 228 KiB

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

  • Mobile performance score: 72

    72/100

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

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    599 KiB

    23 images could be 599 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Facebook, Google Tag Manager and Clarity and others), adding 1.5 MB and 366 ms of main-thread time.

  • Use efficient cache lifetimes

    285 KiB

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

  • Server response: 1.4 s

    1.4 s

    Your server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • sunfrogimages.com adds 0 ms

    0 ms

    sunfrogimages.com costs a phone 0 ms of main-thread work and 968 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 · 27 KiB

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

  • 8 long tasks on the main thread

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

1 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 831 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

6 to fix67
  • 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.52

    0.52

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

  • Largest Contentful Paint: 6.7 s

    6.7 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Total Blocking Time: 218 ms

    218 ms

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

  • Tap response (INP) got 19% slower for real visitors

    +19%

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

7 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 127 ms

    127 ms

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 521 ms

    521 ms

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

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

    -39%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 109 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 109 requests on a phone: images 969 KiB (35), scripts 908 KiB (34) and stylesheets 59 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 10 images below the first screen load straight away

    10 images further down the page (230 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.4 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8690
  • 218 tap targets too small

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

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 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

3 to fixGoogle 10087
  • Canonical points to another host

    Your canonical URL points to sunfrog.com, not lookhuman.com, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (45 characters)

    Your meta description is only 45 characters: “Shop unique designs by Look Human on SunFrog.”. 70 to 160 characters is enough to sell the click.

  • 283 internal links, 1 external

    The homepage links to 283 pages on lookhuman.com and 1 external page.

5 checks passed
  • One H1 headline

    Your main headline reads: “Look Human”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Look Human Storefront | SunFrog”.

  • 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.sunfrog.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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 (276 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages share 4 titles

    / and /artist/lookhuman/latest all use the title “Look Human Storefront | SunFrog”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    /artist/lookhuman/latest, /artist/lookhuman/trending and /artist/lookhuman/bestsellers use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    /product/gherkin-from-home, /tshirts/gherkin-from-home, /hoodies/gherkin-from-home, /sweatshirts/gherkin-from-home and /product/stand-with-ukraine-flag-colors took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 83 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 97 small tap targets

    97 of 131 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://www.sunfrog.com/products/stand-with-ukraine-flag-colors?ref=artist_lookhuman&lh_entry=https…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 242 words

    The homepage has only about 242 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Start Shopping”.

  • 1 call to action

    The homepage has 1 call to action, for example “Learn more”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 lookhuman.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
Next.js
E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on lookhuman.com, including 16 speed issues, 3 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