Website review, no card needed
bristol.com.py website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 89 checks
This review found 43 issues worth fixing on bristol.com.py, 25 of them high impact, across 89 checks. The most urgent: fcdn.app adds 2.5 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
| Nov 7, 2026 | 2.5 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 369 ms |
| Jun 6, 2026 | 385 ms |
| Jun 13, 2026 | 396 ms |
| Jun 20, 2026 | 406 ms |
| Jun 27, 2026 | 408 ms |
| Jul 4, 2026 | 441 ms |
| Jul 11, 2026 | 480 ms |
| Jul 18, 2026 | 531 ms |
| Jul 25, 2026 | 594 ms |
| Aug 1, 2026 | 598 ms |
| Aug 8, 2026 | 529 ms |
| Aug 15, 2026 | 467 ms |
| Aug 22, 2026 | 419 ms |
| Aug 29, 2026 | 389 ms |
| Sep 5, 2026 | 391 ms |
| Sep 12, 2026 | 390 ms |
| Sep 19, 2026 | 386 ms |
| Sep 26, 2026 | 401 ms |
| Oct 3, 2026 | 449 ms |
| Oct 10, 2026 | 508 ms |
| Oct 17, 2026 | 574 ms |
| Oct 24, 2026 | 608 ms |
| Oct 31, 2026 | 607 ms |
| Nov 7, 2026 | 617 ms |
| Nov 14, 2026 | 603 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
1.7 s
3.4 s
5.0 s
6.7 s
8.4 s
10.1 s
11.7 s
13.4 s
Speed
fcdn.app adds 2.5 s
2.5 sfcdn.app costs a phone 2.5 s of main-thread work and 4.4 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.
Render-blocking requests
2.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.6 s · 661 KiBAbout 661 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 734 KiB17 files are served with short cache lifetimes, so returning visitors download them again (734 KiB).
Improve image delivery
1.2 s · 626 KiB26 images could be 626 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Main-thread work: 17.6 s
A phone's processor spends 17.6 s on main-thread work while loading, 5.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
15,345 HTML elements
The page has 15,345 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Facebook adds 1.0 s
1.0 sFacebook costs a phone 1.0 s of main-thread work and 400 KiB 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: 28
28/100Your mobile performance score is 28. 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 (fcdn.app, Facebook and Google Tag Manager and others), adding 5.9 MB and 5.0 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
Google Tag Manager adds 860 ms
860 msGoogle Tag Manager costs a phone 860 ms of main-thread work and 499 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.
net.py adds 179 ms
179 msnet.py costs a phone 179 ms of main-thread work and 366 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
150 ms · 117 KiBAbout 117 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
42 KiB42 KiB could be saved by minifying JavaScript.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
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 CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 44 ms
44 msYour server sent the HTML in 44 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: 1.5 s
1.5 sReal visitors wait 1.5 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.47
0.47For real visitors the layout shifts by 0.47 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 12.8 s
12.8 sYour largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “catalogo splits”. Most of its time is element render delay (5.9 s).
Total Blocking Time: 4.7 s
4.7 sScripts block taps and scrolling for 4.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 13.3 s
13.3 sVisually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 369 ms to 603 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 386 requests
6.1 MBYour homepage downloads 6.1 MB in 386 requests on a phone: images 3.8 MB (281), scripts 1.6 MB (24) and fonts 476 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (90 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 206.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
16 buttons without a name
16 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
15 dropdowns have no label.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
<marquee> elements are deprecated and must not be used (1 element)
<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (111 elements)
All page content should be contained by landmarks: 111 elements on the page fail this check, rated moderate by axe-core.
123 form fields without a label
123 form fields have no label, so screen readers announce an empty box and autofill guesses.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 454 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 failed. 3 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.
845 internal links, 14 external
The homepage links to 845 pages on bristol.com.py and 14 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Comprá electrodomésticos, celulares, televisores, motos y más en Bristol. Financiación propia, cuotas accesibles y enví…”.
One H1 headline
Your main headline reads: “Bristol: Electrodomésticos y Tecnología en Paraguay”.
Title: 46 characters
Your title is a healthy 46 characters: “Electrodomésticos, Celulares y TVs en Paraguay”.
Canonical URL set
The canonical URL is https://www.bristol.com.py/.
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://www.bristol.com.py/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (6,605 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bristol.com.py/llms.txt (4 KiB, 0 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 188 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://f.fcdn.app/assets/manifest.json' from origin 'https://www.bristol.com.py' has been block…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
358 of 366 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 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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,060 words of copy
The homepage carries about 1,060 words of visible text.
3 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
24 other companies contacted
Loading the homepage contacts 24 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 bristol.com.py, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on bristol.com.py, including 25 speed issues, 1 SEO issue and 3 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.