Website review, no card needed
smartbeemo.com website review
Visit site (opens in a new tab)Reviewed 27 October 202620 issues · 72 checks
This review found 20 issues worth fixing on smartbeemo.com, 9 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.8 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 6.1 s |
| May 30, 2026 | 6.5 s |
| Jun 6, 2026 | 6.6 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 6.1 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.4 s |
| Jul 18, 2026 | 5.4 s |
| Jul 25, 2026 | 5.6 s |
| Aug 1, 2026 | 5.5 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 409 ms |
| May 16, 2026 | 419 ms |
| May 23, 2026 | 427 ms |
| May 30, 2026 | 441 ms |
| Jun 6, 2026 | 445 ms |
| Jun 13, 2026 | 453 ms |
| Jun 20, 2026 | 439 ms |
| Jun 27, 2026 | 424 ms |
| Jul 4, 2026 | 428 ms |
| Jul 11, 2026 | 431 ms |
| Jul 18, 2026 | 444 ms |
| Jul 25, 2026 | 474 ms |
| Aug 1, 2026 | 481 ms |
| Aug 8, 2026 | 504 ms |
| Aug 15, 2026 | 533 ms |
| Aug 22, 2026 | 523 ms |
| Aug 29, 2026 | 518 ms |
| Sep 5, 2026 | 507 ms |
| Sep 12, 2026 | 496 ms |
| Sep 19, 2026 | 489 ms |
| Sep 26, 2026 | 470 ms |
| Oct 3, 2026 | 475 ms |
| Oct 10, 2026 | 475 ms |
| Oct 17, 2026 | 503 ms |
| Oct 24, 2026 | 544 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
Speed
Improve image delivery
300 ms · 48 KiB1 image could be 48 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.
Use efficient cache lifetimes
150 ms · 20 KiB1 file is served with short cache lifetimes, so returning visitors download them again (20 KiB).
1 third-party service on the page
1 third-party service load with your homepage (googleusercontent.com), adding 49 KiB and 0 ms of main-thread time.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99 (desktop: 41). That is in Google's “good” band (90 and up).
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 3 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 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.
Real-user LCP: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 544 ms
544 msReal visitors wait 544 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 409 ms to 544 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.8 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Kendi bütçenize dokunmadan dijital kazanç dünyasına adım at…”.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Speed Index: 0.9 s
0.9 sVisually, the page fills in at 0.9 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.02 g of CO₂ per visit
0.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.02 g of CO₂e: 2.1 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: 64 KiB in 2 requests
64 KiBYour homepage downloads 64 KiB in 2 requests on a phone: images 49 KiB (1) and HTML 15 KiB (1). 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h1 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
41 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: 41 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Lanza tu tienda de Ecommerce y hazla crecer.” and “Lanza tu tienda de Ecommerce y hazla crecer.”). One clear main headline is easier for people and search engines.
27 internal links, 15 external
The homepage links to 27 pages on smartbeemo.com and 15 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Descubre un ecosistema de soluciones para ecommerce, diseñadas para potenciar tu tienda online. ¡Haz crecer tu negocio …”.
Title: 49 characters
Your title is a healthy 49 characters: “Lanza y crece tu tienda de Ecommerce I smartBeemo”.
Canonical URL set
The canonical URL is https://smartbeemo.com/.
Structured data in place
Structured data found: EducationalOrganization, LocalBusiness, WebPage 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 http://smartbeemo.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://smartbeemo.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,472 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://smartbeemo.com/academia/programas-online and https://smartbeemo.com/contactenos have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://smartbeemo.com/academia/programas-online and https://smartbeemo.com/contactenos have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://smartbeemo.com/contactenos 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
Linked pages load
All 8 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 8 pages that loaded have a <title>.
Best practices
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.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 29-field form
Your longest form asks for 29 fields (5 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,392 words of copy
The homepage carries about 1,392 words of visible text.
4 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
2 other companies contacted
Loading the homepage contacts 2 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 smartbeemo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on smartbeemo.com, including 8 speed issues, 1 SEO issue 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.