Website review, no card needed
yra-makeover.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 80 checks
This review found 39 issues worth fixing on yra-makeover.com, 15 of them high impact, across 80 checks. The most urgent: main-thread work: 13.7 s. 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
68D- #105,750 of 120,410 reviewed websitesbeats 10%
- #63,543 of 68,161 online storesbeats 5%
- #58,571 of 62,115 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.3 s |
| Aug 1, 2026 | 1.6 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 109 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 112 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
2.1 s
4.2 s
6.2 s
8.3 s
10.4 s
12.5 s
14.5 s
16.6 s
Speed
Main-thread work: 13.7 s
A phone's processor spends 13.7 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.1 MB and 2.0 s of main-thread time.
Improve image delivery
450 ms · 1.5 MB11 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 820 ms
820 msGoogle Tag Manager costs a phone 820 ms of main-thread work and 309 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
600 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 575 ms. During a long task the page ignores taps.
Reduce unused JavaScript
150 ms · 332 KiBAbout 332 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 415 ms
415 msShopify costs a phone 415 ms of main-thread work and 476 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.
Klaviyo adds 252 ms
252 msKlaviyo costs a phone 252 ms of main-thread work and 76 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.
Use efficient cache lifetimes
224 KiB24 files are served with short cache lifetimes, so returning visitors download them again (224 KiB).
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Reduce unused CSS
150 ms · 21 KiBAbout 21 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.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 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
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 10.2 MB in 302 requests
10.2 MBYour homepage downloads 10.2 MB in 302 requests on a phone: media 5.7 MB (1), images 2.0 MB (22) and scripts 1.1 MB (92). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
1.2 MB8 images are downloaded at several times the size a phone draws them, for example Sharpener.jpg at 3,839 px wide, shown at 362 px. Resized copies would save about 1.2 MB.
1 image over 500 KB
Sharpener.jpg weighs 636 KiB. On a phone connection a single image that size takes seconds.
6 images below the first screen load straight away
6 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (395 KiB) 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 2.9 g of CO₂ per visit
2.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.88 g of CO₂e: 345.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 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: 48 passed and 6 failed. 4 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 (55 characters)
Your meta description is only 55 characters: “יעל רנה-אסף | naturopathic makeover 🍃100% נטוּרוֹפתי🍃”. 70 to 160 characters is enough to sell the click.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
74 internal links, 8 external
The homepage links to 74 pages on yra-makeover.com and 8 external pages.
6 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “yra-makeover.com – YRA Makeover”.
Canonical URL set
The canonical URL is https://yra-makeover.com/.
Structured data in place
Structured data found: 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://yra-makeover.com/sitemap.xml.
AI search readiness
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.
llms.txt published
The site publishes https://yra-makeover.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://yra-makeover.com/products/year-end-42 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://yra-makeover.com/collections/%D7%9E%D7%A1%D7%9C%D7%95%D7%9C%D7%99-%D7%94%D7%AA%D7%96%D7%95%D7%A0%D7%94-%D7%9E%D7%99%D7%95%D7%97%D7%93%D7%99%D7%9D-%D7%9C%D7%9E%D7%A6%D7%91 and https://yra-makeover.com/products/the-total-body-makeover-variant all use the title “מסלול מייקאובר תזונה – YRA Makeover”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://yra-makeover.com/pages/%D7%A1%D7%99%D7%A4%D7%95%D7%A8%D7%99-%D7%94%D7%A6%D7%9C%D7%97%D7%94 has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://yra-makeover.com/collections/%D7%9E%D7%A1%D7%9C%D7%95%D7%9C%D7%99-%D7%94%D7%AA%D7%96%D7%95%D7%A0%D7%94-%D7%9E%D7%99%D7%95%D7%97%D7%93%D7%99%D7%9D-%D7%9C%D7%9E%D7%A6%D7%91 and https://yra-makeover.com/products/the-total-body-makeover-variant use the same meta description. A description written for each page earns more clicks.
9 links to non-canonical URLs
Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://yra-makeover.com/collections/%D7%A7%D7%99%D7%98%D7%99%D7%9D-%D7%9E%D7%9E%D7%95%D7%A7%D7%93%D7%99%D7%9D-quick-fix, whose canonical is https://yra-makeover.com/collections/%d7%a7%d7%99%d7%98%d7%99%d7%9d-%d7%9e%d7%9e%d7%95%d7%a7%d7%93%d7%99%d7%9d-quick-fix. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://yra-makeover.com/pages/%D7%A1%D7%99%D7%A4%D7%95%D7%A8%D7%99-%D7%94%D7%A6%D7%9C%D7%97%D7%94, https://yra-makeover.com/pages/about and https://yra-makeover.com/collections/%D7%9E%D7%99%D7%99%D7%A7%D7%90%D7%95%D7%91%D7%A8-%D7%AA%D7%96%D7%95%D7%A0%D7%AA%D7%99 have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://yra-makeover.com/collections/%D7%A7%D7%99%D7%98%D7%99%D7%9D-%D7%9E%D7%9E%D7%95%D7%A7%D7%93%D7%99%D7%9D-quick-fix, https://yra-makeover.com/collections/%D7%9E%D7%A1%D7%9C%D7%95%D7%9C%D7%99-%D7%94%D7%AA%D7%96%D7%95%D7%A0%D7%94-%D7%9E%D7%99%D7%95%D7%97%D7%93%D7%99%D7%9D-%D7%9C%D7%9E%D7%A6%D7%91, https://yra-makeover.com/collections/gazoz, https://yra-makeover.com/collections/hair-makeover-1, https://yra-makeover.com/collections/%D7%9E%D7%99%D7%A0%D7%99-%D7%A7%D7%99%D7%98%D7%99%D7%9D-%D7%9C%D7%A9%D7%99%D7%A2%D7%A8 and https://yra-makeover.com/collections/%D7%91%D7%95%D7%A1%D7%98%D7%99%D7%9D-%D7%A0%D7%98%D7%95%D7%A8%D7%95%D7%A4%D7%AA%D7%99%D7%99%D7%9D-%D7%A9%D7%99%D7%A2%D7%A8 and 7 others have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
14 of 16 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.
Only about 61 words
The homepage has only about 61 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.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop now”.
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and TikTok Pixel (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
20 other companies contacted
Loading the homepage contacts 20 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 yra-makeover.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
1clickpopup · Tolstoy · Freegifts · chimpstatic.com · klaviyo.com · cloudfront.net · flashyapp.com · bogos.io
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
- jQuery
- E-commerce
- Shopify
- 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 39 issues on yra-makeover.com, including 14 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.