Website review, no card needed
hoooyi.com website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 82 checks
This review found 33 issues worth fixing on hoooyi.com, 11 of them high impact, across 82 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82B- #34,606 of 123,879 reviewed websitesbeats 67%
- #22,912 of 69,702 online storesbeats 61%
- #22,128 of 63,406 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 103 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 114 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 152 ms |
| Oct 31, 2026 | 149 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
Speed
Improve image delivery
9.7 s · 8.5 MB58 images could be 8.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.7 s faster on a phone.
Reduce unused JavaScript
4.2 s · 792 KiBAbout 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 2.0 MB and 1.1 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 624 ms
624 msGoogle Tag Manager costs a phone 624 ms of main-thread work and 1.2 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.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 258 ms
258 msShopify costs a phone 258 ms of main-thread work and 527 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.
Render-blocking requests
300 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,047 HTML elements
The page has 2,047 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 18 KiBAbout 18 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
21 KiB6 files are served with short cache lifetimes, so returning visitors download them again (21 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.
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: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 47.9 s
47.9 sYour largest element takes 47.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 49.8 s
49.8 sThe page becomes fully interactive after 49.8 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 103 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 521 ms
521 msScripts block taps and scrolling for 521 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
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: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 692 ms
692 msReal visitors wait 692 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 309 requests
12.9 MBYour homepage downloads 12.9 MB in 309 requests on a phone: images 9.8 MB (97), scripts 2.1 MB (96) and other files 712 KiB (81). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
3.1 MB9 images are downloaded at several times the size a phone draws them, for example TK-20260719-_fawaz_dc99-_16613-black_23185-black-M_-1.jpg at 1,701 px wide, shown at 171 px. Resized copies would save about 3.1 MB.
5 images in older formats
5 images (1.2 MB) are 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 3.7 g of CO₂ per visit
3.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.66 g of CO₂e: 438.8 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
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.
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 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (51 characters)
Your meta description is only 51 characters: “Mens Clothes & Unisex Clothes | Shop Online Fashion”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("www.pinterest.com/Hoooyi_official")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
One H1 headline
Your <h1> is empty.
133 internal links, 8 external
The homepage links to 133 pages on hoooyi.com and 8 external pages.
4 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Mens Clothes & Unisex Clothes | Shop Online Fashion – HOOOYI”.
Canonical URL set
The canonical URL is https://hoooyi.com/.
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://hoooyi.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://hoooyi.com/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.
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.
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,508 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://hoooyi.com/collections/all and https://hoooyi.com/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://hoooyi.com/collections/all, https://hoooyi.com/products/regular-fit-glitch-ghost-print-cotton-t-shirt, https://hoooyi.com/products/regular-fit-1-battery-print-cotton-t-shirt and https://hoooyi.com/products/color-block-corduroy-hooded-shirt have 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 84 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 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.
Every page has a meta description
All 5 pages that loaded have a meta description.
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 5 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
73 of 85 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
About 442 words of copy
The homepage carries about 442 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Apply”, “Türkiye (TRY ₺)” and “Contact Us”.
7 short forms
7 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
33 other companies contacted
Loading the homepage contacts 33 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 hoooyi.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
- Tailwind CSS
- 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 33 issues on hoooyi.com, including 15 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.