Website review, no card needed

yosekastationery.com logo

yosekastationery.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 81 checks

This review found 34 issues worth fixing on yosekastationery.com, 12 of them high impact, across 81 checks. The most urgent: youTube adds 1.4 s. 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.1 s916 msMay 16Oct 31985 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 2026988 ms
Sep 5, 2026954 ms
Sep 12, 2026953 ms
Sep 19, 2026937 ms
Sep 26, 2026942 ms
Oct 3, 2026967 ms
Oct 10, 2026973 ms
Oct 17, 2026991 ms
Oct 24, 2026984 ms
Oct 31, 2026985 ms
Real-visitor tap response (INP)75th percentile, phones
80 ms70 msMay 16Oct 3171 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202672 ms
May 23, 202672 ms
May 30, 202675 ms
Jun 6, 202677 ms
Jun 13, 202678 ms
Jun 20, 202678 ms
Jun 27, 202678 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202676 ms
Aug 15, 202674 ms
Aug 22, 202675 ms
Aug 29, 202673 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202671 ms
Oct 24, 202671 ms
Oct 31, 202671 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 yosekastationery.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix57
  • YouTube adds 1.4 s

    1.4 s

    YouTube costs a phone 1.4 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 16,259 HTML elements

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

  • Main-thread work: 9.4 s

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

  • Improve image delivery

    150 ms · 2.2 MB

    61 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and Other Google APIs/SDKs and others), adding 3.9 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 57

    57/100

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

  • Render-blocking requests

    950 ms

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

  • Shopify adds 159 ms

    159 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    197 KiB

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

  • Minify JavaScript

    150 ms · 2 KiB

    2 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    55 KiB

    11 files are served with short cache lifetimes, so returning visitors download them again (55 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: 28 ms

    28 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 35.4 s

    35.4 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

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

  • 14 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

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: 1.7 s

    1.7 s

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

  • Real-user INP: 161 ms

    161 ms

    Real visitors wait 161 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.4 s

    1.4 s

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

  • Real-user TTFB: 391 ms

    391 ms

    Real visitors wait 391 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

    0

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

Images and page weight

2 to fix64
  • Page weight: 10.0 MB in 529 requests

    10.0 MB

    Your homepage downloads 10.0 MB in 529 requests on a phone: images 4.6 MB (121), scripts 3.2 MB (166) and other files 1.1 MB (193). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    yoseka.stationery_37717444_2046172622084036_3637116518300385 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 2.8 g of CO₂ per visit

    2.83 g

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

4 to fixGoogle 9795
  • 17 tap targets too small

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

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

  • 17 links without text

    17 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 233 images in the HTML carry an alt attribute.

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

SEO

5 to fixGoogle 9279
  • Title is short (17 characters)

    Your title is only 17 characters: “Yoseka Stationery”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/logo_300x_2x_2527d43e-24d5-4ada-956e-930875…”.

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

  • 799 internal links, 3 external

    The homepage links to 799 pages on yosekastationery.com and 3 external pages.

4 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Stationery store in Greenpoint, Brooklyn, New York City. Curated stationery from notebooks, pens, pencils to fountain p…”.

  • Canonical URL set

    The canonical URL is https://yosekastationery.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://yosekastationery.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 (4,670 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://yosekastationery.com/collections/2027-hightide-planners, https://yosekastationery.com/collections/2027-aura-estelle-planners, https://yosekastationery.com/collections/2027-kleid-planners, https://yosekastationery.com/collections/delfonics-2027 and https://yosekastationery.com/collections/shinnippon-calendars-2027 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 7385
  • 113 small tap targets

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

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelectorAll')”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 4,991 words of copy

    The homepage carries about 4,991 words of visible text.

2 checks passed
  • 118 calls to action

    The homepage has 118 calls to action, for example “Shop Now”.

  • 77 short forms

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

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 Pinterest Tag (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 yosekastationery.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews

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 34 issues on yosekastationery.com, including 14 speed issues, 5 SEO issues and 4 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