Website review, no card needed
yazskihandmade.com website review
Visit site (opens in a new tab)Reviewed 5 November 202623 issues · 68 checks
This review found 23 issues worth fixing on yazskihandmade.com, 6 of them high impact, across 68 checks. The most urgent: font display. 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
78C- #58,959 of 116,274 reviewed websitesbeats 44%
- #39,070 of 66,754 online storesbeats 36%
- #37,373 of 60,924 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 763 ms |
| May 23, 2026 | 784 ms |
| May 30, 2026 | 750 ms |
| Jun 6, 2026 | 868 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 63 ms |
| May 23, 2026 | 65 ms |
| May 30, 2026 | 63 ms |
| Jun 6, 2026 | 66 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
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.1 s
6.9 s
Speed
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Mobile performance score: 84
84/100Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 144 KiB4 images could be 144 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Reduce unused JavaScript
280 ms · 91 KiBAbout 91 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (Hexton, Shopify and shop.app), adding 126 KiB and 37 ms of main-thread time.
Use efficient cache lifetimes
29 KiB4 files are served with short cache lifetimes, so returning visitors download them again (29 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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 195 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.178
0.178The layout shifts by 0.178 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Yazski Handmade Handcrafted items made by Yazski”. Most of its time is resource load delay (1.4 s).
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image 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 63 ms to 66 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Time to Interactive: 3.6 s
3.6 sThe page is fully interactive after 3.6 s.
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.22 g of CO₂e: 25.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 779 KiB in 65 requests
779 KiBYour homepage downloads 779 KiB in 65 requests on a phone: scripts 286 KiB (32), images 281 KiB (6) and other files 86 KiB (19). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
44 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: 44 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Yazski Handmade”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("www.facebook.com/yazskihandmade")”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
21 internal links, 1 external
The homepage links to 21 pages on yazskihandmade.com and 1 external page.
5 checks passed
One H1 headline
Your main headline reads: “<img src="//yazskihandmade.com/cdn/shop/files/Yazski_250x.png?v=1614328662" srcset="//yazskihandmade.com/cdn/shop/files…”.
Canonical URL set
The canonical URL is https://yazskihandmade.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://yazskihandmade.com/sitemap.xml.
AI search readiness
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 (304 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://yazskihandmade.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://yazskihandmade.com/www.facebook.com/yazskihandmade and https://yazskihandmade.com/instagram.com/yazski.handmade, which answer with an error. Visitors hit a dead end and search engines drop them.
3 pages without a meta description
https://yazskihandmade.com/collections/stickers, https://yazskihandmade.com/collections/ready-to-ship and https://yazskihandmade.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://yazskihandmade.com/collections/fabric has 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.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
5 checks passed
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 6 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 10 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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 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 249 words
The homepage has only about 249 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
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 yazskihandmade.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
King Product Options · 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 23 issues on yazskihandmade.com, including 9 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.