Website review, no card needed

shihiko.com logo

shihiko.com website review

Visit site (opens in a new tab)Reviewed 20 November 202628 issues · 80 checks

This review found 28 issues worth fixing on shihiko.com, 8 of them high impact, across 80 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
883 ms675 msMay 30Nov 14833 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026711 ms
Jun 6, 2026699 ms
Jun 13, 2026710 ms
Jun 20, 2026717 ms
Jun 27, 2026718 ms
Jul 4, 2026725 ms
Jul 11, 2026730 ms
Jul 18, 2026741 ms
Jul 25, 2026751 ms
Aug 1, 2026751 ms
Aug 8, 2026746 ms
Aug 15, 2026737 ms
Aug 22, 2026732 ms
Aug 29, 2026726 ms
Sep 5, 2026739 ms
Sep 12, 2026748 ms
Sep 19, 2026759 ms
Sep 26, 2026784 ms
Oct 3, 2026801 ms
Oct 10, 2026841 ms
Oct 17, 2026856 ms
Oct 24, 2026859 ms
Oct 31, 2026858 ms
Nov 7, 2026849 ms
Nov 14, 2026833 ms
Real-visitor tap response (INP)75th percentile, phones
159 ms125 msMay 30Nov 14139 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026138 ms
Jun 6, 2026141 ms
Jun 13, 2026145 ms
Jun 20, 2026139 ms
Jun 27, 2026137 ms
Jul 4, 2026130 ms
Jul 11, 2026129 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026131 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026137 ms
Sep 5, 2026141 ms
Sep 12, 2026143 ms
Sep 19, 2026145 ms
Sep 26, 2026146 ms
Oct 3, 2026147 ms
Oct 10, 2026154 ms
Oct 17, 2026155 ms
Oct 24, 2026155 ms
Oct 31, 2026146 ms
Nov 7, 2026144 ms
Nov 14, 2026139 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 shihiko.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shihiko.com at 0.8 s0.8 s
  2. shihiko.com at 1.7 s1.7 s
  3. shihiko.com at 2.5 s2.5 s
  4. shihiko.com at 3.3 s3.3 s
  5. shihiko.com at 4.1 s4.1 s
  6. shihiko.com at 5.0 s5.0 s
  7. shihiko.com at 5.8 s5.8 s
  8. shihiko.com at 6.6 s6.6 s

Speed

9 to fix76
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 5.0 s

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

  • Improve image delivery

    4.3 MB

    27 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and alia-prod.com and others), adding 1.9 MB and 1.5 s of main-thread time.

  • Mobile performance score: 76

    76/100

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

  • Reduce unused JavaScript

    728 KiB

    About 728 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 538 ms

    538 ms

    Google Tag Manager costs a phone 538 ms of main-thread work and 521 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.

  • Shopify adds 427 ms

    427 ms

    Shopify costs a phone 427 ms of main-thread work and 669 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.

  • 2,997 HTML elements

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

  • 14 long tasks on the main thread

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

  • Use efficient cache lifetimes

    210 KiB

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

  • Reduce unused CSS

    57 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    47 KiB

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

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

    20 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 23.0 s

    23.0 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 599 ms

    599 ms

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

  • Tap response (INP) held steady for real visitors

    +1%

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

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

    +19%

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

9 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.0 s

    1.0 s

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

  • Real-user INP: 132 ms

    132 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 451 ms

    451 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.057

    0.057

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “_______L_____ayout”.

Images and page weight

3 to fix53
  • Page weight: 9.5 MB in 359 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 359 requests on a phone: images 6.0 MB (57), scripts 2.0 MB (120) and other files 1,012 KiB (146). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 4 images far larger than shown

    32 KiB

    4 images are downloaded at several times the size a phone draws them, for example bluemoon.jpg at 767 px wide, shown at 240 px. Resized copies would save about 32 KiB.

  • 1 image in older formats

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

    2.70 g

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

Accessibility

4 to fixGoogle 9195
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Zoom is disabled

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

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 85 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

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

  • 123 internal links, 4 external

    The homepage links to 123 pages on shihiko.com and 4 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Shop Shihiko streetwear online for hoodies, tees, jackets, bottoms, and accessories with bold styles made for modern ur…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Shihiko Streetwear Clothing & Fashion Online Store”.

  • Canonical URL set

    The canonical URL is https://shihiko.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://shihiko.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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,143 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://shihiko.com/collections/hoodies, https://shihiko.com/collections/t-shirts, https://shihiko.com/collections/longsleeves, https://shihiko.com/collections/knitwear, https://shihiko.com/collections/outwear and https://shihiko.com/collections/jeans and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://shihiko.com/collections/all, https://shihiko.com/collections/hoodies, https://shihiko.com/collections/t-shirts, https://shihiko.com/collections/longsleeves, https://shihiko.com/collections/knitwear and https://shihiko.com/collections/outwear and 9 others 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 45 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9687
  • 15 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 224 words

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

  • 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: “JOIN WAITLIST”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop + -”, “Shop all” and “Shop+-”.

  • 30 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 33 cookies set on arrival

    33

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

  • 42 other companies contacted

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

Apps your storefront loads

Triplewhale · Ta Banner Pop Up · Gorgias Live Chat Helpdesk · Judge Me Reviews · Klaviyo Email Marketing Sms · Candy Rack · Elevate Ab Testing · Applovin Shop Integration · Cartbite · Joy Loyalty Program · Freegifts · Simple Social Login · afterpay.com · cloudfront.net · avada.io · bogos.io · instant.one · Swym Wishlist Plus

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on shihiko.com, including 12 speed issues, 2 SEO issues 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
shihiko.com website review: scores and fixes | Programmable