Website review, no card needed

levinsfactory.com logo

levinsfactory.com website review

Visit site (opens in a new tab)Reviewed 12 November 202625 issues · 73 checks

This review found 25 issues worth fixing on levinsfactory.com, 7 of them high impact, across 73 checks. The most urgent: improve image delivery. 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.3 s995 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.0 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
119 ms84 msMay 23Nov 791 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202692 ms
Jun 13, 202691 ms
Jun 20, 202692 ms
Jun 27, 202690 ms
Jul 4, 202696 ms
Jul 11, 2026103 ms
Jul 18, 2026107 ms
Jul 25, 2026111 ms
Aug 1, 2026109 ms
Aug 8, 2026115 ms
Aug 15, 2026103 ms
Aug 22, 2026103 ms
Aug 29, 2026101 ms
Sep 5, 202694 ms
Sep 26, 202689 ms
Oct 10, 2026105 ms
Oct 17, 202693 ms
Oct 24, 202688 ms
Oct 31, 202689 ms
Nov 7, 202691 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 levinsfactory.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix75
  • Improve image delivery

    1.0 s · 464 KiB

    10 images could be 464 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    700 ms

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

  • 1,781 HTML elements

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

  • Reduce unused JavaScript

    150 ms · 88 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Shopify and shop.app and others), adding 113 KiB and 60 ms of main-thread time.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    6 KiB

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

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

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 9.8 s

    9.8 s

    Your largest element takes 9.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: 9.9 s

    9.9 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

10 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: 1.2 s

    1.2 s

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

  • Real-user INP: 93 ms

    93 ms

    Real visitors wait 93 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: 493 ms

    493 ms

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 210 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 210 requests on a phone: images 1.2 MB (22), other files 931 KiB (124) and scripts 211 KiB (37). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    O1CN01bDWcHK1zT3kt1Rg0n__1761286714_550x.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).

  • About 0.7 g of CO₂ per visit

    0.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 83.9 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

3 to fixGoogle 9796
  • 4 tap targets too small

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

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

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • One H1 headline

    Your <h1> is empty.

  • 113 internal links, 10 external

    The homepage links to 113 pages on levinsfactory.com and 10 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Levin‘s Factory公式ストアではアメカジレトロをメインに、あなたのファッションライフを支えるアイテムを紹介しているオリジナルとセレクトのショップです。ど派手な柄シャツから渋カッコイイ商品まで多数の商品を随時アップしていきます。…”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Levin`s Factory公式ストア | Levin`s Factory”.

  • Canonical URL set

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

  • 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://levinsfactory.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 (312 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix55
  • 1 page without a title

    https://levinsfactory.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://levinsfactory.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://levinsfactory.com/products/levin-sfactory-%E3%82%AA%E3%83%BC%E3%83%97%E3%83%B3%E3%82%A8%E3%83%B3%E3%83%89t%E3%82%B7%E3%83%A3%E3%83%84-4 and https://levinsfactory.com/products/levin-sfactory-%E3%82%AA%E3%83%BC%E3%83%97%E3%83%B3%E3%82%A8%E3%83%B3%E3%83%89t%E3%82%B7%E3%83%A3%E3%83%84-3 all use the title “Levin‘sFactory オープンエンドTシャツ | Levin`s Factory”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://levinsfactory.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://levinsfactory.com/collections/%E5%B0%8F%E7%89%A9%E7%B3%BB, whose canonical is https://levinsfactory.com/collections/%e5%b0%8f%e7%89%a9%e7%b3%bb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://levinsfactory.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://levinsfactory.com/collections/%E5%B0%8F%E7%89%A9%E7%B3%BB, https://levinsfactory.com/collections/%E3%82%B8%E3%83%BC%E3%83%B3%E3%82%BA, https://levinsfactory.com/pages/guide, https://levinsfactory.com/blogs/%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9, https://levinsfactory.com/products/levin-sfactory-%E3%82%AA%E3%83%BC%E3%83%97%E3%83%B3%E3%82%A8%E3%83%B3%E3%83%89t%E3%82%B7%E3%83%A3%E3%83%84-4 and https://levinsfactory.com/products/levin-sfactory-%E3%82%AA%E3%83%BC%E3%83%97%E3%83%B3%E3%82%A8%E3%83%B3%E3%83%89t%E3%82%B7%E3%83%A3%E3%83%84-3 and 2 others 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

    33 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: a star rating. 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.

  • Only about 157 words

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

2 checks passed
  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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 levinsfactory.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seowill Sticky Cart · Page Speed Booster · Quick Link

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on levinsfactory.com, including 6 speed issues, 2 SEO issues and 5 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