Website review, no card needed
friopecas.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202646 issues · 95 checks
This review found 46 issues worth fixing on friopecas.com.br, 18 of them high impact, across 95 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 296 ms |
| May 16, 2026 | 294 ms |
| May 23, 2026 | 288 ms |
| May 30, 2026 | 287 ms |
| Jun 6, 2026 | 298 ms |
| Jun 13, 2026 | 307 ms |
| Jun 20, 2026 | 314 ms |
| Jun 27, 2026 | 312 ms |
| Jul 4, 2026 | 306 ms |
| Jul 11, 2026 | 304 ms |
| Jul 18, 2026 | 295 ms |
| Jul 25, 2026 | 300 ms |
| Aug 1, 2026 | 314 ms |
| Aug 8, 2026 | 327 ms |
| Aug 15, 2026 | 337 ms |
| Aug 22, 2026 | 338 ms |
| Aug 29, 2026 | 330 ms |
| Sep 5, 2026 | 316 ms |
| Sep 12, 2026 | 310 ms |
| Sep 19, 2026 | 311 ms |
| Sep 26, 2026 | 311 ms |
| Oct 3, 2026 | 309 ms |
| Oct 10, 2026 | 311 ms |
| Oct 17, 2026 | 316 ms |
| Oct 24, 2026 | 337 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.0 s
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.5 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 (Google Tag Manager, vtexassets.com and Facebook and others), adding 2.6 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
840 ms · 65 KiBAbout 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 840 ms faster on a phone.
Google Tag Manager adds 730 ms
730 msGoogle Tag Manager costs a phone 730 ms of main-thread work and 933 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.
Use efficient cache lifetimes
300 ms · 479 KiB15 files are served with short cache lifetimes, so returning visitors download them again (479 KiB).
vtexassets.com adds 527 ms
527 msvtexassets.com costs a phone 527 ms of main-thread work and 819 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.
uc2bbh.com.br adds 117 ms
117 msuc2bbh.com.br costs a phone 117 ms of main-thread work and 352 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 249 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
122 KiB122 KiB could be saved by minifying JavaScript.
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 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 CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 760 ms
760 msScripts block taps and scrolling for 760 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Loja de Ar-Condicionado com os melhores preços do Brasil!”. Most of its time is element render delay (2.4 s).
Real-user INP: 277 ms
277 msReal visitors wait 277 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 921 ms
921 msReal visitors wait 921 ms for your server to start answering (75th percentile). Good is under 800 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 296 ms to 337 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-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 166 requests
3.4 MBYour homepage downloads 3.4 MB in 166 requests on a phone: scripts 2.9 MB (72), images 152 KiB (36) and HTML 136 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 114.5 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
Invalid ARIA attributes
10 elements use ARIA attributes their role does not allow, which confuses screen readers.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
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.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.
Alternative text of images should not be repeated as text (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 48 images in the HTML carry an alt attribute.
41 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: 41 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 5 problems
Structured data found ((untyped), OnlineStore and WebSite) but with 5 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
No social preview image
No Open Graph image, 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.
34 internal links, 13 external
The homepage links to 34 pages on friopecas.com.br and 13 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Compre ar-condicionado, eletrodomésticos e eletroportáteis na Friopeças com preços imperdíveis. Parcele em até 8x sem j…”.
One H1 headline
Your main headline reads: “Loja de Ar-Condicionado com os melhores preços do Brasil!”.
Title: 65 characters
Your title is a healthy 65 characters: “Friopeças | Loja de Ar-Condicionado e Eletrodomésticos há 31 Anos”.
Canonical URL set
The canonical URL is https://www.friopecas.com.br/.
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.friopecas.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.friopecas.com.br/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (238 words), so crawlers that don't run JavaScript still read it.
Other pages
5 linked pages hidden from search
https://www.friopecas.com.br/618, https://www.friopecas.com.br/534, https://www.friopecas.com.br/312, https://www.friopecas.com.br/544 and https://www.friopecas.com.br/723 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages share a meta description
https://www.friopecas.com.br/618, https://www.friopecas.com.br/534, https://www.friopecas.com.br/312, https://www.friopecas.com.br/a-melhor-opcao-com-as-melhores-condicoes-vix, https://www.friopecas.com.br/544 and https://www.friopecas.com.br/723 use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.friopecas.com.br/calculadora and https://www.friopecas.com.br/nossas-lojas have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.friopecas.com.br/nossas-lojas 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.
7 pages slow to respond
https://www.friopecas.com.br/618, https://www.friopecas.com.br/ar-condicionado/ar-condicionado-janela, https://www.friopecas.com.br/a-melhor-opcao-com-as-melhores-condicoes-vix, https://www.friopecas.com.br/ar-condicionado/ar-condicionado-split-piso-teto, https://www.friopecas.com.br/544 and https://www.friopecas.com.br/723 and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
5 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 a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97160951&tm=gtm002&Ver=2&mid=fb8f522c-505e-41c6-9901-1a6942bb30eb&bo=1&sid=680e9c10d5ff11f1a4f33f2e6c264519&vid=680ec6b0d5ff11f19c632f04e1f06103&vids=1&msclkid=N>m_t.
15 small tap targets
15 of 40 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 'getRegistrations')”.
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.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Only about 237 words
The homepage has only about 237 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.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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 Microsoft Ads 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
37 other companies contacted
Loading the homepage contacts 37 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 friopecas.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on friopecas.com.br, including 21 speed issues, 2 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.