Website review, no card needed
cebra.com.ar website review
Visit site (opens in a new tab)Reviewed 1 November 202661 issues · 92 checks
This review found 61 issues worth fixing on cebra.com.ar, 24 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 356 ms |
| May 16, 2026 | 370 ms |
| May 23, 2026 | 375 ms |
| May 30, 2026 | 381 ms |
| Jun 6, 2026 | 382 ms |
| Jun 13, 2026 | 390 ms |
| Jun 20, 2026 | 392 ms |
| Jun 27, 2026 | 392 ms |
| Jul 4, 2026 | 399 ms |
| Jul 11, 2026 | 396 ms |
| Jul 18, 2026 | 396 ms |
| Jul 25, 2026 | 397 ms |
| Aug 1, 2026 | 400 ms |
| Aug 8, 2026 | 405 ms |
| Aug 15, 2026 | 413 ms |
| Aug 22, 2026 | 412 ms |
| Aug 29, 2026 | 413 ms |
| Sep 5, 2026 | 415 ms |
| Sep 12, 2026 | 416 ms |
| Sep 19, 2026 | 432 ms |
| Sep 26, 2026 | 438 ms |
| Oct 3, 2026 | 440 ms |
| Oct 10, 2026 | 442 ms |
| Oct 17, 2026 | 445 ms |
| Oct 24, 2026 | 443 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.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Reduce unused JavaScript
5.8 s · 982 KiBAbout 982 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.
Improve image delivery
1.7 s · 1.1 MB32 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.
vtexassets.com adds 1.4 s
1.4 svtexassets.com costs a phone 1.4 s of main-thread work and 3.3 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.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google CDN and Google Tag Manager and others), adding 5.0 MB and 2.8 s of main-thread time.
Use efficient cache lifetimes
550 ms · 361 KiB23 files are served with short cache lifetimes, so returning visitors download them again (361 KiB).
Google CDN adds 509 ms
509 msGoogle CDN costs a phone 509 ms of main-thread work and 745 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.
Reduce unused CSS
450 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 355 ms
355 msGoogle Tag Manager costs a phone 355 ms of main-thread work and 329 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 369 ms. During a long task the page ignores taps.
Render-blocking requests
350 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
1,592 HTML elements
The page has 1,592 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
250 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 55 ms
55 msYour server sent the HTML in 55 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 INP: 601 ms
601 msReal visitors wait 601 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.42
0.42For real visitors the layout shifts by 0.42 (75th percentile). Good is under 0.1.
First Contentful Paint: 8.1 s
8.1 sThe first text or image appears after 8.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.0 s
24.0 sYour largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 356 ms to 443 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.144
0.144The layout shifts by 0.144 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Images and page weight
Page weight: 5.8 MB in 147 requests
5.8 MBYour homepage downloads 5.8 MB in 147 requests on a phone: scripts 2.5 MB (52), fonts 1.3 MB (5) and images 1.3 MB (48). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
6886d483-80c2-48a6-8cb0-66bb31f58b4f___772e48015159023dc0a3b 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).
8 images far larger than shown
482 KiB8 images are downloaded at several times the size a phone draws them, for example 9c2cc898-fbe9-4feb-a50c-fb7f1719fbc7___ad7a509dec4899a8d58c7 at 2,048 px wide, shown at 108 px. Resized copies would save about 482 KiB.
1 image below the first screen load straight away
1 image further down the page (220 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (33 KiB) is 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 1.7 g of CO₂ per visit
1.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.65 g of CO₂e: 198.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
48 tap targets too small
48 tap targets are too small or too close together to hit reliably with a finger.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
44 links without text
44 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “Juguetería Cebra”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
78 internal links, 0 external
The homepage links to 78 pages on cebra.com.ar and 0 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.cebra.com.ar/.
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://www.cebra.com.ar/sitemap.xml.
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.cebra.com.ar/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (486 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages hidden from search
https://www.cebra.com.ar/150, https://www.cebra.com.ar/191, https://www.cebra.com.ar/182 and https://www.cebra.com.ar/spiderman%20spidy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.cebra.com.ar/mu%C3%B1eco-esqueleto-pirata-con-sonido-halloween-7799089087585/p all use the title “Juguetería Cebra”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.cebra.com.ar/150, https://www.cebra.com.ar/191, https://www.cebra.com.ar/promociones, https://www.cebra.com.ar/preguntas-frecuentes, https://www.cebra.com.ar/sucursales and https://www.cebra.com.ar/mu%C3%B1eco-esqueleto-pirata-con-sonido-halloween-7799089087585/p and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.cebra.com.ar/mu%C3%B1eco-esqueleto-pirata-con-sonido-halloween-7799089087585/p, whose canonical is https://www.cebra.com.ar/mu%2525C3%2525B1eco-esqueleto-pirata-con-sonido-halloween-7799089087585/p. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.cebra.com.ar/promociones, https://www.cebra.com.ar/preguntas-frecuentes, https://www.cebra.com.ar/sucursales and https://www.cebra.com.ar/mu%C3%B1eco-esqueleto-pirata-con-sonido-halloween-7799089087585/p have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.cebra.com.ar/191 took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 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
37 small tap targets
37 of 114 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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 350 words of copy
The homepage carries about 350 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 (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.
26 other companies contacted
Loading the homepage contacts 26 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 cebra.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 61 issues on cebra.com.ar, including 28 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.