Website review, no card needed
bestore.co.il website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 67 checks
This review found 39 issues worth fixing on bestore.co.il, 9 of them high impact, across 67 checks. The most urgent: google Tag Manager adds 1.4 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 195 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 202 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 200 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 197 ms |
| Aug 22, 2026 | 196 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 198 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 215 ms |
| Oct 31, 2026 | 223 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 1.8 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 3.0 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
547 KiB25 files are served with short cache lifetimes, so returning visitors download them again (547 KiB).
Facebook adds 316 ms
316 msFacebook costs a phone 316 ms of main-thread work and 413 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google/Doubleclick Ads adds 223 ms
223 msGoogle/Doubleclick Ads costs a phone 223 ms of main-thread work and 555 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 149 ms. During a long task the page ignores taps.
Improve image delivery
91 KiB1 image could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Document request latency
7 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 21.2 s
21.2 sThe page becomes fully interactive after 21.2 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 232 ms
232 msReal visitors wait 232 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.114
0.114The layout shifts by 0.114 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 195 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “אתר בי פארם עבר לאפליקציה, עם כל המוצרים, הקופונים וההטבות …”.
Images and page weight
Page weight: 3.1 MB in 131 requests
3.1 MBYour homepage downloads 3.1 MB in 131 requests on a phone: scripts 2.8 MB (45), images 186 KiB (18) and other files 86 KiB (63). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 checks passed
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.bestore.co.il/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at bestore.co.il/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
3 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “הכירו את אפליקציית Be מבית שופרסל – אפליקציית בי פארם שמביאה אליכם מבצעים בלעדיים ומבחר עצום של מוצרי פארם, קוסמטיקה וב…”.
One H1 headline
Your main headline reads: “אפליקצית Be פארם House of Beauty”.
Title: 44 characters
Your title is a healthy 44 characters: “מוצרי פארם, קוסמטיקה ובית מרקחת אונליין | Be”.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.bestore.co.il/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.
Best practices
5 broken images
5 images failed to load on a phone, for example https://www.bestore.co.il/img/phoneImg.png?v=2.
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Outbrain and 2 mores (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 3 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.
34 other companies contacted
Loading the homepage contacts 34 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 bestore.co.il, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Shufersal Set Shufersal Ltd
Company
- Founded
- 1991
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 bestore.co.il, including 18 speed issues, 7 SEO issues and 5 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.