Website review, no card needed
bbb.com.pa website review
Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 81 checks
This review found 32 issues worth fixing on bbb.com.pa, 7 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
81B- #39,756 of 117,924 reviewed websitesbeats 61%
- #26,571 of 67,048 online storesbeats 54%
- #25,631 of 61,137 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.7 s |
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 245 ms |
| May 2, 2026 | 249 ms |
| May 9, 2026 | 255 ms |
| May 16, 2026 | 253 ms |
| May 23, 2026 | 251 ms |
| May 30, 2026 | 250 ms |
| Jun 6, 2026 | 251 ms |
| Jun 13, 2026 | 255 ms |
| Jun 20, 2026 | 261 ms |
| Jun 27, 2026 | 263 ms |
| Jul 4, 2026 | 263 ms |
| Jul 11, 2026 | 259 ms |
| Jul 18, 2026 | 251 ms |
| Jul 25, 2026 | 244 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 249 ms |
| Aug 15, 2026 | 256 ms |
| Aug 22, 2026 | 260 ms |
| Aug 29, 2026 | 261 ms |
| Sep 5, 2026 | 261 ms |
| Sep 12, 2026 | 263 ms |
| Sep 19, 2026 | 264 ms |
| Sep 26, 2026 | 260 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 254 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
Render-blocking requests
1.2 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 67
67/100Your mobile performance score is 67 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
100 ms · 509 KiB15 images could be 509 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused JavaScript
340 ms · 243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 340 ms faster on a phone.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 656 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,580 HTML elements
The page has 1,580 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 76 ms
76 msShopify costs a phone 76 ms of main-thread work and 334 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Shopify and Cloudflare CDN and others), adding 629 KiB and 236 ms of main-thread time.
Reduce unused CSS
190 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 895 ms
895 msReal visitors wait 895 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 245 ms to 254 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 136 ms
136 msScripts block the page for only 136 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 225 requests
3.3 MBYour homepage downloads 3.3 MB in 225 requests on a phone: images 1.3 MB (43), other files 908 KiB (121) and scripts 776 KiB (45). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ATARDECER_MOVIL.png 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).
5 images far larger than shown
287 KiB5 images are downloaded at several times the size a phone draws them, for example Mujer-Zapatoscerrados_MujerPiccadilly160109STRSOFTSTAR_PRETO at 1,200 px wide, shown at 53 px. Resized copies would save about 287 KiB.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
5 links without text
5 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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h5 and h2 → h4), 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).
2 checks passed
Every image has alt text
All 71 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
146 internal links, 4 external
The homepage links to 146 pages on bbb.com.pa and 4 external pages.
8 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Encuentra en bbb Shoes & Boots la mayor variedad de zapatos de marca para toda la familia. Deportivos, mocasines y más.…”.
One H1 headline
Your main headline reads: “OFERTAS”.
Title: 52 characters
Your title is a healthy 52 characters: “bbb Shoes & Boots: Zapatos en Panamá | Tienda Online”.
Canonical URL set
The canonical URL is https://bbb.com.pa/.
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://bbb.com.pa/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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (420 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bbb.com.pa/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
11 small tap targets
11 of 43 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 71 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 187 words
The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
3 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
12 other companies contacted
Loading the homepage contacts 12 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 bbb.com.pa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on bbb.com.pa, including 15 speed 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.