Website review, no card needed

hinomi.co logo

hinomi.co website review

Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 87 checks

This review found 36 issues worth fixing on hinomi.co, 10 of them high impact, across 87 checks. The most urgent: render-blocking 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.2 s1.6 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
160 ms116 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026122 ms
May 23, 2026124 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026127 ms
Jul 11, 2026128 ms
Jul 18, 2026129 ms
Jul 25, 2026130 ms
Aug 1, 2026130 ms
Aug 8, 2026135 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026140 ms
Sep 19, 2026146 ms
Sep 26, 2026146 ms
Oct 3, 2026147 ms
Oct 10, 2026153 ms
Oct 17, 2026154 ms
Oct 24, 2026155 ms
Oct 31, 2026154 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 hinomi.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hinomi.co at 0.8 s0.8 s
  2. hinomi.co at 1.6 s1.6 s
  3. hinomi.co at 2.4 s2.4 s
  4. hinomi.co at 3.2 s3.2 s
  5. hinomi.co at 4.0 s4.0 s
  6. hinomi.co at 4.8 s4.8 s
  7. hinomi.co at 5.6 s5.6 s
  8. hinomi.co at 6.4 s6.4 s

Speed

13 to fix46
  • Render-blocking requests

    1.0 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.3 s

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

  • Reduce unused JavaScript

    300 ms · 1.5 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, Shopify and Google CDN and others), adding 3.7 MB and 1.3 s of main-thread time.

  • Use efficient cache lifetimes

    1.2 MB

    17 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • route.com adds 721 ms

    721 ms

    route.com costs a phone 721 ms of main-thread work and 1.1 MB 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.

  • Duplicated JavaScript

    485 KiB

    485 KiB JavaScript is shipped twice across bundles.

  • 14 long tasks on the main thread

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

  • Shopify adds 208 ms

    208 ms

    Shopify costs a phone 208 ms of main-thread work and 1.6 MB 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.

  • Google CDN adds 183 ms

    183 ms

    Google CDN costs a phone 183 ms of main-thread work and 298 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.

  • 1,936 HTML elements

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

  • tidio.co adds 99 ms

    99 ms

    tidio.co costs a phone 99 ms of main-thread work and 515 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 · 58 KiB

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

  • Improve image delivery

    159 KiB

    4 images could be 159 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).

  • Legacy JavaScript

    33 KiB

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

  • Minify CSS

    6 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

8 to fix100
  • Time to Interactive: 28.9 s

    28.9 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Early Bird Black Friday Access Lowest Prices Guaranteed. Be…”.

  • Total Blocking Time: 1.1 s

    1.1 s

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

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

    +26%

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

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

    +20%

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 12 images without width and height

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

7 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.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: 155 ms

    155 ms

    Real visitors wait 155 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: 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: 580 ms

    580 ms

    Real visitors wait 580 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).

Images and page weight

2 to fix60
  • Page weight: 5.1 MB in 277 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 277 requests on a phone: scripts 3.1 MB (124), other files 696 KiB (86) and images 572 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    45 KiB

    1 image is downloaded at several times the size a phone draws it, for example h2_pro_-_mobile.webp at 1,200 px wide, shown at 350 px. Resized copies would save about 45 KiB.

  • 1 image in older formats

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

    1.45 g

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

5 to fixGoogle 8993
  • 49 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 113 internal links, 10 external

    The homepage links to 113 pages on hinomi.co and 10 external pages.

8 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Experience ultimate ergonomic comfort with Hinomi. Shop premium ergonomic chairs and desks designed to support your wor…”.

  • One H1 headline

    Your main headline reads: “Ergonomic Home Office Furniture for Comfort and Productivity”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Hinomi USA | Ergonomic Home Office Furniture & Equipment Online”.

  • Canonical URL set

    The canonical URL is https://www.hinomi.co/.

  • Structured data in place

    Structured data found: FAQPage, ItemList, Organization and WebSite.

  • 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.hinomi.co/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 (1,462 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.hinomi.co/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.hinomi.co/policies/shipping-policy and https://www.hinomi.co/pages/black-friday-sale have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.hinomi.co/pages/black-friday-sale has 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 49 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 8 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.

  • About 1,228 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Early Black Friday Deals” and “Shop Now”.

  • 34 calls to action

    The homepage has 34 calls to action, for example “Shop Early Black Friday Deals”, “Contact” and “Contact Us”.

  • 19 short forms

    19 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 Klaviyo (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.

  • 18 cookies set on arrival

    18

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 hinomi.co, 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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Ang Extra Menu · Assortion · Impact Com · Sami Product Labels · Judge Me Reviews · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Route Protection Tracking · Microsoft Clarity · Uppromote Affiliate · Pagefly Ai Page Builder · Videowise Video Commerce · Easylocation · Hyper Menu · Forms · Affliate By Secomapp · Polar Analytics

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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Singapore

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on hinomi.co, including 21 speed issues, 1 SEO issue and 2 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