Website review, no card needed

qlomono.com logo

qlomono.com website review

Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 96 checks

This review found 31 issues worth fixing on qlomono.com, 6 of them high impact, across 96 checks. The most urgent: no DMARC policy. 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

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

How it loaded on a phone

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

qlomono.com does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix74
  • Reduce unused JavaScript

    600 ms · 557 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    400 ms

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

  • Main-thread work: 2.7 s

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

  • 1,758 HTML elements

    The page has 1,758 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 (firebaseapp.com, Shopify and chaty.app and others), adding 217 KiB and 235 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 52 KiB

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

  • Reduce unused CSS

    150 ms · 21 KiB

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

  • 4 long tasks on the main thread

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

  • Improve image delivery

    145 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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: 7 ms

    7 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 6.6 s

    6.6 s

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

  • Time to Interactive: 6.6 s

    6.6 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Total Blocking Time: 173 ms

    173 ms

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

  • Speed Index: 3.1 s

    3.1 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 2 images below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.49 g

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

3 checks passed
  • Page weight: 1.7 MB in 168 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 168 requests on a phone: other files 786 KiB (103), images 413 KiB (21) and scripts 388 KiB (37). That is a lean page.

  • 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

4 to fixGoogle 8696
  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 170 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

2 to fixGoogle 10088
  • Title is short (19 characters)

    Your title is only 19 characters: “QLOMONO (クロモノ)公式ストア”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 226 internal links, 5 external

    The homepage links to 226 pages on qlomono.com and 5 external pages.

6 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “QLOMONOの黒を基調としたモノトーンコーデは、 シンプルながらも洗練されたスタイルをご提案致します。 ありきたりなファッションの常識、固定概念を破り捨て 他とは一線を画したオリジナルな存在へ、そんなお手伝いができると信じております。”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://qlomono.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.

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

  • llms.txt published

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

Other pages

3 to fix85
  • 15 pages without a meta description

    /collections/all, /collections/%E3%82%B8%E3%83%A3%E3%82%B1%E3%83%83%E3%83%88-%E3%82%B3%E3%83%BC%E3%83%88, /collections/%E3%82%A6%E3%82%A3%E3%83%B3%E3%82%BF%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%88, /collections/%E3%82%B7%E3%83%A3%E3%83%84, /collections/%E3%82%BB%E3%83%BC%E3%82%BF%E3%83%BC-%E3%82%AB%E3%83%BC%E3%83%87%E3%82%A3%E3%82%AC%E3%83%B3 and /collections/%E3%82%AB%E3%83%BC%E3%83%87%E3%82%A3%E3%82%AC%E3%83%B3 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 links to non-canonical URLs

    Your homepage links to 14 pages by a URL that isn't their canonical one, for example /collections/%E3%82%B8%E3%83%A3%E3%82%B1%E3%83%83%E3%83%88-%E3%82%B3%E3%83%BC%E3%83%88, whose canonical is /collections/%e3%82%b8%e3%83%a3%e3%82%b1%e3%83%83%e3%83%88-%e3%82%b3%e3%83%bc%e3%83%88. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    /collections/%E3%83%90%E3%83%83%E3%82%B0 and /collections/%E3%83%96%E3%83%BC%E3%83%84 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    /collections/all, /collections/%E3%82%B8%E3%83%A3%E3%82%B1%E3%83%83%E3%83%88-%E3%82%B3%E3%83%BC%E3%83%88, /collections/%E3%82%A6%E3%82%A3%E3%83%B3%E3%82%BF%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%88, /collections/%E3%82%B7%E3%83%A3%E3%83%84, /collections/%E3%82%BB%E3%83%BC%E3%82%BF%E3%83%BC-%E3%82%AB%E3%83%BC%E3%83%87%E3%82%A3%E3%82%AC%E3%83%B3 and /collections/%E3%82%AB%E3%83%BC%E3%83%87%E3%82%A3%E3%82%AC%E3%83%B3 and 9 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 97 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 to fixGoogle 7388
  • 19 small tap targets

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://qlomono.com/account.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (qlomono.com).

  • Valid certificate (53 days left)

    The certificate from Let's Encrypt · YE1 verifies for qlomono.com and is valid for another 53 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://qlomono.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 44 links work

    All 44 links checked from your homepage (40 internal, 4 external) answered without errors.

Domain and trust

1 to fix
  • Domain expires in 79 days

    qlomono.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

  • No CAA record

    qlomono.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    qlomono.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

1 checks passed
  • Domain is 4 years old

    4 years

    qlomono.com was registered in Jan 2022 through GMO Internet Group, Inc. d/b/a Onamae.com. An established domain carries more trust with email providers and search engines.

Content and conversion

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

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

1 checks passed
  • 2 short forms

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

Email authentication

2 to fix0
  • No DMARC policy

    qlomono.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

  • No SPF record

    qlomono.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Domain receives no email

    qlomono.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

  • Email authentication score: 0/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

cloudfunctions.net · chaty.app · hextom.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on qlomono.com, including 8 speed issues, 2 SEO issues and 6 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